Support for Azure API Management policies in custom connectors

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Power Platform product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Enabled for Public preview General availability
Admins, makers, or analysts, automatically This feature is released. May 1, 2019 This feature is released. Oct 28, 2019

Feature details

While building connectors for Power Apps and Power Automate, developers might need to modify behaviors for the underlying API. For example, in cases where a service provides custom domain or sub-domain endpoints, connectors might need to dynamically route the requests to endpoints based on the connection parameters.

In other cases, connectors might add extra headers or query parameters, or enforce throttling limits for their operations. Today, you can manage these behavioral modifications with Azure API Management (APIM) policies for any of the standard built-in connectors.

Until now, APIM policies weren't available for custom connectors. This has meant that any modification to custom connectors must be done in-house. Partners who build these custom connectors rely on Microsoft for any modification to their connectors, even to try out and test them. This leads to a high-touch development model, which isn't ideal.

With this release, you can enable APIM policies on your custom connectors for your apps (Power Apps) and flows, and then use APIM policies to modify the behaviors of your connectors. For example, APIM policies allow you to limit the number of calls from a connection on one or more operations in your connector. You can use other APIM policies to fix headers or query parameters, or even modify a field or a parameter. You can also use policies to improve the overall user experience of your connectors.

Policy in custom connector

See also

Open source connectors (blog)

Policy templates overview (docs)