A Power Apps custom connector is a governed description of an API, not a way to turn an unsuitable endpoint into a safe business service. Start with the API contract, authentication and data policy. Build the connector only after those decisions are clear.
You do not automatically need an Azure subscription or a new resource group to create a connector. You do need an accessible API, permission to use it, a Power Platform environment in which you can create connectors, and a licence that covers the resulting app and connector use. Microsoft's custom connector wizard supports creating a connector from a blank definition or importing an OpenAPI description.
Prerequisites
Collect these before opening the wizard:
- the API's HTTPS base URL and operation paths
- a current OpenAPI definition, if one exists
- request and response examples with sensitive values removed
- the authentication method and identity owner
- test credentials with the least privileges needed
- error responses, throttling behaviour and pagination rules
- the target environments and deployment owner
Custom connectors are classed as premium capabilities for licensing purposes. Licensing changes, and the connector may also call a separately charged service, so verify the current Power Apps licensing guidance and the API provider's terms before release.
Build the connector
In make.powerapps.com, select the correct environment, open Solutions, then edit or create an unmanaged solution. Choose New custom connector > Create from blank. The exact navigation can change, so use the current Microsoft wizard if the labels differ.
- Give the connector a stable name and description.
- Set the scheme, host and base URL.
- Configure authentication.
- Define each action's operation ID, summary, request and response.
- Import examples or edit the generated schema.
- Create or update the connector before opening the Test page.
Use operation IDs that can survive UI wording changes. Do not encode a version number into every name unless versioning is part of the API contract.
Authentication is the design, not a final checkbox
For a Microsoft Entra ID protected API, register the API and client correctly, expose only the required scopes, and configure the connector's OAuth settings. Microsoft's Entra ID authentication guide describes the redirect URI and consent flow.
Never put a reusable API secret in a Power Fx formula, example payload or article screenshot. If the service accepts only an API key, understand who can create connections and how the key will be rotated. A maker's personal connection is not a sound production ownership model.
Test the contract properly
The connector Test page proves that a selected operation can call the endpoint with the current test connection. It does not prove reliability, authorisation across all user roles or production capacity.
Test at least:
- a valid request
- missing and invalid input
- an unauthorised identity
- an identity that is authenticated but lacks permission
- an empty response and a paged response
- throttling and service errors
- a token or key rotation
Return useful status codes and a consistent error body from the API. Power Apps makers cannot handle an error well if every failure becomes an anonymous 500.
Data loss prevention and sharing
Power Platform data policies group connectors as business, non-business or blocked. A policy can stop an app combining your custom connector with another connector, even when each connection works separately. Ask the environment administrator to review the connector against the tenant's data loss prevention strategy.
Sharing the connector is not the same as sharing its connections. Users still need permission to the app, connector and underlying service. Test with a normal user, not only the maker or environment administrator.
Move it through environments
Put the connector and dependent app or flow in a solution. Use separate development, test and production environments, and replace environment-specific URLs and connection references during deployment. Microsoft's Power Platform ALM guidance explains the difference between unmanaged development work and managed deployment artefacts.
Do not edit the production connector as the normal release process. Export, import, bind the target connections, run the negative tests again, and keep a rollback version.
For more practical connector patterns with licensing and operational ownership made visible, join the Power Apps Builders Space.
Sources
- Create a custom connector from scratch, Microsoft Learn
- Authenticate an API and connector with Microsoft Entra ID, Microsoft Learn
- Power Apps licensing FAQs, Microsoft Learn
- Power Platform data loss prevention policies, Microsoft Learn
- Application lifecycle management with Power Platform, Microsoft Learn