Share
Report
4We are using Power Automate under an M365 E3 license. Due to the mandatory MFA enforcement, the connections used by our flows are frequently disconnected.
As a workaround, we created service accounts and excluded them from the MFA policy. This worked for a while. However, Microsoft has recently re-enforced MFA for all users, including these service accounts.
As a result, the Power Automate connections are now being disconnected almost every week, requiring manual reauthentication of multiple flows, which is not sustainable.
Is there any tenant-level configuration, recommended approach, or supported pattern that allows having non-interactive or non-expiring identities to act as owners or connection accounts for Power Automate flows without being affected by MFA re-enforcement?
Any guidance on best practices for this scenario would be greatly appreciated.
All responses (
Answers (
