Skip to content

Commit 8e1fafc

Browse files
Merge pull request #300829 from dlepow/patch-471314
[APIM] Update configure-service-update-settings.md
2 parents 0704e18 + 0c362bb commit 8e1fafc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,15 +15,15 @@ ms.author: danlep
1515

1616
This article shows you how to configure *service update* settings (preview) 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.
1717

18-
You can't control exactly when Azure updates each API Management instance, but in select service tiers you can choose an *update group* for your instance so that it receives updates earlier or later than it usually would during an update rollout. You can also configure a *maintenance window* during the day when you want your instance to receive updates.
18+
You can't control exactly when Azure updates each API Management instance, but in select service tiers you can choose an *update group* (also called a *release channel*) for your instance so that it receives updates earlier or later than it usually would during an update rollout. You can also configure a *maintenance window* during the day when you want your instance to receive updates.
1919

2020
* **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.
2121

2222
Choose from:
2323
* **Early** - Receive updates early in the rollout, for testing and early access to new features. This option is not recommended for production deployments.
2424
* **Default** - Receive updates as part of the regular release rollout. This option is recommended for most services, including production deployments.
2525
* **Late** - Receive updates later than the previous groups, typically weeks after the initial rollout. This option is recommended for mission-critical deployments only.
26-
* **AI Gateway Early** (GenAI release) - Get early access to the latest [AI gateway features and updates](genai-gateway-capabilities.md) before they reach other update groups. Receive other service updates as part of the **Late** rollout group.
26+
* **AI Gateway Early** (GenAI release channel) - Get early access to the latest [AI gateway features and updates](genai-gateway-capabilities.md) before they reach other update groups. Receive other service updates as part of the **Late** rollout group.
2727

2828
> [!NOTE]
2929
> 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.

0 commit comments

Comments
 (0)