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.
The connector certification process outlined in this article is for independent publishers. If you own the underlying service to your connector, go to Verified publisher certification process.
Note
This article provides information for certifying custom connectors in Azure Logic Apps, Microsoft Power Automate, Microsoft Power Apps, and using them in Microsoft Copilot Studio. Before following the steps in this article, read Get your connector certified.
When Microsoft certifies your connector for the Independent Publisher program and publishes your connector, your name appears in the product as the official publisher and a generic icon appears on your connector. Preparing and submitting your connector for certification is easy. Before you submit connector files to Microsoft, review and complete all the steps in this article.
Prerequisites
The Independent Publisher Connector Group lets anyone publish a connector to the official list of Microsoft connectors. If you want to contribute to the group, review the group's resources and take any required actions:
- Familiarize yourself with the Power Platform Connectors GitHub repository. The repository contains folders that specifically support independent publishers.
- Review Learning Content for Independent Publisher Connectors
- Read, understand, and agree to the content of the Independent Publisher Connector Group's manifesto.
Step 1: Verify connector isn't already built
Before you start building a connector, verify that the connector isn't already built. To check, you can search for the connector in these places:
- Microsoft Copilot Studio, Microsoft Power Platform, and Azure Logic Apps connectors' list in documentation.
- Power Platform Connectors independent publisher connectors' pull request list in the GitHub repository.
Use this table to see what you can do with your connector based on its status:
| If your proposed connector: | Option: |
|---|---|
| Already exists for Copilot Studio and Power Platform. | You can't build the connector. |
| Already exists as an independent publisher connector. | You can add more functionality to the connector. |
| Is currently a pull request and a proposal. | You can contact the independent publisher to collaborate with them on the connector. |
| Is a pull request and isn't a proposal. | Wait until the connector is certified and deployed. Then, add an update to that connector. |
Step 2: Share connector proposal with Microsoft
After you check that the connector isn't on the platform, share your connector proposal in the Independent Publisher Connector Group's GitHub repository. Sharing your proposal helps avoid duplicate efforts and can help you find collaborators.
To share your proposal, submit a pull request in the GitHub repository that meets these criteria:
- Title the pull request, Proposal - Connector Name (Independent Publisher). For example,
Proposal - HubSpotCRM (Independent Publisher). - Commit an intro.md file with as many details as you can provide. If you're open to finding a collaborator, include your contact email.
Note
You use the same pull request when you're ready to submit all of the files for certification in Step 4.
Step 3: Build connector
Build your connector. To get started, see Create a custom connector from scratch. Before you submit your connector for independent publisher validation and deployment, follow connector preparation best practices:
- Give your connector a title that meets Microsoft requirements.
- Write a description for your connector.
- Define operation and parameter summaries and descriptions.
- Define exact operation responses.
- Prepare the connector artifacts.
Review all the steps in the prepare connector files for certification article.
Step 4: Submit connector artifacts
When you're ready to submit your connector artifacts for Microsoft validation, certification, and deployment, be sure to:
- Submit the connector artifacts to the pull request you created in Step 2.
- Fill out the checklist in the pull request template.
- Remove
Proposal -from your pull request title.
Step 5: Go through connector validation and certification process
After you submit your connector for validation, you can expect to hear from your Microsoft certification engineer within 1–2 weeks.
- If feedback requires an update to the connector, submit the update directly to your initial pull request. Allow an extra 1–2 weeks for this. You might need to fix Swagger validation errors.
- During this process, you keep ownership of your connector, and can accept or reject any changes to your connector.
- After Microsoft approves and merges the pull request, your connector goes through certification. During the certification process, your Microsoft contact reaches out within 1–2 weeks.
- As your connector finishes certification, we also engage with you about a marketing opportunity for your connector on the Power Automate blog.
Step 6: Wait for connector deployment
After the validation and certification process is complete, Microsoft prepares and deploys your certified connector files to a preview region. The preview region lets you test your connector after certification for deployment and confirm the go-live to Microsoft. Your preview testing environment is only available for two days.
Important
On average, it takes 15 business days to deploy the connector. This time is required regardless of the size or complexity of your connector, whether it's new or an update. To protect integrity, all connectors are subject to the same validation tasks to test functionality and content followed in every deployment.
Deployment schedules: Connector deployment schedules for production start Friday mornings, PST/PDT. Notify your Microsoft contact at least 24 hours in advance when you're ready for production deployment so your connector is included in the next scheduled deployment.
Region deployment: Microsoft notifies you by email with the names of the regions where the connector is deployed, as deployment to regions happens in steps. If there's a deployment delay or freeze, you receive an email notification. To learn more, go to Region deployment.
Follow submission best practices
Follow best practices for a successful connector submission:
- Submit only one connector per pull request to ensure that our validation process runs smoothly.
- Follow the pattern
Connector Name (Independent Publisher)in your connector pull request. - Add your email to the support email section. This is in case we need to contact you.
- Fill in the privacy policy parameter with the privacy policy for the end service.
- Write detailed operation descriptions so users can understand your operation.
- If your connector uses OAuth, provide detailed steps on how to create an app in your readme.md. If you don't, certification is delayed. For an example of documentation to include, see the Readme.md example.
- Add response schemas to your actions unless the response schema is dynamic. This helps your connector get 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 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's an API change or update, or a platform issue.
- If there are any platform or security issues, Microsoft investigates as they arise and deprecates broken independent publisher connectors.
Next step
Move your connector from preview to general availability (GA)