{"id":13882,"date":"2021-04-14T08:00:23","date_gmt":"2021-04-14T15:00:23","guid":{"rendered":""},"modified":"2025-06-11T07:54:45","modified_gmt":"2025-06-11T14:54:45","slug":"announcing-data-source-environment-variables","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/announcing-data-source-environment-variables\/","title":{"rendered":"Announcing data source environment variables"},"content":{"rendered":"
Today we’re excited to announce a vast new set of capabilities that provide enterprise grade application lifecycle management for the data sources<\/strong>\u00a0that canvas apps and cloud flows connect to. Environment variables are now natively built into<\/strong> authoring experiences across canvas apps and cloud flows as well as solution authoring and solution import<\/strong> experiences. We’ve also added several new and enhanced\u00a0API’s<\/strong> to simplify working with environment variables in code and within automated ALM<\/strong> pipelines.<\/p>\n \u00a0<\/p>\n \u00a0<\/p>\n Environment variables have been a powerful tool for a variety of ALM scenarios as they allow you to externalize input parameters from the components that use them. They’re now much simpler to work with and can store parameters required to connect to data.<\/strong>\u00a0 This allows you to change the data sources <\/strong>(as well as other types of parameters) when migrating solutions to other environments.<\/p>\n \u00a0<\/p>\n If you want to provide new environment variable values<\/strong> when importing to other environments, it’s important to remove the values from your solution before it’s exported<\/strong>. You do not<\/span> need to delete them from the environment, however. This way everything will remain connected in the development environment.\u00a0<\/em><\/p>\n It’s important to ensure users of the application have appropriate access. In addition to sharing the apps and flows, they’ll need an appropriate security role granting access to canvas apps, processes, and environment variables in Dataverse.<\/p>\n If you need to change the data sources being used in a production environment, you may edit the values of the environment variables or update them via managed solution upgrade. Any apps and flows using the environment variables will start using the new values.<\/p>\n For more information please refer to the docs<\/a>.<\/p>\n In case you’re unfamiliar with importing solutions, connection references, and environment variables I suggest reading this blog post<\/a> to gain a base understanding.\u00a0<\/em> Today we’re excited to announce a vast new set of capabilities that provide enterprise grade application lifecycle management for the data sources used within canvas apps and cloud flows. Environment variables are now natively built into authoring experiences across canvas apps and flows as well as solution and solution import experiences. We’ve also added several new API’s to simplify working with environment variables in code and within automated ALM pipelines.<\/p>\n","protected":false},"author":95,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ms_queue_id":[],"ep_exclude_from_search":false,"_classifai_error":"","_classifai_text_to_speech_error":"","_alt_title":"","ms-ems-related-posts":[],"footnotes":""},"audience":[3378],"content-type":[3424],"job-role":[],"product":[3473],"property":[],"topic":[3421,3422],"coauthors":[2139],"class_list":["post-13882","post","type-post","status-publish","format-standard","hentry","audience-it-professional","content-type-news","product-power-apps","topic-application-modernization","topic-hyperautomation"],"yoast_head":"\n
<\/p>\nWhy data source environment variables?<\/h2>\n
Build<\/h3>\n
\n
Deploy & Automate<\/h3>\n
\n
Govern<\/h3>\n
\n
<\/h2>\n
Let’s use a simple example:<\/h2>\n
<\/p>\n\n
\n
Step 1: Create my solution and canvas app<\/h3>\n
\n
\n
<\/li>\n\n
<\/p>\nStep 2: Create a cloud flow<\/h3>\n
\n

\nNote: Some experience improvements are rolling out and some are still in-development. For example, the “Parameters” label will soon be “Environment variables” and the list will have better filtering based on the parameter type.\u00a0<\/em><\/p>\nStep 3: Migrate your solution to another environment<\/h3>\n
\n
Step 4: Manage<\/h3>\n
More information<\/h2>\n
\nWe’d love to hear your feedback<\/strong>. Please comment below or visit the Power Apps community site<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"