Skip to content

Commit 80386cf

Browse files
author
Simonx Xu
authored
Merge pull request #9389 from MicrosoftDocs/main
Auto push to live 2025-07-22 10:01:50
2 parents 2a02d1c + c672ba8 commit 80386cf

File tree

2 files changed

+11
-10
lines changed

2 files changed

+11
-10
lines changed

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-managed-identities.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Troubleshoot Azure File Sync managed identity issues
33
description: Troubleshoot common issues when your Azure File Sync deployment is configured to use managed identities.
44
ms.service: azure-file-storage
55
ms.topic: troubleshooting
6-
ms.date: 07/16/2025
6+
ms.date: 07/22/2025
77
author: khdownie
88
ms.author: kendownie
99
---
@@ -170,17 +170,18 @@ Set-AzStorageSyncServerEndpointPermission -ResourceGroupName <string> -StorageSy
170170
> The `-Name` parameter is the name of the server endpoint. It's a GUID, not the friendly name that's displayed in the Azure portal. To get the server endpoint name, run the [Get-AzStorageSyncServerEndpoint](/powershell/module/az.storagesync/get-azstoragesyncserverendpoint) cmdlet.
171171
172172

173-
### Sync Session fails with ECS_E_AUTH_IDENTITY_NOT_FOUND error
173+
### Sync Session fails with the ECS_E_AUTH_IDENTITY_NOT_FOUND error
174174

175-
The `ECS_E_AUTH_IDENTITY_NOT_FOUND` error occurs when the server's managed identity used to communicate with the Azure File Sync service has changed, but the Azure File Sync service is still expecting the previous identity. This can result in authentication failures.
175+
The `ECS_E_AUTH_IDENTITY_NOT_FOUND` error occurs when the server's managed identity used to communicate with the Azure File Sync service has changed, but the Azure File Sync service is still expecting the previous one, causing authentication to fail.
176176

177-
You can identify this issue by checking for **Event ID 9530** in the **Telemetry** event log within **Event Viewer**. This event indicates that the managed identity's `applicationId` has changed.
177+
You can identify this issue by checking for **Event ID 9530** in the **Telemetry** event log within **Event Viewer**. This event indicates that the `applicationId` of the managed identity has changed.
178178

179-
Common scenarios that can trigger this issue include:
180-
- Azure Arc resource deletion and recreation
181-
- Toggling the system-assigned managed identity on an Azure VM off and then back on
179+
This issue often occurs in the following situations:
182180

183-
When the managed identity changes, the File Sync agent will attempt to use the new identity, but the Azure File Sync service is still configured to authorize the previous one. This mismatch causes requests to fail with the `ECS_E_AUTH_IDENTITY_NOT_FOUND` error.
181+
- Azure Arc resource deletion and recreation.
182+
- Turning off and then re-enabling the system-assigned managed identity on an Azure virtual machine.
183+
184+
When the managed identity changes, the File Sync agent tries to use the new identity, but the Azure File Sync service is still configured to authorize the previous one. This mismatch causes requests to fail with the `ECS_E_AUTH_IDENTITY_NOT_FOUND` error.
184185

185186
To resolve this issue, run the following PowerShell command:
186187

support/entra/entra-id/app-integration/application-delegated-permission-access-tokens-identity-platform.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Delegated permission tokens can only be obtained from the following flows:
3434
* [Authorization code grant flow](/azure/active-directory/develop/v2-oauth2-auth-code-flow)
3535
* [On-Behalf-Of flow](/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow)
3636
* [Device authorization grant flow](/azure/active-directory/develop/v2-oauth2-device-code)
37-
* [Resource Owner Password Credentials grant flow](/azure/active-directory/develop/v2-oauth2-device-code)
37+
* [Resource Owner Password Credentials grant flow](/entra/identity-platform/v2-oauth-ropc)
3838

3939
## Identify the permission type for an access token
4040

@@ -86,4 +86,4 @@ Users often encounter issues when their applications call Microsoft Graph REST e
8686
* Verify if the endpoint supports delegated permissions, application permissions, or both.
8787
* Verify that the access token has the correct permissions to call the endpoint.
8888

89-
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
89+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

0 commit comments

Comments
 (0)