{"id":111043,"date":"2020-09-15T06:56:52","date_gmt":"2020-09-15T13:56:52","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/move-flows-across-environments-without-resetting-connections\/"},"modified":"2025-06-11T07:57:44","modified_gmt":"2025-06-11T14:57:44","slug":"move-flows-across-environments-without-resetting-connections","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/move-flows-across-environments-without-resetting-connections\/","title":{"rendered":"Move flows across environments without resetting connections!"},"content":{"rendered":"

Today, I am really excited to announce the public preview of “Connection References”. We are introducing this new concept, to make it easier for customers to maintain a level of abstraction between flows and the connections used by them. Connection references are particularly useful when moving flows across environments, updating flow definitions, automating deployment pipelines for secure, and healthy Application Lifecycle Management.<\/p>\n

A couple of things to keep in mind before we dive deeper:<\/p>\n

This new feature is only available for “Solution-Aware” flows, as it relies on the solution framework provided by the Common Data Service instance. Learn more<\/a> about solutions in Power Platform.<\/p>\n

To understand, how connection references work, it is important to understand how flows and connections are associated with each other.<\/p>\n

Without connection references – every action in your flow is bound to a specific instance of a connection that it will use to “execute” that action. This is why today, while moving flows across environments – users are required to rebind every operation to a connection.<\/p>\n

[Connections contain secrets, and therefore can’t be moved across environments]<\/em><\/p>\n

Visualizing this across multiple flows – you may have something as follows, where each dotted line indicates – a link that requires rebinding after importing or updating a flow via a solution.<\/p>\n

\"\"
Flows without connection references<\/figcaption><\/figure>\n

When you move flows across environments – all the links shown by dotted <\/em>lines are severed. This means in the above example without connection references, users are required to rebind each of these six links between flow operations and connections after performing an update or import.<\/p>\n

Connection references provides an abstraction layer between resources (like flows and canvas apps) and the connections they use, and has durable dependency tracking across environments. This means you will only need to setup your connection references once per environment!<\/p>\n

Another added benefit of this feature is that if you ever need to swap out connections, you will only have to do it once – by updating the connection reference to a different connection (as opposed to updating every operation).<\/p>\n

Please note, during the preview – there is a limitation of reusing a connection reference in up to 16 flows only. This limitation will be removed as the feature becomes generally available.<\/p>\n

\"\"
Flows with Connection References<\/figcaption><\/figure>\n

Using Connection References<\/h3>\n

If you’re building a new solution-aware flow, connection references will automatically be created for you.<\/p>\n

Users are also able to create connection references independently, from the +New menu in the solution explorer.\"\"<\/p>\n

\u00a0<\/p>\n

In summary,<\/p>\n