Grace edits

Author: khdownie

articles/storage/file-sync/file-sync-throttling.md

@@ -1,21 +1,21 @@
 ---
 title: Azure File Sync Throttling Limits
-description: Understand how Azure File Sync integrates with Azure Throttling Service (ATS) to implement throttling on key APIs to protect against unexpected load surges.
+description: Understand how Azure File Sync implements throttling on key APIs for individual resources and within a storage sync service.
 author: khdownie
 ms.service: azure-file-storage
-ms.topic: how-to
-ms.date: 10/15/2025
+ms.topic: concept-article
+ms.date: 10/21/2025
 ms.author: kendownie
 # Customer intent: "As an IT administrator, I want to understand Azure File Sync throttling behavior so I can avoid throttling and maintain optimal performance for my file shares."
 ---
 
 # Understand Azure File Sync throttling
 
-Azure File Sync now integrates with Azure Throttling Service (ATS) to implement throttling on key APIs to protect against unexpected load surges. This article explains how throttling works for Azure File Sync, and lists the throttling limits.
+Azure File Sync now implements throttling on key APIs. This article explains how throttling works for Azure File Sync, and lists the throttling limits.
 
 ## Azure Resource Manager (ARM) throttling behavior
 
-Azure Resource Manager [implements throttling](/azure/azure-resource-manager/management/request-limits-and-throttling) at two levels: subscription and tenant. This is done to manage the number of requests made to Azure services, ensuring fair usage and preventing overloading. If requests are within the limits for these levels, they are routed to the resource provider.
+Azure Resource Manager [implements throttling](/azure/azure-resource-manager/management/request-limits-and-throttling) at two levels: subscription and tenant. If requests are within the limits for these levels, they are routed to the resource provider.
 
 ## Azure File Sync throttling behavior
 
@@ -27,8 +27,6 @@ Azure File Sync enforces throttling in two ways:
 
 - **Using the storage sync service resource as a scope.** Excessive operations across resources within a storage sync service will result in a temporary block on all resources under that service until the enforcement period expires.
 
-By throttling in this manner, we can better control consumption of our APIs to protect customers from potential outages.
-
 ## Per-resource limits
 
 The following table lists the per-resource limits for Azure File Sync.
@@ -40,9 +38,6 @@ The following table lists the per-resource limits for Azure File Sync.
 | DELETE requests                            | Deleting a server endpoint                                               | 12    | 3 minutes         | 4 tokens/min     |
 | GET requests                               | Browsing a server endpoint resource in the Azure portal                  | 400   | 3 minutes         | ~2 tokens/s      |
 | GET list requests                          | Browsing the list of server endpoints under a sync group in the Azure portal | 1,800  | 3 minutes         | ~10 tokens/s     |
-| Cloud endpoint trigger change detection request\* | Triggering change detection on a specific cloud endpoint                 | 5     | 30 minutes        | 1 per 6 mins     |
-
-\*The trigger change detection feature for cloud endpoints is powerful, but also resource-intensive. Running it too often can degrade performance and even cancel previous operations. For this reason, we’ve set a specific limit to ensure the system has enough time to process each change detection request.
 
 ## Storage sync service limits
 
@@ -62,7 +57,7 @@ The following are common questions about throttling in Azure File Sync.
 
 ### What's the reasoning behind these limits?
 
-Most customers only run a few PUT/PATCH/DELETE operations at a time, such as setting up resources or adjusting settings. That’s why limits on actions like creating, updating, or deleting resources are set fairly low. This helps prevent accidental overloads and keeps the service running smoothly.
+Most customers only run a few PUT/PATCH/DELETE operations at a time, such as setting up resources or adjusting settings. That’s why limits on actions like creating, updating, or deleting resources are set fairly low.
 
 ### Do I need to worry about day-to-day operations like browsing and reading files?