Custom connector FAQ for Azure Logic Apps, Microsoft Flow, and PowerApps

Note

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.

Requirements

Q: Can I build a connector without REST APIs?
A: For PowerApps and Microsoft Flow, you must support stable HTTP REST APIs for your service. For Logic Apps, you also have the option of using a SOAP API.

Q: What tools can I use to expose an API?
A: Azure has capabilities and services that you can use for exposing any service as an API, such as Azure App Service for hosting, API Management, and more.

Q: What authentication types are supported?
A: You can use these supported authentication standards:

Limits

Q: What are the limits for connectors and API requests?
A: The following tables show the limits:

Azure Logic Apps Limit
Number of custom connectors that you can create 1,000 per Azure subscription
Number of requests per minute for each connection created by a custom connector 500 requests for each connection created by the connector
Microsoft Flow and PowerApps Limit
Number of custom connectors that you can create Free plan: one1
Office 365 and Dynamics 365 plans: one
Plan 1 and Plan 2: unlimited
Number of requests per minute for each connection created by a custom connector 500 requests for each connection created by the connector

1 The free plan doesn’t allow you to share connections or custom connectors with other people in your company.

If you use an OpenAPI definition or Postman collection to describe a custom connector, the file must be less than 1 MB.

Triggers

Q: Can I build triggers without webhooks?
A: Custom connectors for Azure Logic Apps and Microsoft Flow support webhook-based and polling triggers. Webhook-based triggers wait for an event to occur, while polling triggers call your service at a specified frequency to check for new data. If you want to request other patterns for implementation, contact condevhelp@microsoft.com with more details about your API.

Certification

Q: I'm not a Microsoft partner or Independent Software Vendor (ISV). Can I still create connectors?
A: Yes, you can register and share these connectors for internal use in your organization, but if you want to certify and publicly release a connector, you must either own the underlying service or present explicit rights to use the API.

Other

Q: My APIs use a dynamic host. How do I implement them with OpenAPI?
A: Custom connectors don't support dynamic hosts. Instead, use a static host for development and testing purposes. If you want to certify your connector, ask your Microsoft contact about dynamic implementation.

Q: Do you support Postman Collection V2?
A: No, only Postman Collection V1 is currently supported.

Q: Do you support OpenAPI 3.0?
A: No, only OpenAPI 2.0 is currently supported.