Submit your connector for Microsoft certification
This topic is part of a tutorial series on creating and using custom connectors in Azure Logic Apps, Microsoft Flow, and PowerApps. 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, Microsoft Flow, and Microsoft PowerApps, submit your connector to Microsoft for certification. Microsoft will review the connector and, if it meets certification criteria, will 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 PowerApps as well as automation and integration through Azure Logic Apps and Microsoft Flow. 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.
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 OAuth2, 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|
Before submitting your connector for certification, review the functionality and content of your connector. It is required that you test your custom connector within Flow, PowerApps and Logic Apps to ensure the operations work as expected and the naming, descriptions etc. make sense to the end user.
Some common items you can check for:
- Invalid OpenAPI (Swagger) specification or JSON errors that appear in the Validation section in the connector Definition
- Runtime and schema validation errors that appear in the Test section from the custom connector wizard
- Make sure that each operation, input parameter, and response attribute in your connector's OpenAPI specification includes summary, description, and visibility information
Submit your connector to Microsoft for certification
Certification typically takes about two weeks from submitting the artifacts through publishing, depending on how well it meets the certification criteria. To apply for certification, follow these steps:
If your connector is approved, Microsoft will send the mutual Non-Disclosure Agreement and the Partner Agreement that are required to submit your connector for review.
Once the agreements are signed, send this information to your nomination contact for review:
The connector ID for your custom connector (the generated id found in the URL when selecting your custom connector). Note this custom connector should have at least 10 successful calls per operation.
The OpenAPI specification file that describes your API
The icon file (.png or .jpg) that represents your connector
- Your icon should have a ~160 pixel logo inside a 230 pixel square. A white logo on a colored background is preferred.
Your icon's brand color in hexadecimal format, which should match the colored background in the icon file
- A test account for validation
- If all operations require test parameters, provide test values for at least one operation
- If your connector uses OAuth, provide client ID/secrets for testing with https://*.consent.azure-apim.net/redirect as the whitelisted redirect URL. We'll reach out for the production details
- An email address for support or details on how customers can file support issues
Please let us know if you are unable to provide any of the above. We will contact you if we have any questions or need additional information.
After we validate your connector's functionality and content, we stage the connector for deployment across all products and regions.
By default, all connectors are published as "preview" and "premium". A "premium" connectors means users will need a paid subscription to leverage them. If the service your connector leverages is built on Azure, you can apply for listing your connector as a "standard" connector that's available to all users with Office 365 Enterprise plans. For more details, ask your nomination contact.
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 through this certification process.
After the connector has been publicly available for some time, it can qualify to have the "preview" tag removed. For more details, ask your nomination contact.