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-11Lines changed: 14 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,17 @@
1
1
---
2
2
title: Troubleshoot broken connections
3
-
description: Learn how to troubleshoot and resolve connection problems and ensure a smoother experience with your applications and services in Microsoft Power Automate.
3
+
description: Learn how to troubleshoot and resolve connection problems and ensure a smoother experience with your applications and services in Microsoft Power Platform.
4
4
ms.custom: sap:Connections
5
5
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/22/2025
10
10
11
11
---
12
-
# Troubleshoot broken connections in Power Automate
12
+
# Troubleshoot broken connections in Microsoft Power Platform
13
13
14
-
This article describes the following common issues about broken connections in Microsoft Power Automate and helps you troubleshoot and solve these issues.
14
+
There are various reasons why [connection](/power-automate/add-manage-connections) problems might occur in Microsoft Power Platform. This article describes some of the common reasons and helps you troubleshoot and solve these issues.
15
15
16
16
-[Connection times out](#connection-times-out)
17
17
-[A DLP block occurs](#a-dlp-block-occurs)
@@ -49,7 +49,7 @@ When a DLP block occurs, you might also receive one of the following error messa
49
49
### Troubleshooting steps
50
50
51
51
1. Review DLP policies: Check the DLP policies configured in the organization to understand what actions are being blocked and why.
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
+
2. Consult with your administrator: If they've blocked the connector or connection, consult with them about unblocking it.
53
53
54
54
## Invalid authenticated devices
55
55
@@ -71,14 +71,16 @@ In this situation, you might also receive one of the following error messages:
71
71
72
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.
73
73
74
+
For more information, see [Refresh tokens in the Microsoft identity platform](/entra/identity-platform/refresh-tokens).
75
+
74
76
In this situation, you might also receive one of the following error messages:
75
77
76
78
> - The refresh token has expired due to inactivity. The token was issued on \<DateTime> and was inactive for 90.00:00:00.
77
79
> - The provided authorization code or refresh token has expired due to inactivity. Send a new interactive authorization request for this user and resource.
78
80
79
81
### Troubleshooting steps
80
82
81
-
To troubleshoot this issue, create a new connection or re-authorize the existing one.
83
+
Create a new connection or re-authorize the existing one.
82
84
83
85
## Connection issue related to attended mode
84
86
@@ -88,19 +90,19 @@ This refers to problems that occur when a user tries to use features that requir
88
90
89
91
### Troubleshooting steps
90
92
91
-
Ensure the user has the correct license to interact with the system as required in attended mode. For more information, see [Which Power Automate licenses do I need?](/power-platform/admin/power-automate-licensing/faqs#which-power-automate-licenses-do-i-need)
93
+
Ensure the user has the correct license to interact with the system as required in unattended mode. For more information, see [Which Power Automate licenses do I need?](/power-platform/admin/power-automate-licensing/faqs#which-power-automate-licenses-do-i-need)
92
94
93
95
## Password modification by a user
94
96
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).
97
+
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.
96
98
97
99
You might also receive the following error message:
98
100
99
101
> 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>'.
100
102
101
103
### Troubleshooting steps
102
104
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.
105
+
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. To avoid this issue, use services like [Microsoft Entra ID](/entra/fundamentals/whatis).
104
106
105
107
## Azure Active Directory (AAD) configuration is changed
106
108
@@ -130,7 +132,7 @@ To resolve this issue, another user with access can reauthorize the connection,
130
132
131
133
## Tenant administrator disables the application
132
134
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.
135
+
This refers to a situation where the tenant administrator has deactivated 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.
134
136
135
137
You might also receive the following error message:
136
138
@@ -142,4 +144,5 @@ To resolve this issue, the tenant administrator needs to reenable the applicatio
142
144
143
145
## More information
144
146
145
-
[Manage connections in Power Automate](/power-automate/add-manage-connections)
147
+
-[Manage connections in Power Automate](/power-automate/add-manage-connections)
148
+
-[Create a connection with a service principal](/power-automate/desktop-flows/alm/alm-connection)
0 commit comments