Skip to content

Commit 5e4d1ba

Browse files
authored
Merge pull request #8640 from MicrosoftDocs/jeffpatt24-patch-3
Update file-sync-troubleshoot-managed-identities.md
2 parents fb27722 + ca4704e commit 5e4d1ba

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

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

Lines changed: 3 additions & 3 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: 11/04/2024
6+
ms.date: 04/02/2025
77
author: khdownie
88
ms.author: kendownie
99
---
@@ -32,13 +32,13 @@ Get-AzStorageSyncServer -ResourceGroupName <string> -StorageSyncServiceName <str
3232
Verify the `ApplicationId` property has a GUID which indicates that the server is configured to use a system-assigned managed identity. Once the server uses a system-assigned managed identity, the value of the `ActiveAuthType` property is updated to `ManagedIdentity`. If the value is `Certificate`, the server uses shared keys to authenticate to Azure file shares.
3333

3434
> [!NOTE]
35-
> Once a server is configured to use a system-assigned managed identity, it can take up to one hour before the server uses the system-assigned managed identity to authenticate to the Storage Sync Service and Azure file shares.
35+
> Once a server is configured to use a system-assigned managed identity, it can take up to 15 minutes before the server uses the system-assigned managed identity to authenticate to the Storage Sync Service and Azure file shares.
3636
3737
## Set-AzStorageSyncServiceIdentity cmdlet doesn't configure a server to use a system-assigned managed identity
3838

3939
If running the `Set-AzStorageSyncServiceIdentity` cmdlet doesn't configure a registered server to use a system-assigned managed identity, it's likely because the server doesn't have a system-assigned managed identity.
4040

41-
To enable a system-assigned managed identity on a registered server that has the Azure File Sync v19 agent installed, perform the following steps:
41+
To enable a system-assigned managed identity on a registered server that has the Azure File Sync v20 agent installed, perform the following steps:
4242

4343
- If the server is hosted outside of Azure, it must be an Azure Arc-enabled server to have a system-assigned managed identity. For more information about Azure Arc-enabled servers and how to install the Azure Connected Machine agent, see [Azure Arc-enabled servers Overview](/azure/azure-arc/servers/overview).
4444

0 commit comments

Comments
 (0)