Sharing, ownership, and going to production
1. Sharing, ownership, and going to production
A flow that runs perfectly on your laptop isn't done. Production-grade means co-owned, runnable by people who didn't build it, and promotable from Dev to Prod. This video covers ownership, connections, environments, and Solutions.2. Owners and run-only users
Open Share on any flow and you'll see two tiers. Owners have full control, so they can edit the flow, change its trigger, swap connections, and add or remove other owners. Run-only users can trigger the flow, usually via a manual button trigger or a shared automated trigger, but they can't change a thing. Run-only users don't even need their own connector authentication; they inherit the flow's connections at trigger time. The principle is least privilege, so give people the smallest tier that lets them do their job.3. Single ownership is a continuity risk
Connections in Power Automate are owned by the user who created them, not by the flow itself. When that user is offboarded, their connections become invalid, and any flow using them starts failing with `Authentication failed` errors the next time it runs. The flow itself is fine; the credentials underneath it are gone. Co-ownership is how you guard against this. Add at least one co-owner who can edit the flow and re-authenticate connections after a departure. Single-ownership flows die the day their owner leaves. Always co-own anything you intend to keep running.4. Connections are user-scoped
Inspect the Connections panel and you'll see exactly which user authenticated each connector. SharePoint might be on your account, Excel Online on a colleague's, Office 365 Users on a third. If any of those users leaves, that connector breaks. For flows you intend to keep in production long-term, use a service account, a dedicated user identity owned by the team rather than any individual. A service account sticks around regardless of personnel changes, so you never end up with a broken connection because someone left the company or moved to a different department. Their connections just keep working.5. Environment promotion: Dev, Test, Prod
Production-grade flows don't live in the environment where you built them. The standard pattern is three environments. Dev is where you iterate, break things, try things, throw flows away. Test mirrors production's data shape and is where stakeholders run user acceptance testing. Prod is where real users live, where every change is reviewed, and where you don't go in and tweak a connection at three in the afternoon on a Friday. Moving a flow between environments isn't copy-paste, since connections, references, and environment-specific URLs all change. That's what Solutions are for.6. Solutions: the production wrapper
A Solution is a container for flows, data tables, connection references, and environment variables, all packaged together. Two pieces matter most. Connection references are named placeholders that let each environment supply its own connection at import time, so the Test environment doesn't accidentally write to Prod's SharePoint. Environment variables do the same thing for values like SharePoint URLs, recipient emails, or threshold numbers, values that change between Dev, Test, and Prod. Export the Solution from Dev, import it into Test, point it at the Test environment's connections and variables, and the flow is configured for that environment without editing the flow itself.7. Let's practice!
Co-own, connect cleanly, and promote through environments. Let's inspect a real Share dialog.Create Your Free Account
or
By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.