Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article explains how to update certified connectors for Microsoft Copilot Studio, Microsoft Power Automate, Microsoft Power Apps, and Azure Logic Apps. Make sure you have a certified connector released with Microsoft before you follow these steps.
To update your certified connector, submit a new set of connector artifacts for certification. Follow the same instructions you used when you first certified your connector.
- If you're a verified publisher, go to Verified publisher certification process for instructions.
- If you're an independent publisher, go to Independent publisher certification process for instructions.
Also, ensure that your new connector version still adheres to our guidelines and requirements.
Microsoft reviews your updates and deploys the updated connector version. This article describes the criteria for updates.
Submit an update
Important
Open source the connector before Microsoft adds it to the certification portal to reduce inconsistencies. See Verified publisher certification process.
Make sure you meet submission requirements before you submit your update. If you don't, your update process can be delayed.
(For verified publishers) When your new connector artifacts are ready, go to Partner Center.
You need to have already submitted artifacts to Partner Center in Microsoft 365 and Copilot Program. Reopen the same offer and update the relevant tab in Product Overview.
You must have previously submitted artifacts to the Partner Center in Microsoft 365 and Copilot Program. Reopen the same offer and update the relevant tab in Product Overview of your offer.
Don't create a new offer to update your existing certified connector.
After you submit your artifacts, Microsoft certifies the new version and sends it back to you for testing. Test your connector as you did for the first version.
To learn more, see Test your connector in certification. Confirm the go-live post in Partner Center, and Microsoft deploys your connector.
To learn more, go to Test your connector in certification. Confirm the go-live post in Partner Center, which Microsoft deploys as your connector.
Important
Deployment takes 15 days, no matter the size or complexity of your connector, whether it's new or an update. To protect integrity, Microsoft runs the same validation tasks to test functionality and content for every deployment.
Learn more in production schedule.
Notify your customers of breaking changes
If your new connector version changes the functionality of operations—for example, changing an operation path—the update introduces breaking changes. The connector needs special handling, and you need to inform your customers.
Many update scenarios can introduce breaking changes. Here are common examples.
| Name | Description |
|---|---|
| AuthenticationMethodRemoved | Do not remove existing authentication methods. Changing the authentication type of your connector in an update isn't allowed. |
| ConnectionParametersRemoved | Do not remove field connection parameters. This change may break existing flows because their connections are still using this field. |
| InputFieldDeleted | The input field is deleted. |
| InputFieldVisibilityChangedToInternal | The input-field visibility is changed to internal. This change may cause the Default value to replace existing values or existing values are removed for existing flows after update. |
| OperationDeleted | The operation is deleted. This change may break existing flows. |
| OperationHidden | The operation is hidden. This change may break the designer for existing flows. |
| OutputFieldAddedWhenRestricted | The output field is added when additional properties are not allowed. This change may break validation for existing flows. |
| OutputFieldChangedToOptionalFromRequired | The output field is changed from required to optional. This change may break existing flows that rely on this field, as required. |
| OutputFieldDeleted | The output field is deleted. This change may break existing flows if they are using this field and the actual payload is changed. |
| OutputFieldTypeChanged | The type is changed for the output field. This change may break existing flows if they are using this field and actual payload is changed. |
| OutputFieldTypeFormatChanged | The type format is changed for the output field. This change may break existing flows if they're using this field and the actual payload is changed. |
| OutputSchemaRemoved | The output schema definition is removed. This change may break existing flows that use this output and the actual payload is changed. |
| ParameterVisibilityChangedToInternal | The visibility is changed to internal for the parameter. This change may cause the Default value to replace existing values or existing values are removed for existing flows after update. |
| ResponseHeaderRemoved | The response header is removed. This change may break any existing flows that use this header and actual payload is changed. |
| ResponseHeaderTypeChanged | The response header type is changed. This change may break existing flows that use this header and actual payload is changed. |
| ResponseHeaderTypeFormatChanged | The response header type format is changed. This change may break existing flows that use this header and actual payload has been changed. |
| TierChangedToPremium | The connector tier is changed to Premium. This change means customers with Free plans can no longer use the connector. |
Make sure you detail all connector updates and any breaking changes in the intro.md file in your certification package. The public documentation generated from the intro.md file helps you inform your customers about breaking changes. Learn more in Create an intro.md artifact.
As a best practice, follow operational versioning to handle breaking changes. This lets existing workflows keep working and introduces new versions of operations as needed. Some breaking changes don't require operational versioning. Connect with your Microsoft contact to discuss these cases.