Showing results for 
Search instead for 
Did you mean: 

Version Control on Flow Definitions

As would any decent tool where users make changes to code or configuration changes, implementing a version control component, would allow a user to a) rollback, and b) reference back to code.  Optional additional features show which user performed the edits, datetime stamp of changes, and code diff tool between versions.

Status: Under Review
Kudo Collector

Microsoft does not have to implement this, it would be enough if they would provide a flow that every time a flow is modified, it requests a user version comment and saves in a SharePoint library with comment, flow id, link to flow and sends free chocolate cookies to the one who modified the flow...

*irony off*

Advocate I

At the moment I am using "Save as" feature to create my own backups before making significant changes. But proper version control would be a better solution (as I sometimes forget to make copies and often "break" my flows 😉

Regular Visitor

It would be great to be able to check in/out flow definition changes.

Advocate IV

Almost 3 years in review for such a foundational feature... Word Online has it, SharePoint has it, Power Apps has it...  How long does it take to review something that glaring?


I'm afraid this ideas management system is a cemetery where ideas dies and very people visit... especially the Microsoft Program managers.  This tool doesn't appear to be curated or managed dynamically... or even hooked up to an ALS / or Project mgmt for a seamless application lifecycle.

Not applicable

Please get versioning into Power Automate, the fact that it's in PowerApps and not PowerAutomate is very odd.  We can't continue to expect developers to have to use SaveAs each time they make a change.  

Not applicable

This is must have feature for us Specially as we work on Team Flows .. Microsoft Should consider implementing this soon.  

Frequent Visitor

Why it is taking tooooooooooo long? Almost 3 years in Under review🤔

Regular Visitor

Wow, something this important is still just Under Review after 3 years?!

Not applicable

I would really appreciate the Version Control as well.

Basic Version Control like in SharePoint (Online) would be sufficient, preferably combined with "Check-Out" / "Check-In" and a (configurable) required "Check-In comment".

Advocate IV

3 Years LATER!!!  That is quite a review process you have there for a very foundational and badly needed feature.  This is a must for a low code development tool.  Don't believe me? Just turn off version history feature in Visual Studio and see what kind of worldwide riots you end up with...


Without version history makes flow version risky to use for complex processes....  Even Word has it!!!  


Where is the senior management when needed?