A flow that worked yesterday and fails today usually has nothing wrong with its logic. The connection underneath it broke. Microsoft Learn’s troubleshooting article Troubleshoot broken connections in Microsoft Power Platform (last updated 31 March 2026) lists eleven causes, from expired tokens and password changes to Conditional Access and Terms of Use policies.
The governance point is that most of these breaks are caused by identity and policy decisions made outside Power Automate, often by a different team. The fix is rarely in the flow designer. This article walks through each scenario with a realistic use case, the error text Learn lists, who has to act, and what prevents it from happening again.
The eleven scenarios at a glance
| Scenario | Typical use case | Who fixes it |
|---|---|---|
| Connection times out | Gateway flow fails during a server patch window | Maker, with infrastructure team |
| Inactivity persists for a long time | Quarterly SharePoint flow unused for 90 days | Maker |
| Password modification is made by a user | Owner resets an expired password | Maker |
| Microsoft Entra ID configuration is changed | New MFA rule for sign-ins from a new location | Tenant admin, then maker |
| DLP block occurs | Blocked connector added to a flow | Power Platform admin |
| Invalid authenticated devices are used | Repair attempted from a non-compliant laptop | Tenant admin, then maker |
| Conditional Access policy mismatch for embedded flows | Flow started from a SharePoint list fails | Identity admin |
| Terms of Use policy breaks flow connections | Service account flows fail after a new Terms of Use control | Identity admin and flow owner |
| Connection owner account is deleted or disabled | Leaver’s shared connection breaks a team flow | Another user with access |
| Tenant administrator disables the application | App registration clean-up disables a service principal | Tenant admin |
| Connection problem related to attended mode | Desktop flow moved to an unattended machine | Licensing admin |
Tokens and sign-in
Four scenarios come down to the token behind a connection no longer being valid.

1. Connection times out
Use case. A nightly flow reads orders from an on-premises SQL Server through a data gateway. The server is offline for its monthly patch window and the run fails.
What Learn says. The server does not respond “within a specified time limit,” because it is offline, the network has issues, or processing takes too long. The fix is to check the internet connection, check the server status and “try increasing the timeout limit.”
Prevention. Align flow schedules with maintenance windows and add retry policies to actions that call slow systems. Note that the error Learn lists for this section, “The user could not be authenticated as the grant is expired,” describes an expired grant rather than a timeout, so read the run history before assuming the network is at fault.
2. Inactivity persists for a long time
Use case. A records team runs a SharePoint archive flow once a quarter. Between runs the connection is idle, and when the next quarter arrives the flow fails.
What Learn says. “The SharePoint connector requires usage at least one time every 90 days to remain active.” The error reads “The refresh token has expired due to inactivity.” The fix is to “create a new connection or reauthorize the existing one.”
Prevention. Keep a register of low-frequency flows and check their connections before each cycle. Quarterly and annual processes are the ones most likely to fail silently.
3. Password modification is made by a user
Use case. An HR coordinator’s password expires and is reset. The Outlook connection in the employee onboarding flow stops sending welcome emails.
What Learn says. “Every time that you update your password, you invalidate the existing connection that uses the old password.” The error says the grant “has expired due to it being revoked” and that the user “might have changed or reset their password.” Makers must edit the connection or create a new one, and Learn suggests using services such as Microsoft Entra ID to avoid the problem.
Prevention. Business-critical flows should not depend on one person’s password. Where the connector supports it, a service principal connection removes the personal password from the picture.
4. Microsoft Entra ID configuration is changed
Use case. The security team starts requiring MFA for sign-ins from outside named locations. A manager traveling abroad finds that the approval flows they own have stopped and ask for sign-in.
What Learn says. Changes such as “moving to a new location, altering user roles, and updating security settings” can invalidate tokens. The error reads “Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication.” The fix is to contact the tenant administrator and reauthorize.
Prevention. Identity changes should go through a change notice that names Power Automate as an affected service, so makers can reauthorize before runs fail.
Devices and policies
Four scenarios are caused by a policy refusing the token or the action. These are the ones makers cannot fix alone.

5. DLP block occurs
Use case. A maker adds a Dropbox action to a flow in an environment whose data policy blocks that connector. The flow is suspended.
What Learn says. A block occurs when a policy “detects that an action, such as sending an email message or sharing a file, violates the organization’s data protection rules.” The fix is to review the policies and ask the administrator to unblock the connector. The two errors Learn lists here, however, are Conditional Access errors (“Access has been blocked by Conditional Access policies” and a domain-joined device requirement), not data policy errors.
Prevention. Publish the connector classification for each environment so makers know before they build. Power Platform Engineer covered how data policies now reach agents as well in Copilot Studio Data Policies Now Apply to Every Agent.
6. Invalid authenticated devices are used
Use case. A finance analyst tries to repair a connection from a personal laptop that is not enrolled in Intune. Sign-in is refused.
What Learn says. This is “not related to Power Automate but to the tenant’s configuration.” Errors include “Device used during the authentication is disabled” and “Conditional Access policy requires a compliant device.” The fix is to ask the tenant administrator why the device was disabled and reauthorize.
Prevention. Tell makers which devices may be used to create and repair connections, and make the support route to the device management team obvious.
7. Conditional Access policy mismatch for embedded flows
Use case. A Conditional Access policy requires MFA for SharePoint Online only. A user runs a flow from a SharePoint list and it fails with AADSTS50076.
What Learn says. The host application “exchanges its token for a Microsoft Flow Service token,” and the exchange fails when requirements differ. The fix is to go to Protection, Conditional Access, Policies in the Microsoft Entra admin center and “switch your policy to target the Office 365 app or All cloud apps.” If individual apps must be targeted, align MFA, Terms of Use and device compliance with Microsoft Flow Service (Application ID 7df0a125-d3be-4c96-aa54-591f83ff541c), then ask users to sign out and back in.
Prevention. Treat SharePoint, Teams, Excel and Power Automate as one surface in Conditional Access design.
8. Terms of Use policy breaks flow connections
Use case. Compliance adds a Terms of Use grant control to a policy that covers all users. The next morning, flows owned by an integration service account show “Failed to refresh access token for service.”
What Learn says. Silent token refresh fails because “the Terms of Use acceptance page can’t be presented without an interactive session,” which “breaks connections retroactively.” Learn notes the error “doesn’t specifically mention Terms of Use.” The fix is to check Entra sign-in logs for AADSTS50158 or AADSTS53003 against Microsoft Flow Service, have the owner accept interactively, repair the connection and “exclude service accounts and dedicated flow connection owners” from Terms of Use policies.
Prevention. This is the scenario most likely to be misdiagnosed. Add Terms of Use changes to the same change notice as other Conditional Access updates.
Owners, applications and licenses
The last three scenarios happen when the account, application or license behind a connection is no longer there.

9. Connection owner account is deleted or disabled
Use case. An analyst leaves the company. Their account is disabled, and the shared connection used by the team’s purchase approval flow fails for everyone.
What Learn says. The connection “becomes invalid and affects all users who share it.” Errors include “The user account is disabled.” The fix is to “have another user who has access reauthorize the connection. This action updates the ownership and restores functionalities for all users.”
Prevention. Add flow and connection ownership to the leaver process, and make sure every shared flow has a second owner before it reaches production.
10. Tenant administrator disables the application
Use case. During an app registration clean-up, an admin disables an Entra application that a deployment pipeline uses through a service principal connection.
What Learn says. Disabling the application “invalidates any service principal connections associated with the application because it can no longer issue tokens.” The fix is for the tenant administrator to “reenable the application or create a new service principal connection.”
Prevention. Tag app registrations that back Power Platform connections and check those tags before any clean-up. Service principals solve the password problem in scenario 3, but they need an owner of their own.
11. Connection problem related to attended mode
Use case. A desktop flow built and tested on a maker’s own machine is moved to run overnight on an unattended virtual machine. The owner does not hold a license that covers unattended runs, and the connection fails.
What Learn says. “If a user without the appropriate license tries to use unattended mode, the connection fails.” The fix is to make sure the user has the correct license, with a pointer to the Power Automate licensing FAQ. Power Platform Engineer covered desktop flow scheduling in Desktop Flows Get Templates, Native Schedules, and a Flowchart Designer.
Prevention. Make the license check part of the move from attended to unattended, not something discovered after the first failed night.
What the documentation does not cover yet
As read on 20 November 2026, the Learn article leaves some gaps admins should know about:
- The error listed under “Connection times out” describes an expired grant, and the errors under “DLP block occurs” are Conditional Access errors. Makers who match on error text may land in the wrong section.
- It does not say where to change a timeout limit, or which actions allow it.
- The 90-day inactivity window is given only for SharePoint. Other connectors are not listed.
- It offers no admin tool, report or PowerShell command for finding broken connections across a tenant, or for finding connections owned by a disabled account before they fail.
- It does not name which licenses cover unattended mode; it links to the licensing FAQ instead.
- It does not cover how these scenarios apply to Copilot Studio agents and workflows that use the same connections.
Admin checklist
- Add Power Automate to the impact list for every Conditional Access, MFA, Terms of Use and device compliance change.
- Target Office 365 or All cloud apps in Conditional Access, or align host apps with Microsoft Flow Service.
- Exclude service accounts and dedicated flow connection owners from Terms of Use grant controls.
- Add flow and connection ownership to the leaver process, and require a second owner for shared flows.
- Use service principal connections for business-critical flows where the connector supports them, and tag the app registrations behind them.
- Keep a register of quarterly and annual flows and check their connections before each run.
- Publish connector classifications per environment so makers see data policy limits before building.
- Check licensing before any desktop flow moves from attended to unattended.
- Route connection failures to monitoring and alerts rather than waiting for users to notice. See Power Platform Admins Get a Cowork Plugin, Alert Routing, and Metrics Export, and for who owns which admin surface, Copilot Studio Agent Governance Now Spans Five Admin Centers.
Sources
- Troubleshoot broken connections in Microsoft Power Platform, Microsoft Learn, last updated 31 March 2026
- Conditional access and multifactor authentication in Power Automate, Microsoft Learn (linked from the article, not reviewed for this post)
- Manage connections in Power Automate, Microsoft Learn (linked from the article)
- Which Power Automate licenses do I need?, Microsoft Learn (linked from the article)
