Submit your connector for Microsoft certification


This topic is part of a tutorial series on creating and using custom connectors in Azure Logic Apps, Power Automate, and Power Apps. Make sure you read the custom connector overview to understand the process.

To make a custom connector publicly available for all users in Azure Logic Apps, Power Automate, and Power Apps, submit your connector to Microsoft for certification. Microsoft will review the connector and, if it meets certification criteria, approve it for publishing. See the full list of publicly available connectors.

Why should you certify a connector?

Certifying a connector and releasing it publicly offers extensibility of your app through Power Apps as well as automation and integration through Azure Logic Apps and Power Automate. The same connector can drive more usage of your service and your existing API without additional development.

  • Drive more usage
    Increase the reach, discoverability, and usage of your service by publishing pre-defined task specific templates that integrate your app with our growing family of connectors.
  • Expand the reach of your API
    Enable power users to leverage your APIs and extend your solution without having to write code. Using simple clicks, a business user can create and share a multitude of solutions like the one shown below, for organizational or personal use.

Task specific templates

Certification Criteria

In order to qualify for certification, you must meet the following requirements:

Capability Details Required or Recommended
Software-as-a-Service (SaaS) app You must either own the underlying service or present explicit rights to use the API and provide a user scenario that fits well with our products. Required
Authentication type Your API must support one of: OAuth2, Anonymous Authentication, API Key, or Basic Authentication. Required
Support You must provide a support contact so that customers can get help. Required
Availability and uptime Your app has at least 99.9% uptime. Recommended

Certification Process

You don't need to have finished development on your custom connector to apply for certification. Follow the steps below to begin the certification process:

  1. Registration

    1. Register your connector for certification by filling out our registration form.

    2. Expect an email from a Microsoft contact to understand your custom connector, learn about your development progress, and guide you through the certification process.

  2. Submission

    When you are ready to submit your custom connector and your Microsoft contact has instructed you to do so, follow these instructions to prepare and submit your custom connector to Microsoft.

  3. Certification and Deployment

    After we validate your connector's functionality and content, we stage the connector for deployment in the Preview region for testing. Follow these instructions to create an environment in the Preview region in preparation for your testing. Once testing is complete, we ask that you open source your connector. Finally, we'll deploy your connector across all products and regions.

  4. Support and Updates

    Once the connector is released publicly, you may monitor your connector and the related product forums to see if customers hit any issues or have feature requests.

    Updates to an existing connector can be submitted by following these instructions.

    After the connector has been publicly available for some time, it can qualify to have the "preview" tag removed. For more details, ask your Microsoft contact.