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.
Note
This article is part of a tutorial series on creating and using custom connectors in Azure Logic Apps, Microsoft Power Automate, and Microsoft Power Apps, and calling connectors as tools in Microsoft Copilot Studio. Ensure you read the custom connector overview to understand the process.
API and OpenAPI
Q: What are the limits for connectors and API requests? A: The following tables show the limits:
Azure Logic Apps
| Limit | Value |
|---|---|
| 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 |
| Maximum schema count per body allowed in a Swagger file | 512 |
| Maximum number of operations allowed in a Swagger file | 256 |
| Maximum number of schemas per operation allowed in a Swagger file | 16,384 |
| Maximum number of schemas allowed in a Swagger file | Maximum number of operations allowed in a Swagger file * Maximum number of schemas per operation allowed in a Swagger file |
| Maximum request content-length that can be sent to a gateway | 3,182,218 |
Power Automate and Power Apps
| Limit | Value |
|---|---|
| Number of custom connectors that you can create | Free plan: one1 Office 365 and Dynamics 365 plans: one Per user plan: 50 |
| Number of requests per minute for each connection created by a custom connector | 10000 requests for each connection created by the connector |
| Maximum request content-length that can be sent to a gateway | 3,182,218 |
1 The free plan doesn't allow you to share connections or custom connectors with other people in your company. Dynamic scaling of connectors isn't supported in a free or pay-as-you-go environment, and so the number of custom connectors that can be created is one.
If you use an OpenAPI definition or Postman collection to describe a custom connector, the file must be less than 1 MB.
Q: What are the size limits for connectors and operations through a gateway? A: The limits can be found in the gateway documentation.
Q: My APIs use a dynamic host. How do I implement them with OpenAPI? A: Policy templates can be used to dynamically modify the host at runtime. To learn more, go to the Set Host URL.
Q: Do you support Postman Collection V2? A: Yes, support for Postman Collection v2 is available as of October 2021.
Q: Do you support OpenAPI 3.0? A: No, only OpenAPI 2.0 is currently supported. Support for OpenAPI 3 is in the backlog.
Certification
Q: I don't own the API and I don't have explicit rights to use the API. Can I still create connectors? A: Yes, you can register and share these connectors for internal use within your organization, or you can publish it as an independent publisher connector. To certify and publicly release a connector as an independent publisher, you don't need to own the underlying service or present explicit rights to use the API.
Q: How long does certification take? A: The time for certification significantly depends on the quality of the submission and the speed of your testing. Barring problems with the process, it typically takes three to five business days. After certification, deployment to all regions will take another 7 to 10 business days.
Q: Where can I get help if I'm having trouble understanding or executing the submission steps? A: Connect with your Microsoft contact for assistance. You're also encouraged to provide any feedback on our documentation so we can improve it.
Q: Can my connector be certified as a Standard connector instead of Premium? A: No. Unfortunately, we currently only release certified connectors as Premium. Any user with a Power Automate license can use both Standard and Premium connectors.
Q: Can the Preview tag be removed from my connector? A: Your connector needs to meet certain requirements before the Preview tag can be removed. Ensure that your connector has significant usage and high reliability before contacting your Microsoft contact to ask this.
Q: Can the throttling limits for my connector be adjusted? A: We handle throttling limit adjustments on a case-by-case basis. Connect with your Microsoft contact with justification if you'd like your connector's limits adjusted.
Requirements
Q: Can I build a connector without REST APIs? A: For Power Apps and Power Automate, your service must support stable HTTP REST APIs. For Logic Apps, you can also use a SOAP API.
Q: What tools can I use to expose an API? A: Azure provides capabilities and services for exposing any service as an API. These tools include Azure App Service for hosting and API Management.
Q: What authentication types are supported? A: Use these supported authentication standards:
- OAuth 2.0 for specific services, including Microsoft Entra ID, Facebook, Dropbox, GitHub, and SalesForce
- Generic OAuth 2.0
- Basic authentication
- API Key (except on-premises data gateway)
Note
Client credentials grant type isn't supported.
Q: What headers can connectors use in their back-end services? A: You can use the following four headers from Microsoft:
- x-ms-workflow-name
- x-ms-environment-id
- x-ms-workflow-version
- x-ms-workflow-run-id
These headers can change. Check for updates before creating your connectors.
Support
Q: I have a technical question about connector development. Where should I ask for help? A: Add your question to the Power Automate Forum Connector Development Forum. Our team or a community member provides an answer. You can also search for a similar issue. Posting your question helps you get answers from a wider community and improves the forum's knowledge base.
Q: Is a developer plan available to use for my connector development efforts? A: Yes, the Power Apps Community Plan is available for use and is free for Power Apps and Power Automate.
Triggers
Q: Can I build triggers without webhooks? A: Custom connectors for Azure Logic Apps and Power Automate 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.
Related information
Connectors overview Get your connector certified
Provide feedback
We greatly appreciate feedback on issues with our connector platform, or new feature ideas. To provide feedback, go to Submit issues or get help with connectors and select your feedback type.