Forum Discussion

Matthew Carter's avatar
Matthew Carter
Iron Contributor
Jan 04, 2022

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 / ...
admin
office 365
jjdev-nz's avatar
jjdev-nz
Copper Contributor
Apr 13, 2022

Hi LimeLeaf 

 

MS is not very clear on the licensing and it's obvious from all the comments on the web. 

I understand the reasoning for using a Per Flow license for business-critical Flows that uses Premium connectors that are triggered by many users and frequently per day. Flows that have a Per Flow license have an API limit of 250k per day. But if a Flow with Premium connectors is only triggered a few times in a day, then it's not cost effective to use a Per Flow license.  

Regardless if one uses a Per User license connected to a real user or service account, that account can only do 40k API calls per day. Any automated or scheduled Flows always runs in the context of the Flow owner/creator. So if we are using an Per User license connected to a real user or service account, what is the difference, we are paying for the license and using it within the API limits of the day.

If you have a Flow that is exceeding 40k API calls, then its time to look at getting a Per Flow license in my opinion.  

LimeLeaf's avatar
LimeLeaf
Copper Contributor
Apr 13, 2022

Yep, I have the same understanding here. As far as the flows are triggered in a moderate way and in sum they don't exceed a limit of 40k api calls per day and user there shouldn't be licensing issue.

So only for API intensive flows there should be used a per flow license.

To be honest it would be great to have a recommendation in the microsoft documentation that points into this direction.

Resources