Update your certified connector

This article contains information for updating the certified connectors for Power Automate, Power Apps, Azure Logic Apps, and Microsoft Copilot Studio. Make sure you have a certified, released connector with Microsoft before following these steps.

To update your certified connector, you need to submit a new set of connector artifacts for certification. Follow the same instructions you used when first certifying 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 evaluates your updates and deploys the updated version of the connector. This article describes the criteria for updates.

Submit an update

1. Ensure that you Meet submission requirements before proceeding with your update submission. Failure to do so can result in delays in the update process.

2. (For verified publishers) After you get the new connector artifacts ready to submit, go to Partner Center.

   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.

3. Don't create a new offer for updating your existing certified connector.

4. After you submit your artifacts, we certify the new version and send it back to you for testing. Then, test your connector as we did for the first version.

   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

   Fifteen days are required for deployment regardless of the size or complexity of your connector, whether it's new or an update. To protect integrity, the connector is subjected to the same validation tasks to test functionality and content that are followed in every deployment.

   Learn more in production schedule.

Notify your customer of breaking changes

If your new connector version changes the functionality of the operations within your connector—for example, changing an operation path—the update introduces breaking changes. The connector needs special handling.

You need to provide customers with the breaking changes you're going to use in the new update by updating explicitly the intro.md file, which is in the certification package. The public documentation that generates through the intro.md file can be utilized to market about the breaking changes to your customer. Learn more on how to generate the intro.md file in Create an intro.md artifact.

Generally, we suggest operational versioning as a solution to breaking changes. This allows existing workflows to continue to work and introduces new versions of operations as needed. There are some cases of breaking changes that might not require operational versioning. Connect with your Microsoft contact to discuss these cases.