Skip to content

Commit bed3bfa

Browse files
authored
upddates based on the comments
1 parent e952fb3 commit bed3bfa

1 file changed

Lines changed: 14 additions & 11 deletions

File tree

support/power-platform/power-automate/connections/troubleshoot-broken-connections.md

Lines changed: 14 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
---
22
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.
44
ms.custom: sap:Connections
55
ms.workload: connectors
66
author: nravindra-msft
77
ms.author: nravindra
88
ms.reviewer: angieandrews
9-
ms.date: 01/21/2025
9+
ms.date: 01/22/2025
1010

1111
---
12-
# Troubleshoot broken connections in Power Automate
12+
# Troubleshoot broken connections in Microsoft Power Platform
1313

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.
1515

1616
- [Connection times out](#connection-times-out)
1717
- [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
4949
### Troubleshooting steps
5050

5151
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.
5353

5454
## Invalid authenticated devices
5555

@@ -71,14 +71,16 @@ In this situation, you might also receive one of the following error messages:
7171

7272
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.
7373

74+
For more information, see [Refresh tokens in the Microsoft identity platform](/entra/identity-platform/refresh-tokens).
75+
7476
In this situation, you might also receive one of the following error messages:
7577

7678
> - The refresh token has expired due to inactivity. The token was issued on \<DateTime> and was inactive for 90.00:00:00.
7779
> - The provided authorization code or refresh token has expired due to inactivity. Send a new interactive authorization request for this user and resource.
7880
7981
### Troubleshooting steps
8082

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.
8284

8385
## Connection issue related to attended mode
8486

@@ -88,19 +90,19 @@ This refers to problems that occur when a user tries to use features that requir
8890

8991
### Troubleshooting steps
9092

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)
9294

9395
## Password modification by a user
9496

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.
9698

9799
You might also receive the following error message:
98100

99101
> 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>'.
100102
101103
### Troubleshooting steps
102104

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).
104106

105107
## Azure Active Directory (AAD) configuration is changed
106108

@@ -130,7 +132,7 @@ To resolve this issue, another user with access can reauthorize the connection,
130132

131133
## Tenant administrator disables the application
132134

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.
134136

135137
You might also receive the following error message:
136138

@@ -142,4 +144,5 @@ To resolve this issue, the tenant administrator needs to reenable the applicatio
142144

143145
## More information
144146

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

Comments
 (0)