Merge pull request #277288 from jeffpatt24/patch-10

Update storage-sync-files-agent-update-policy.md

Author: prmerger-automator[bot]

articles/storage/file-sync/file-sync-release-notes.md

@@ -5,15 +5,15 @@ services: storage
 author: wmgries
 ms.service: azure-file-storage
 ms.topic: conceptual
-ms.date: 05/08/2024
+ms.date: 06/05/2024
 ms.author: wgries
 ---
 
 # Release notes for Azure File Sync
 
 Azure File Sync enables centralizing your organization's file shares in Azure Files, while keeping the flexibility, performance, and compatibility of a Windows file server. While some users may opt to keep a full copy of their data locally, Azure File Sync additionally has the ability to transform Windows Server into a quick cache of your Azure file share. You can use any protocol that's available on Windows Server to access your data locally, including SMB, NFS, and FTPS. You can have as many caches as you need across the world.
 
-This article provides the release notes for Azure File Sync. It's important to note that major releases of Azure File Sync include service and agent improvements (for example, 15.0.0.0). Minor releases of Azure File Sync are typically for agent improvements (for example, 15.2.0.0).
+This article provides the release notes for Azure File Sync. It's important to note that major releases of Azure File Sync include service and agent improvements (for example, 17.0.0.0). Minor releases of Azure File Sync are typically for agent improvements (for example, 17.2.0.0).
 
 ## Supported versions
 

includes/storage-sync-files-agent-update-policy.md

@@ -2,15 +2,15 @@
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: include
-ms.date: 06/04/2024
+ms.date: 06/05/2024
 ms.author: kendownie
 ---
 The Azure File Sync agent is updated on a regular basis to add new functionality and to address issues. We recommend updating the Azure File Sync agent as new versions are available.
 
 #### Major vs. minor agent versions
 
-* Major agent versions often contain new features and have an increasing number as the first part of the version number. For example: 16.0.0.0
-* Minor agent versions are also called "patches" and are released more frequently than major versions. They often contain bug fixes and smaller improvements but no new features. For example: 16.2.0.0
+* Major agent versions often contain new features and have an increasing number as the first part of the version number. For example: 17.0.0.0
+* Minor agent versions are also called "patches" and are released more frequently than major versions. They often contain bug fixes and smaller improvements but no new features. For example: 17.2.0.0
 
 #### Upgrade paths
 
@@ -62,7 +62,7 @@ To change the current policy setting to the immediate update track, you can use:
 Set-StorageSyncAgentAutoUpdatePolicy -PolicyMode InstallLatest -Day <day> -Hour <hour>
 ```
 > [!NOTE]
-> If flighting has already completed for the latest agent version and the agent auto update policy is set to InstallLatest, the agent will not auto-update until the next agent version is flighted. To update to an agent version that has completed flighting, use Microsoft Update or AfsUpdater.exe. To check if an agent version is currently flighting, check the [supported versions](/azure/storage/file-sync/file-sync-release-notes#supported-versions) section in the release notes.
+> If flighting has already completed for the latest agent version and the agent auto update policy is changed to InstallLatest, the agent will not auto-upgrade until the next agent version is flighted. To update to an agent version that has completed flighting, use Microsoft Update or AfsUpdater.exe. To check if an agent version is currently flighting, check the [supported versions](/azure/storage/file-sync/file-sync-release-notes#supported-versions) section in the release notes.
 
 #### Agent lifecycle and change management guarantees
 
@@ -71,7 +71,7 @@ Azure File Sync is a cloud service which continuously introduces new features an
 - Major agent versions are supported for at least six months from the date of initial release.
 - We guarantee there is an overlap of at least three months between the support of major agent versions.
 - Warnings are issued for registered servers using a soon-to-be expired agent at least three months prior to expiration. You can check if a registered server is using an older version of the agent under the registered servers section of a Storage Sync Service.
-- The lifetime of a minor agent version is bound to the associated major version. For example, when agent version 16.0.0.0 is set to expire, agent versions 16.\*.\*.\* will all be set to expire together.
+- The lifetime of a minor agent version is bound to the associated major version. For example, when agent version 17.0.0.0 is set to expire, agent versions 17.\*.\*.\* will all be set to expire together.
 
 > [!NOTE]
 > Installing an agent version with an expiration warning will display a warning but succeed. Attempting to install or connect with an expired agent version isn't supported and will be blocked.