User Profile
jjdev-nz
Copper Contributor
Joined 4 years ago
User Widgets
Recent Discussions
Re: Best practices for Power Automate with service account
Gilbert_Smulders, I might be incorrect, but I think the enforcement for MFA is only applicable for certain applications as per the below link. I think if they were to enforce the MFA for all service accounts, it would cause major issues for everyone that uses them in the Power Platform. You may need to setup a conditional access policy for your service accounts to bypass MFA. Mandatory Microsoft Entra multifactor authentication (MFA) - Microsoft Entra ID | Microsoft Learn1.7KViews0likes0CommentsRe: Best practices for Power Automate with service account
HiLimeLeaf 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. Regardlessif 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.29KViews1like1CommentRe: Best practices for Power Automate with service account
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.141KViews4likes8Comments
Recent Blog Articles
No content to show