review pass

Author: gitName

articles/api-management/configure-service-update-settings.md

@@ -4,32 +4,34 @@ description: Learn how to configure settings for applying service updates to you
 author: dlepow
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 03/18/2025
+ms.date: 04/02/2025
 ms.author: danlep
 ---
 
 # Configure service update settings for your API Management instances 
 
-[!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
+[!INCLUDE [api-management-availability-premium-dev-standard-basic](../../includes/api-management-availability-premium-dev-standard-basic.md)]
 
-This article shows you how to configure service update settings in your API Management instance. Azure periodically applies service updates automatically to API Management instances, using a phased rollout approach. These updates include new features, security enhancements, and reliability improvements. 
+
+This article shows you how to configure *service update* settings in your API Management instance. Azure periodically applies service updates automatically to API Management instances, using a phased rollout approach. These updates include new features, security enhancements, and reliability improvements. 
 
 You can't control exactly when Azure updates each instance, but API Management lets you select an *update group* for your instance, and also a *maintenance window* during the day when you want your instance to receive updates. 
 
-* **Update group** - A set of instances that receive updates during a production rollout, which can take from several days to several weeks. Choose from:
-    * **Early** - Receive updates early. Updates might include preview builds.
-    * **Default** - Receive updates according to the usual phased rollout.
-    * **Late** - Receive updates later. Updates include the most stable builds.
+* **Update group** - A set of instances that receive API Management service updates during a production rollout, which can take from several days to several weeks to complete. 
+
+    Choose from:
+    * **Early** - Receive updates early in the rollout, for testing and early access to new features. This option is not recommended for production deployments.
+    * **Default** - Receive updates as part of the regular release rollout. This option is recommended for most services, including production deployments.
+    * **Late** - Receive updates later than the previous groups, typically weeks after the initial rollout. This option is recommended for mission-critical deployments only.
 
     > [!NOTE]
     > Azure deploys all updates using a [safe deployment practices (SDP) framework](https://azure.microsoft.com/blog/advancing-safe-deployment-practices/). Updates released early in a rollout might be less stable and replaced later by stable releases. All instances are eventually updated to the most stable release builds.
 
-    For example, you might want to add a test instance to the **Early** update group. This instance receives updates before your production instances, which you might put in the **Late** update group. You can monitor the test instance for any issues caused by the updates before they reach your production instances. [Learn more about canary deployments](#canary-deployment-strategies) with API Management
+    For example, you might want to add a test instance to the **Early** update group. This instance receives updates before your production instances, which you put in the **Default** or **Late** update group. You can monitor the test instance for any issues caused by the updates before they reach your production instances. [Learn more about canary deployments](#canary-deployment-strategies) with API Management
 
  * **Maintenance window** - An 8-hour daily period when you want your instance to receive updates. By default, the maintenance window is 10 PM to 6 AM in the instance's timezone. 
 
-    Service disruptions are rare during an update, but you might want to reduce risk by selecting times of low service use. For example, set a maintenance window during weekday evenings and weekend mornings for your production instances. 
-
+    Service disruptions are rare during an update, but you might want to reduce risk by selecting times of low service use. For example, for production instances, set a maintenance window during weekday evenings and weekend mornings. 
 
 ## Configure service update settings
 
@@ -53,7 +55,7 @@ Here's how to know about service updates that are expected or are in progress.
 
     To receive notifications automatically, [set up an alert](/azure/azure-monitor/alerts/alerts-activity-log) on the Activity log.
 
-* Updates roll out to regions in the following phases: Azure EUAP regions, followed by West Central US, followed by remaining regions in several later phases. The sequence of regions updated in the later deployment phases differs from service to service. You can expect at least 24 hours between each phase of the production rollout.
+* By default, updates roll out to regions in the following phases: Azure EUAP regions, followed by West Central US, followed by remaining regions in several later phases. The sequence of regions updated in the later deployment phases differs from service to service. You can expect at least 24 hours between each phase of the production rollout.
 
 * Within a region, API Management instances in the Premium tier receive updates several hours later than those in other service tiers.
 
@@ -62,9 +64,9 @@ Here's how to know about service updates that are expected or are in progress.
 
 ## Canary deployment strategies
 
-Here are example strategies to use an API Management instance as a canary deployment that receives updates earlier than your production instances.
+You can use an API Management instances assigned to a specific update group or deployed in a specific Azure region as a canary deployment that receives updates earlier than your production instances.
 
-* **Add instance to Early update group** - Use an API Management instance in the Early update group to validate updates early in the production pipeline. This instance is effectively your canary deployment. 
+* **Add instance to Early update group** - Use an API Management instance in the Early update group to validate updates early in a production rollout. This instance is effectively your canary deployment. 
 
 * **Deploy in canary region** - If you have access to an Azure EUAP region, use an instance there to validate updates as soon as they're released to the production pipeline. Learn about the [Azure region access request process](/troubleshoot/azure/general/region-access-request-process).