cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Frequent Visitor

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

Announcements
firstImage

Super User Program Update

Three Super User rank tiers have been launched!

firstImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

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

Top Solution Authors
Top Kudoed Authors
Users online (5,222)