Exporting an Azure hosted API to PowerApps and Microsoft Flow

Creating custom connectors for PowerApps and Microsoft Flow

PowerApps is a service for building and using custom business apps that connect to your data and work across platforms. Microsoft Flow makes it easy to automate workflows and business processes between your favorite apps and services. Both PowerApps and Microsoft Flow come with a variety of built-in connectors to data sources such as Office 365, Dynamics 365, Salesforce, and more. However, users also need to be able to leverage data sources and APIs being built by their organization.

Similarly, developers that want to expose their APIs more broadly within the organization may want to make their APIs available to PowerApps and Microsoft Flow users. This topic will show you how to expose an API built with Azure App Service or Azure Functions to PowerApps and Microsoft Flow. Azure App Service is a platform-as-a-service offering that allows developers to quickly and easily build enterprise-grade web, mobile, and API applications. Azure Functions is an event-based serverless compute solution that allows you to quickly author code that can react to other parts of your system and scale based on demand.

To learn more about these services, see:

Sharing an API definition

APIs are often described using an Open API document (sometimes referred to as a "Swagger" document). This contains all of the information about what operations are available and how the data should be structured. PowerApps and Microsoft Flow can create custom connectors for any Open API 2.0 document. Once a custom connector is created, it can be used in exactly the same way as one of the built-in connectors and can quickly be integrated into an application.

Azure App Service and Azure Functions have built-in support for creating, hosting, and managing an Open API document. In order to create a custom connector for a web, mobile, API, or function app, two steps will be needed:

  1. Retrieving the API definition from App Service or Azure Functions
  2. Importing the API definition into PowerApps

It is possible that these two steps will need to be carried out by separate individuals within an organization, as a given user may not have permission to perform both actions. In this case, a developer who has contributor access to the App Service or Azure Functions application will need to obtain the API definition (a single JSON file) or a link to it. They will then need to provide that definition to a PowerApps or Microsoft Flow owner. That owner can use the metadata to create the custom connector.


Because a copy of the API definition is being used, PowerApps and Microsoft Flow will not immediately know about updates or breaking changes to the application. If a new version of the API is made available, these steps should be repeated for the new version.

Retrieving the API definition from App Service or Azure Functions

In this section, you will export the API definition for your App Service API, to be used later in PowerApps.

  1. Open the Azure Portal and navigate to your App Service or Azure Functions application.

    If using Azure App Service, select API definition from the settings list.

    If using Azure Functions, select Function app settings and then Configure API metadata.

  2. If an API definition has been provided, you will see an Export to PowerApps + Microsoft Flow button. Click this button to begin the export process.

  3. You can choose to either Download the API definition or Get a link. Whichever you choose, the result will be provided in the next section. Select one of these options and follow the instructions.

  4. If your API definition includes any security definitions, these will be called out in step #2. During import, PowerApps and Microsoft Flow will detect these and will prompt for security information. The services use this to log users in, so that they can access the API. If your API requires authentication, ensure that it is captured as a security definition in your Open API document.

    Gather the credentials related to each definition for use in the next section.


If using Azure Active Directory authentication, a new AAD app registration will be needed which has delegated access to your API and a reply URL of https://msmanaged-na.consent.azure-apim.net/redirect. Please see this example for more detail, substituting your API for Azure Resource Manager.

If another individual will be importing the API definition into PowerApps, you will provide the client ID and client secret of the new registration, as well as the resource URL of your API, in addition to the API definition file. Make sure that these secrets are managed securely. Do not share the security credentials of the API itself.

Importing the API definition into PowerApps and Microsoft Flow

In this section, you will create a custom connector in PowerApps and Microsoft Flow using the API definition obtained earlier. Custom connectors are shared between the two services, so you only need to import the definition once. For more information on custom connectors, see Register and use custom connectors in PowerApps and Register and use custom connectors in Microsoft Flow.

To import into PowerApps or Microsoft Flow:

  1. Open the Powerapps web portal or the Microsoft Flow web portal, and sign in.

  2. Click the Settings button (the gear icon) at the upper right of the page and select Custom connectors.

  3. Click Create custom connector.

  4. On the General tab, provide a name for your API, and then upload the OpenAPI definition or paste in the metadata URL. Click Continue.

  5. On the Security tab, if you are prompted to provide authentication details, enter the values obtained in the previous section. If not, proceed to the next step.

  6. On the Definitions tab, all the operations defined in your OpenAPI file are auto-populated. If all your required operations are defined, you can go to the next step. If not, you can add and modify operations here.

  7. Click Create connector. If you want to test API calls, go to the next step.

  8. On the Test tab, create a connection, select an operation to test, and enter any data required by the operation.

  9. Click Test operation.