You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -87,6 +88,81 @@ Perform one of the following options for your Windows Server 2012 R2 servers pri
87
88
88
89
- Option #2: Deploy a new Azure File Sync server that's running a [supported operating system version](file-sync-planning.md#operating-system-requirements) to replace your Windows 2012 R2 servers. For guidance, see [Replace an Azure File Sync server](file-sync-replace-server.md).
89
90
91
+
## Version 22.3.0.0
92
+
The following release notes are for Azure File Sync version 22.3.0.0 (released April 17, 2026). This release contains improvements for the Azure File Sync service and agent.
93
+
### Improvements and issues that are fixed
94
+
95
+
**Sync and change detection reliability**
96
+
Addressed reliability issues in corner case error conditions to ensure more consistent sync and change detection behavior.
97
+
98
+
**Certificate rotation compatibility in Azure China regions**
99
+
Resolves a certificate rotation issue affecting China East 2 and China North 2. Customers in these regions who applied the temporary workaround can now remove it after upgrading to v22.3.
100
+
101
+
**Miscellaneous reliability and telemetry improvements for cloud tiering and sync**
102
+
103
+
### Evaluation Tool
104
+
Before deploying Azure File Sync, you should evaluate whether it's compatible with your system using the Azure File Sync evaluation tool. This tool is an Azure PowerShell cmdlet that checks for potential issues with your file system and dataset, such as unsupported OS version. For installation and usage instructions, see [Evaluation Tool](file-sync-planning.md#evaluation-cmdlet) section in the planning guide.
105
+
106
+
### Agent installation and server configuration
107
+
For more information on how to install and configure the Azure File Sync agent with Windows Server, see [Planning for an Azure File Sync deployment](file-sync-planning.md) and [How to deploy Azure File Sync](file-sync-deployment-guide.md).
108
+
109
+
- The agent installation requires a restart for servers that have an existing Azure File Sync agent installation if the agent version is older than 18.2.0.0.
110
+
- The agent installation package must be installed with elevated (admin) permissions.
111
+
- The agent isn't supported on Nano Server deployment option.
112
+
- The agent is supported only on Windows Server 2016, Windows Server 2019, Windows Server 2022 and Windows Server 2025.
113
+
- The Azure File Sync agent installation package is specific to the operating system version. If you're upgrading a server to a newer version of Windows Server, you must first uninstall the Azure File Sync agent and restart the server. ***Don't unregister and re-register the server during the OS upgrade, or it will lead to orphaned tiered files on existing server endpoints.*** Then, upgrade the operating system to the new version. After the upgrade is complete, install the Azure File Sync agent that matches the new Windows Server version such as 2016, 2019, 2022, or 2025. After installing the agent on the upgraded server, the Azure portal should reflect the correct server status within 30 minutes.
114
+
- The agent requires at least 2 GiB of memory. If the server is running in a virtual machine with dynamic memory enabled, the VM should be configured with a minimum 2048 MiB of memory. See [Recommended system resources](file-sync-planning.md#recommended-system-resources) for more information.
115
+
- The agent uses TLS 1.2 or 1.3 (Windows Server 2022 or newer) by default. TLS 1.0 and 1.1 aren't supported.
116
+
- Server registration using the [Register-AzStorageSyncServer](/powershell/module/az.storagesync/register-azstoragesyncserver) and ServerRegistration.exe require .NET Framework 4.7.2. or higher.
117
+
- The Storage Sync Agent (FileSyncSvc) service doesn't support server endpoints located on a volume that has the system volume information (SVI) directory compressed. If the SVI directory is compressed, the Storage Sync Agent (FileSyncSvc) service will fail to start.
118
+
- Agent installation can fail with error **0x80c84111** if required Windows security updates are missing. To prevent this issue, make sure the following updates are installed based on your server version:
119
+
- Windows Server 2016 [Microsoft Update Catalog](https://catalog.update.microsoft.com/Search.aspx?q=cumulative%20windows%20server%202016) (latest cumulative update)
120
+
- Windows Server 2019 [Microsoft Update Catalog](https://catalog.update.microsoft.com/Search.aspx?q=cumulative%20windows%20server%202019) (latest cumulative update)
121
+
- Cumulative updates are released monthly. To deploy the latest update, users can either use Windows Update or manually download it from the [Microsoft Update Catalog](https://catalog.update.microsoft.com). If installing manually, users should review the associated KB article to ensure all prerequisites are met. If the Windows Updates aren't installed prior to installing the Azure File Sync agent, the Storage Sync Agent service (FileSyncSvc) will fail to start. To learn more, see the [Azure File Sync troubleshooting documentation](/troubleshoot/azure/azure-storage/files/file-sync/file-sync-troubleshoot).
122
+
123
+
124
+
### Interoperability
125
+
- Antivirus, backup, and other applications that access tiered files can cause undesirable recall unless they respect the offline attribute and skip reading the content of those files. For more information, see [Troubleshoot Azure File Sync](/troubleshoot/azure/azure-storage/file-sync-troubleshoot?toc=/azure/storage/file-sync/toc.json).
126
+
- File Server Resource Manager (FSRM) file screens can cause endless sync failures when files are blocked because of the file screen.
127
+
- Running sysprep on a server that has the Azure File Sync agent installed isn't supported and can lead to unexpected results. The Azure File Sync agent should be installed after deploying the server image and completing sysprep mini-setup.
128
+
129
+
### Sync limitations
130
+
The following items don't sync, but the rest of the system continues to operate normally:
131
+
132
+
- Azure File Sync supports all characters that are supported by the [NTFS file system](/windows/win32/fileio/naming-a-file) except invalid surrogate pairs. See [Troubleshooting guide](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-sync-errors?toc=/azure/storage/file-sync/toc.json#handling-unsupported-characters) for more information.
133
+
- Paths that are longer than 2,048 characters.
134
+
- The system access control list (SACL) portion of a security descriptor that's used for auditing.
135
+
- Extended attributes.
136
+
- Alternate data streams.
137
+
- Reparse points.
138
+
- Hard links.
139
+
- Compression (if it's set on a server file) isn't preserved when changes sync to that file from other endpoints.
140
+
- Any file that's encrypted with EFS (or other user mode encryption) that prevents the service from reading the data.
141
+
142
+
> [!NOTE]
143
+
> Azure File Sync always encrypts data in transit. Data is always encrypted at rest in Azure.
144
+
145
+
### Server endpoint
146
+
- A server endpoint can be created only on an NTFS volume. Azure File Sync doesn't currently support ReFS, FAT, or FAT32.
147
+
- Cloud tiering isn't supported on the system volume. To create a server endpoint on the system volume, disable cloud tiering when creating the server endpoint.
148
+
- Failover Clustering is supported only with clustered disks, but not with Cluster Shared Volumes (CSVs).
149
+
- A server endpoint can't be nested. It can coexist on the same volume in parallel with another endpoint.
150
+
- Don't store an OS or application paging file within a server endpoint location.
151
+
152
+
### Cloud endpoint
153
+
- Azure File Sync supports making changes to the Azure file share directly. However, any changes made on the Azure file share first need to be discovered by an Azure File Sync change detection job. A change detection job is initiated for a cloud endpoint once every 24 hours. To immediately sync files that are changed in the Azure file share, use the [Invoke-AzStorageSyncChangeDetection](/powershell/module/az.storagesync/invoke-azstoragesyncchangedetection) PowerShell cmdlet to manually initiate the detection of changes in the Azure file share.
154
+
- The storage sync service and/or storage account can be moved to a different resource group, subscription, or Microsoft Entra (formerly Azure AD) tenant. After moving the storage sync service or storage account, you need to give the Microsoft.StorageSync application access to the storage account (see [Ensure Azure File Sync has access to the storage account](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-sync-errors?toc=/azure/storage/file-sync/toc.json#troubleshoot-rbac)).
155
+
156
+
> [!NOTE]
157
+
> When creating the cloud endpoint, the storage sync service and storage account must be in the same Microsoft Entra ID tenant. After you create the cloud endpoint, you can move the storage sync service and storage account to different Microsoft Entra ID tenants.
158
+
159
+
### Cloud tiering
160
+
- If a tiered file is copied to another location by using Robocopy, the resulting file isn't tiered. The offline attribute might be set because Robocopy incorrectly includes that attribute in copy operations.
161
+
- When copying files using Robocopy, use the /MIR option to preserve file timestamps. This will ensure older files are tiered sooner than recently accessed files.
162
+
163
+
164
+
165
+
90
166
## Version 22.0.0.0
91
167
The following release notes are for Azure File Sync version 22.0.0.0 (released December 09, 2025). This release contains improvements for the Azure File Sync service and agent.
0 commit comments