You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/power-platform/power-automate/connections/troubleshoot-broken-connections.md
+14-13Lines changed: 14 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,8 @@ ms.workload: connectors
6
6
author: nravindra-msft
7
7
ms.author: nravindra
8
8
ms.reviewer: angieandrews
9
-
ms.date: 01/21/2025
9
+
ms.date: 01/21/2025
10
+
10
11
---
11
12
# Troubleshoot broken connections in Power Automate
12
13
@@ -20,7 +21,7 @@ This article describes the following common issues about broken connections in M
20
21
-[Password modification by a user](#password-modification-by-a-user)
21
22
-[Azure Active Directory (AAD) configuration is changed](#azure-active-directory-aad-configuration-is-changed)
22
23
-[Connection owner account is deleted or disabled](#connection-owner-account-is-deleted-or-disabled)
23
-
-[Tenant administrator disabled the application](#tenant-administrator-disabled-the-application)
24
+
-[Tenant administrator disables the application](#tenant-administrator-disables-the-application)
24
25
25
26
## Connection times out
26
27
@@ -34,7 +35,7 @@ You might also receive the following error message:
34
35
35
36
1. Check your internet connection: Ensure that the internet connection is stable and working properly.
36
37
2. Check the server status: Verify if the server you're trying to connect to is online and not experiencing any downtime.
37
-
3. Try increasing the time-out limit: Sometimes, increasing the time-out limit can help in establishing a connection with the server.
38
+
3. Try increasing the time-out limit: Sometimes, increasing the time-out limit can help in establishing a connection with the server.
38
39
39
40
## A DLP block occurs
40
41
@@ -48,11 +49,11 @@ When a DLP block occurs, you might also receive one of the following error messa
48
49
### Troubleshooting steps
49
50
50
51
1. Review DLP policies: Check the DLP policies configured in the organization to understand what actions are being blocked and why.
51
-
2. Consult with your administrator: The administrator might block the connector or connection. It's a good idea to consult with your administrator and discuss the issue to unblock it.
52
+
2. Consult with your administrator: The administrator might block the connector or connection. It's a good idea to consult with your administrator and discuss the issue to unblock it.
52
53
53
54
## Invalid authenticated devices
54
55
55
-
This refers to a situation where a user tries to authenticate using a device for multi-factor authentication (MFA), but the device is disabled. This issue isn't related to Power Automate but to the tenant's configuration at the administrative level.
56
+
This refers to a situation where a user tries to authenticate using a device for multi-factor authentication (MFA), but the device is disabled. This issue isn't related to Power Automate but to the tenant's configuration at the administrative level.
56
57
57
58
In this situation, you might also receive one of the following error messages:
58
59
@@ -68,7 +69,7 @@ In this situation, you might also receive one of the following error messages:
68
69
69
70
## Inactivity for a long time
70
71
71
-
This refers to a situation where a connection becomes invalid because it hasn't been used for a specified period. For example, the SharePoint connector requires usage at least once every 90 days to remain active. If the connection isn't used within this period, it expires.
72
+
This refers to a situation where a connection becomes invalid because it hasn't been used for a specified period. For example, the SharePoint connector requires usage at least once every 90 days to remain active. If the connection isn't used within this period, it expires.
72
73
73
74
In this situation, you might also receive one of the following error messages:
74
75
@@ -81,7 +82,7 @@ To troubleshoot this issue, create a new connection or re-authorize the existing
81
82
82
83
## Connection issue related to attended mode
83
84
84
-
This refers to problems that occur when a user tries to use features that require a license for unattended mode but doesn't have the necessary license. In attended mode, the user must be present and interact with the system, whereas unattended mode allows for fully automated processes without user interaction. If a user without the appropriate license attempts to use unattended mode, the connection fails.
85
+
This refers to problems that occur when a user tries to use features that require a license for unattended mode but doesn't have the necessary license. In attended mode, the user must be present and interact with the system, whereas unattended mode allows for fully automated processes without user interaction. If a user without the appropriate license attempts to use unattended mode, the connection fails.
85
86
86
87
[Learn more about attended and unattended scenarios for process automation](/power-automate/guidance/planning/attended-unattended).
87
88
@@ -91,19 +92,19 @@ Ensure the user has the correct license to interact with the system as required
91
92
92
93
## Password modification by a user
93
94
94
-
This issue occurs when the account password used to create the connection is deleted, changed, or expired. Since account verification is a crucial part of authentication whenever a connection is triggered, the connection breaks if the new password isn't updated. To avoid this issue, use services like [Microsoft Entra ID](/entra/fundamentals/whatis).
95
+
This issue occurs when the account password used to create the connection is deleted, changed, or expired. Since account verification is a crucial part of authentication whenever a connection is triggered, the connection breaks if the new password isn't updated. To avoid this issue, use services like [Microsoft Entra ID](/entra/fundamentals/whatis).
95
96
96
97
You might also receive the following error message:
97
98
98
99
> The provided grant has expired due to it being revoked, a fresh auth token is needed. The user might have changed or reset their password. The grant was issued on '\<DateTime>' and the TokensValidFrom date (before which tokens are not valid) for this user is '\<DateTime>'.
99
100
100
101
### Troubleshooting steps
101
102
102
-
Every time a user updates the password, the existing connection with the password becomes invalid, so the user must create a new connection for each of those connectors or edit the existing connection.
103
+
Every time a user updates the password, the existing connection with the password becomes invalid, so the user must create a new connection for each of those connectors or edit the existing connection.
103
104
104
105
## Azure Active Directory (AAD) configuration is changed
105
106
106
-
This refers to modifications made at the Azure Active Directory (AAD) level that affect user identities or access policies. These changes include moving to a new location, altering user roles, or updating security settings. Such changes might invalidate existing tokens and require users to reauthenticate.
107
+
This refers to modifications made at the Azure Active Directory (AAD) level that affect user identities or access policies. These changes include moving to a new location, altering user roles, or updating security settings. Such changes might invalidate existing tokens and require users to reauthenticate.
107
108
108
109
You might also receive the following error message:
109
110
@@ -125,9 +126,9 @@ In this situation, you might also receive one of the following error messages:
125
126
126
127
### Troubleshooting steps
127
128
128
-
To resolve this issue, another user with access can reauthorize the connection, thereby updating the ownership and restoring functionalities for all users.
129
+
To resolve this issue, another user with access can reauthorize the connection, thereby updating the ownership and restoring functionalities for all users.
129
130
130
-
## Tenant administrator disables the application
131
+
## Tenant administrator disables the application
131
132
132
133
This means that the tenant administrator deactivates an application registered in Azure Active Directory (AAD). This action invalidates any service principal connections associated with the application, as it can no longer issue tokens.
133
134
@@ -137,7 +138,7 @@ You might also receive the following error message:
137
138
138
139
### Troubleshooting steps
139
140
140
-
To resolve this issue, the tenant administrator needs to reenable the application or create a new service principal connection.
141
+
To resolve this issue, the tenant administrator needs to reenable the application or create a new service principal connection.
0 commit comments