Skip to content

Commit b2e4bda

Browse files
authored
Merge pull request #9452 from MicrosoftDocs/khdownie-patch-2
Update file-sync-troubleshoot-managed-identities.md
2 parents 0f260f6 + f021238 commit b2e4bda

File tree

1 file changed

+10
-11
lines changed

1 file changed

+10
-11
lines changed

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

Lines changed: 10 additions & 11 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/22/2025
6+
ms.date: 07/31/2025
77
author: khdownie
88
ms.author: kendownie
99
---
@@ -101,7 +101,7 @@ Cloud endpoint:
101101
- Storage Sync Service managed identity must be a member of the **Storage File Data Privileged Contributor** role on an Azure file share.
102102

103103
Server endpoint:
104-
- Register server managed identity must be a member of the **Storage File Data Privileged Contributor** role on an Azure file share.
104+
- Registered server managed identity must be a member of the **Storage File Data Privileged Contributor** role on an Azure file share.
105105

106106
When you run the `Set-AzStorageSyncServiceIdentity` cmdlet or create new cloud and server endpoints, these permissions are granted. If these permissions are removed, operations fail with the errors listed in the following section.
107107

@@ -169,7 +169,6 @@ Set-AzStorageSyncServerEndpointPermission -ResourceGroupName <string> -StorageSy
169169
> [!NOTE]
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
172-
173172
### Sync Session fails with the ECS_E_AUTH_IDENTITY_NOT_FOUND error
174173

175174
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.
@@ -181,24 +180,24 @@ This issue often occurs in the following situations:
181180
- Azure Arc resource deletion and recreation.
182181
- Turning off and then re-enabling the system-assigned managed identity on an Azure virtual machine.
183182

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.
183+
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 and return the `ECS_E_AUTH_IDENTITY_NOT_FOUND` error.
185184

186185
To resolve this issue:
187186

188-
First, ensure the server is configured to use a managed identity.
187+
Make sure that the server is configured to use a managed identity.
189188

190-
You can verify this by:
191-
- Checking the **Settings** > **Managed identities** details in your storage sync service, or
192-
- Running the following PowerShell command:
189+
To verify this configuration:
190+
- Check the **Settings** > **Managed identities** details in your storage sync service, or
191+
- Run the following PowerShell command:
193192

194193
```powershell
195194
Get-AzStorageSyncServer -ResourceGroupName <ResourceGroupName> -StorageSyncServiceName <StorageSyncServiceName>
196195
```
197-
> [!NOTE]
198-
> This error can occur whether the server is using managed identity (MI) or certificate-based authentication, so confirming the identity type is important.
199196

197+
> [!NOTE]
198+
> This error can occur whether the server is using managed identity (MI) or certificate-based authentication. Therefore, it's important to verify the identity type.
200199
201-
If the server is using managed identity and the identity has changed, run the following command to update the server registration:
200+
If the server uses managed identity and the identity was changed, run the following command to update the server registration:
202201

203202
```powershell
204203
Set-AzStorageSyncServer -ResourceGroupName <ResourceGroupName> -StorageSyncServiceName <StorageSyncServiceName> -Identity

0 commit comments

Comments
 (0)