What is a connection reference?

Without connection references, the connection is embedded in the flow. If the flow is moved to another environment, it will still point to the developer's personal connection—or it will fail.

What it solves

The reference is a named intermediary. The flow points to the reference, and the reference points to the actual connection. In testing, the reference can point to a test account, and in production to the shared account, without changing the flow.

Why it is an operational issue, not just a technical one

This is the mechanism that allows production workflows to be owned by a shared user rather than by the person who built them. It is the simplest safeguard against automation stopping when someone leaves.

Set them up from the start

Adding connection references later to flows that are already in production is a cleanup job. Include them from the very first flow you package in a solution.