Microsoft Flow Best Practices

%3CLINGO-SUB%20id%3D%22lingo-sub-6066%22%20slang%3D%22en-US%22%3EMicrosoft%20Flow%20Best%20Practices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-6066%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20are%20the%20best%20practices%20of%20Managing%20Flows%20in%20an%20enterprise%20enviroonment%20in%20terms%20of%3A%3C%2FP%3E%3CP%3E-%20restricting%20who%20can%20create%20flow%3C%2FP%3E%3CP%3E-%20account%20to%20use%20for%20creating%20flows%3C%2FP%3E%3CP%3E-%20source%20control%20or%20versioning%20of%20flows%20and%20how%20to%20update%20Flows%20that%20are%20in%20production%3C%2FP%3E%3CP%3E-%20documenting%20Flows%3F%26nbsp%3B%20Do%20I%20take%20snapshots%20and%20create%20word%20documents%20around%20the%20functionality%20of%20the%20Flow%20or%20is%20there%20a%20way%20to%20export%20the%20Flow%20into%20Visio%20as%20we%20do%20with%20SPD%20Workflows%3F%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4685%22%20target%3D%22_blank%22%3E%40Merwan%20Hade%3C%2FA%3E%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-6066%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Flow%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-240036%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Flow%20Best%20Practices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-240036%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20any%20update%20on%20this%3F%20Specifically%2C%20I'd%20like%20to%20understand%20how%20to%20version%20a%20Flow%20that%20is%20already%20in%20production%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58850%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Flow%20Best%20Practices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58850%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%20to%20ensure%20Flow%20is%20used%20securely%20in%20your%20enterprise%2C%20you%20can%20setup%20Data%20Loss%20Prevention%20(DLP)%20policies%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fflow.microsoft.com%2Fen-us%2Fdocumentation%2Fprevent-data-loss%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fflow.microsoft.com%2Fen-us%2Fdocumentation%2Fprevent-data-loss%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-15838%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Flow%20Best%20Practices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-15838%22%20slang%3D%22en-US%22%3EIs%20there%20any%20update%20on%20this%20original%20query%3F%20I%20would%20also%20like%20to%20know%20how%20to%20restrict%20access%20to%20Flow%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-7398%22%20slang%3D%22en-US%22%3ERE%3A%20Microsoft%20Flow%20Best%20Practices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-7398%22%20slang%3D%22en-US%22%3EJuan%20is%20correct%20in%20that%20Flow%20is%20still%20in%20Preview%20and%20shouldn't%20be%20considered%20ready%20for%20'enterprise'%20production%20environments.%20I%20do%20not%20currently%20know%20of%20documentation%20or%20guidance%20in%20the%20areas%20you%20are%20asking%20about%20-%20however%20you%20are%20asking%20good%20questions.%20Stay%20tuned!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-6684%22%20slang%3D%22en-US%22%3ERE%3A%20Microsoft%20Flow%20Best%20Practices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-6684%22%20slang%3D%22en-US%22%3EI'm%20not%20sure%20if%20Microsoft%20Flow%20can%20be%20considered%20currently%20as%20an%20enterprise%20ready%20technology...by%20the%20way%2C%20there%20is%20a%20lack%20of%20documentation%20from%20Microsoft%20in%20the%20areas%20you%20have%20described%3C%2FLINGO-BODY%3E
Frequent Contributor

What are the best practices of Managing Flows in an enterprise enviroonment in terms of:

- restricting who can create flow

- account to use for creating flows

- source control or versioning of flows and how to update Flows that are in production

- documenting Flows?  Do I take snapshots and create word documents around the functionality of the Flow or is there a way to export the Flow into Visio as we do with SPD Workflows?

@Merwan Hade;

 

5 Replies
I'm not sure if Microsoft Flow can be considered currently as an enterprise ready technology...by the way, there is a lack of documentation from Microsoft in the areas you have described
Juan is correct in that Flow is still in Preview and shouldn't be considered ready for 'enterprise' production environments. I do not currently know of documentation or guidance in the areas you are asking about - however you are asking good questions. Stay tuned!
Is there any update on this original query? I would also like to know how to restrict access to Flow?

Hi all, to ensure Flow is used securely in your enterprise, you can setup Data Loss Prevention (DLP) policies: https://flow.microsoft.com/en-us/documentation/prevent-data-loss/

Is there any update on this? Specifically, I'd like to understand how to version a Flow that is already in production?