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.

What are the benefits of becoming a partner and certifying a connector?

There are many benefits to building and certifying a connector for Power Automate, Power Apps, and Logic Apps. This includes the ability to expand the reach of your API to users of the Power Platform, provide low-friction options for your users to interact with your service, and more. If certifying your connector is something you’d be interested in, start the process by registering your connector and our team will help you every step of the way to succeed with your integration.

  • Certify for free.
    There’s no cost to register, go through the certification process, or update your connector post certification—no matter how many times you update.
  • Integrate your API with Microsoft's Power Platform.
    Have your customers asked for integrations for Power Automate, Power Apps, or Logic Apps? Microsoft’s Power Platform provides citizen developers with the capabilities to build low code or no code apps and powerful automations with our growing family of connectors.
  • Belong to the official list of Microsoft connectors.
    In addition to being listed in the public connector documentation, the connector will be showcased on certified connector pages in the Power Automate and Power Apps sites. Each connector will receive its own connector page on the Power Automate and Power Apps websites.
  • Expand the reach of your API.
    Enable Power Platform users anywhere in the world to use your APIs and extend your solution without having to write a single line of code. Using simple clicks, a business user can create and share a multitude of solutions involving several connectors at the same time.
  • Drive the usage of your API through templates.
    Templates are a combination of connectors that offer predefined automations to target specific scenarios. By publishing a template, you’ll streamline the experience for your users and inspire more ways to use your connector on the platform, simultaneously increasing the reach, discoverability, and usage of your service.
  • Receive dedicated support throughout the certification process.
    A dedicated Microsoft contact will personally review your submission, provide feedback, and help guide you through the entire certification process every step of the way.
  • Obtain thorough review and technical feedback.
    Our team of engineers, who have insights based on over 400 connectors launched to-date, will help unblock partners through technical support and perform a technical review before the connector goes public to ensure its success and reliability.
  • View connector health and usage telemetry any time.
    In ISV Studio, you can view the monthly success rate in terms of API responses, the monthly active connections, and the monthly request count for your certified connector.
  • Market your product to the Microsoft community.
    Once the connector is certified, we’ll highlight it in our monthly Power Automate new connector blog post to drive visibility of the launch to users.
  • Get a social media shoutout.
    We will provide more exposure of your launch by sharing the blog post and an image that highlights your brand on our Power Automate Twitter account.

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're 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. During the submission process, you'll be open sourcing your connector to our Power Platform Connectors repository.

  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 validated, we'll deploy your connector across all products and regions.

    As your connector is finishing certification, we will engage you about a marketing opportunity for the connector on the Power Automate blog. Expect to hear from your Microsoft contact about this opportunity through email.

  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 and meets certain requirements, it can qualify to have the "preview" tag removed. For more details, ask your Microsoft contact.