web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / ALM Best Practise for ...
Power Automate
Unanswered

ALM Best Practise for multi-instance Flow deploying to another tenant

(0) ShareShare
ReportReport
Posted on by 22

Hi, has anyone got any best (/good) practise recommendations for my scenario where I have a solution (small "s") that consists of a SharePoint site, lists and an associated Power Automate flow. I have customers that use this solution multiple times within their tenant. So this means they would have a SharePoint site for each use case, along with an associated flow. Until now I've been using the "Save as" function on an existing flow to create another copy, but I'd ideally like to leverage Solutions and Variables so that I have one copy of the flow and this is then configurable per instance, by updating the variables. My understanding however, is that the variables are at the Environment level, so I can't do that.

 

In short, does anyone know a good way to build flows in a dev tenant, and deploy to be re-used in multiple configurable instances? 

 

Thanks.

Categories:
I have the same question (0)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 286

#2
David_MA Profile Picture

David_MA 256 Super User 2026 Season 1

#3
Expiscornovus Profile Picture

Expiscornovus 225 Most Valuable Professional

Last 30 days Overall leaderboard