TL;DR: Share flows and apps reliably: direct share, export/import via make.powerapps.com, or package everything into a solution with its dependencies.
💡 Challenge
Sharing and moving flows and Power Apps between people and environments can get messy, legacy import paths, missing dependencies, and disconnected flows all cause problems.
✅ Solution
There are several reliable ways to share flows and apps. Pick the one that fits your scenario:
1️⃣ Export/Import: Export flows on make.powerautomate.com. Import on that site is legacy, use the import via make.powerapps.com instead. 2️⃣ Automate sharing with a flow (see #PowerPlatformTip 8). 3️⃣ Package into a solution (Power Apps, flows, connection references, tables, etc.) and export/import it. ⚠️ Watch out for dependency errors, don’t miss anything. 4️⃣ Export a Power App with all connected flows. After import, re-enable each flow and add it back into the app.
🔧 How It’s Done
-
Choose your sharing method based on scope. 🔸 A single flow → direct share or export/import; a whole app + flows → use a solution.
-
Package and check dependencies. 🔸 Add connection references and any required tables, then validate there are no missing dependencies.
-
Import and reconnect. 🔸 Import via make.powerapps.com, re-enable flows, and re-add them to the app where needed. 🔸 Verify everything runs in the target environment.
🎉 Result
Your flows and apps move cleanly between people and environments, with dependencies intact and the right permission levels applied.
🌟 Key Advantages
🔸 Multiple sharing options for different scenarios.
🔸 Solutions keep apps, flows, and dependencies together.
🔸 Granular permission control when sharing.
🎥 Video Tutorial
🛠️ FAQ
1. Can I share flows with external users outside my organization?
Yes, but external users need appropriate Power Platform licenses and must be added as guest users in your Azure AD tenant first.
2. What happens to the flow run history when I share or move flows?
Flow run history stays with the original environment. Only the flow definition and settings are shared or moved to the new environment.
3. Do shared users get the same permission level as the flow owner?
No, you can assign different permission levels (co-owner, editor, or viewer) when sharing flows, allowing granular access control.