Showing results for 
Search instead for 
Did you mean: 
Level: Powered On

Security considerations for Flow connections - Using a Service Account

We are after some best practise guidance for managing Flow connections. I have read few suggestions to use a 'service account' rather than 'personal credentials' when creating Flow. This seems to be a sensible solution e.g. consider the implications of a user with Global Admin rights creating a Flow having connections that use their own credentials. 


However, we have some questions as below. Could anybody who use a service account today share their experience as whether it's been good solution.


- Using a service account comes with additional cost as account itself would require O365 license. I am thinking at least an E3 license to provide the service account access to SharePoint (to update list items) and Exchane Online (for ability to send emails).

- One service account used across many Flows would end up with many permissions e.g. A service account having permissions to many different SharePoint sites.

- How multi-factor authentication would apply to this Service Account. Would this account need to bypass MFA.






Helpful resources


Microsoft Business Applications Virtual Launch Event

Watch the event on demand for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.


Watch Sessions On Demand!

Continue your learning in our online communities.

Power Platform 2019 Release Wave 2 Plan

Power Platform 2019 Release Wave 2 Plan

Features releasing from October 2019 through March 2020.


Flow Community User Group Member Badge

Fill out a quick form to claim your user group badge now!


Microsoft Learn

Learn how to build the business apps that you need.


Power Platform World Tour

Find out where you can attend!


Webinars & Video Gallery

Watch & learn from the Flow Community Video Gallery!

Top Kudoed Authors
Users Online
Currently online: 254 members 4,386 guests
Please welcome our newest community members: