Power Automate · Cloud flows: connection and authentication errors
Unauthorized (401)
Short answer
Unauthorized (401) in a Power Automate cloud flow: The API rejected the request because the authentication token is invalid or expired. The most likely fix is to fix connection, rotate credentials.
VerifiedLast verified
01Error text
Unauthorized
40102Likely causes
- OAuth token expired and the connection couldn't auto-refresh
- The user's account was disabled or password changed
- Service principal secret or certificate expired
- Conditional Access policy blocked the sign-in (geo, device compliance)
03How to fix it
- Go to Power Automate > Connections and find the connection used by the failed action.
- If the connection shows a warning, select Fix connection and re-authenticate.
- For service principal connections, rotate the secret in Microsoft Entra ID and update the connection.
- Check Microsoft Entra ID sign-in logs for Conditional Access blocks: Azure portal > Microsoft Entra ID > Sign-in logs, filter by the app name.
04Official documentation
→Related errors
- Forbidden (403)Forbidden (403) in a Power Automate cloud flow: The authenticated user or app doesn't have permission to perform the requested operation. The most likely fix is to check DLP policies, permissions.
- ConnectionAuthorizationFailedConnectionAuthorizationFailed in a Power Automate cloud flow: The connection exists but its stored credentials are no longer valid. The most likely fix is to fix connection, re-authenticate.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Power Automate work:Open Power Automate jobs