Forum Discussion
Best practices for Power Automate with service account
We had a colleague leave who had their work email address and account connected to MANY Power Automate flows, SharePoint, OneDrive, Forms, Excel, etc. We are looking to create a recommendation / ...
I can't see how MS can force us to use a the Per Flow licensing model instead of a Service account that has a Per User license assigned. In our scenario we create a few account with an E3/5 license and assigne them a Per User license. The accounts are then used by a select few to create any Automated or Scheduled Flows that have business impact. Flows that are for pure personal productivity, are created by the end users personal account. The hard part is keeping up with what flows have business impact vs personal flows.
I'm with you here. I don't think that Microsoft is forcing anybody.
The wording on their post is "[if] the service account is used by many users... it is recommended to assign a per flow license to the flow to ensure any new users adding to the account are automatically compliant."
"Recommended" and "required" have vastly different implications.
The wording on their post is "[if] the service account is used by many users... it is recommended to assign a per flow license to the flow to ensure any new users adding to the account are automatically compliant."
"Recommended" and "required" have vastly different implications.
- The licensing FAQ's have been updated in the last few days https://docs.microsoft.com/en-us/power-platform/admin/power-automate-licensing/faqs#i-have-multiple-flows-running-under-a-shared-service-account-what-licenses-do-i-need
- In this updated document - Microsoft is thinking - that the service account is a shared account with many users that they have access to it. In reality, only the IT has access to the service account. What about that? I am really not happy with this confusing licensing model and each person with which we talking about that topic has another opinion.
