Independent publisher certification process

This process is for independent publishers. If you own the underlying service to your connector, go to Non-Microsoft publisher certification process.

Note

This topic provides information for certifying independent publisher connectors in Azure Logic Apps, Power Automate, and Power Apps. Before following the steps in this article, read Get your connector certified.

After you've finished developing your custom connector, follow these steps to prepare it for certification and generate the connector files to submit to Microsoft. The submission process is done through the GitHub repository for independent publisher connectors.

Read the manifesto

The Independent Publisher Connector Group makes it possible for anyone to publish a connector to the official list of Microsoft connectors. This group asks that participants are aware of and agree to the content of its manifesto. Please read and understand this document if you plan on contributing to or being a part of this effort.

Prepare and submit your connector for certification

The process for certifying your connector as an independent publisher is easy. Before submitting it in the GitHub repository, make sure you perform the steps in this section.

By submitting your independent publisher connector, your name will be featured within our product as the official publisher and a generic icon will be applied to your connector.

Important

If you're considering building and publishing a connector to a Microsoft first party service, email connectorpartnermgmtteam@service.microsoft.com with an explanation of the connector and its endpoints. We'll work with you to find publishing options.

  1. Create a title for your connector that meets Microsoft requirements. For instructions and examples, go to Give your connector a title.

  2. Write a description for your connector. For instructions, go to Write a description for your connector.

  3. Define summaries and descriptions. For instructions, go to Define operation and parameter summaries and descriptions.

  4. Define exact operation responses. For instructions, go to Define exact operation responses.

  5. Add metadata describing the connector and its end service. For instructions, go to Add metadata.

  6. Prepare the connector artifacts. Follow the procedure in Prepare the connector artifacts.

  7. Submit your connector for deployment:

    1. Open a pull request in the open-source repository.

    2. A Microsoft certification engineer will provide feedback within two business days of your initial request. If the feedback requires an update to the connector, you'll need to submit an update to the pull request. Allow an extra two days for this. If you need to troubleshoot swagger errors, go to Fix Swagger Validator errors.

      You'll retain ownership of your connector, and can accept or reject any changes to your connector.

    3. Microsoft will approve and merge the pull request.

  8. Your connector will be submitted for certification. During certification, expect to hear from your Microsoft contact within two business days.

  9. Wait for deployment. After your connector is validated and prepared for production deployment, we'll deploy it to all production regions.

    Important

    On average, it takes 7 to 10 business days to deploy the connector. This is required regardless of the size or complexity of your connector, whether it's new or an update. In order to protect integrity, the connector will be subjected to the same validation tasks to test functionality and content that are followed in every deployment.

    • Deployment schedules: Our connector deployment schedules for production start Monday and Wednesday mornings, PST/PDT. Notify your Microsoft contact when you're ready for production deployment at least 24 hours in advance for us to include your connector in the next scheduled deployment.

    • Region deployment: We'll notify you by email with the names of the regions the connector will be deployed to, as deployment to regions is done in steps. If there's a deployment delay or freeze, you'll be notified by email. More information: Region deployment

    As your connector is finishing certification, we'll engage you about a marketing opportunity for the connector on the Power Automate blog.

  10. Update your connector anytime. Once your certification ends and your connector is published, you can add new operations and functionalities to your connector in the GitHub repository anytime. We'll recertify your connector as needed.

Best practices for submission

  • You can only submit one connector per pull request. This ensures that our validation process runs smoothly.

  • The pull request for your connector should follow the pattern Connector Name (Independent Publisher).

  • Add an email to the support email section. This is in case we need to contact you.

  • Make sure to fill in the privacy policy parameter with the privacy policy for the end service.

  • Make sure that your operation descriptions are detailed. This ensures that the user can understand your operation.

  • If your connector uses OAuth, make sure you provide detailed steps on how to create an app in your readme.md. Failure to do so will result in delays in certification. For an example of documentation to include, go to the Readme.md example.

  • Make sure that you add response schemas to your actions, unless the response schema is dynamic. This will ensure that your connector gets more usage.

  • Review the Checklist before submitting.

Microsoft guarantees

Microsoft commits to satisfying the following guarantees:

  • If there’s an update to the connector, we'll run the breaking change tool and all other validation tools over again.​

  • If there’s no update to a connector, we guarantee that it works unless there is an API change or update, or a platform issue.​

  • Microsoft will investigate platform and security issues as they arise and deprecate broken independent publisher connectors.​

Next step

Test your connector in certification