Environment variable support in custom connectors
Important
This content is archived and is not being updated. For the latest documentation, go to Integrate data into Microsoft Dataverse. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | 
Mar 31, 2022 |
- |
Business value
Custom connectors can now leverage environment variables in the configuration, allowing for seamless development, testing, and deployment of apps and flows using custom connectors.
Feature details
Many enterprises provide app developers access to data sources using APIs. These APIs are often behind an API management product where different versions of the APIs (Dev, Test/UAT, Prod) are maintained. They're also secured by Azure AD or an OAuth server. Until now, customers have had to create different custom connectors, or update custom connectors after deployment, with different API endpoints and application ID/secrets.
With this release, customers can now use an environment variable inside their custom connectors. A custom connector can reference an environment variable for the host/base URL, as well as for other properties like OAuth client ID and client secrets. This allows the same custom connector to be packaged and deployed to different environments where those settings may be different.
For example, in the development environment, the custom connector can target a development API endpoint with a development OAuth/AAD application. The same custom connector in a production environment can target the production API endpoint using a production OAuth/AAD application. This allows for seamless development, testing, and deployment of apps and flows using a custom connector.