Skip to content

Commit 4cd30e4

Browse files
authored
[APIM] Update date and improve clarity in service update behavior
Updated the date and clarified the impact of infrastructure changes on API Management service.
1 parent 76e36f5 commit 4cd30e4

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

includes/api-management-service-update-behavior.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22
author: dlepow
33
ms.service: azure-api-management
44
ms.topic: include
5-
ms.date: 04/18/2025
5+
ms.date: 04/09/2026
66
ms.author: danlep
77
---
88
> [!IMPORTANT]
9-
> Changes to your API Management service's infrastructure (such as configuring custom domains, adding CA certificates, scaling, virtual network configuration, availability zone changes, and region additions) can take 15 minutes or longer to complete, depending on the service tier and the size of the deployment. Expect longer times for an instance with a greater number of scale units or multi-region configuration. Rolling changes to API Management are executed carefully to preserve capacity and availability.
9+
> Changes to your API Management service's infrastructure (such as configuring custom domains, adding CA certificates, scaling, virtual network configuration, availability zone changes, and region additions) can take 15 minutes or longer to complete, depending on the service tier and the size of the deployment. Expect longer times for an instance with a greater number of scale units or multi-region configuration (gateways in multiple locations). Rolling changes to API Management are executed carefully to preserve capacity and availability.
1010
>
1111
> While the service is updating, other service infrastructure changes can't be made. However, you can configure APIs, products, policies, and user settings. The service will **not** experience gateway downtime, and API Management **will continue** to service API requests without interruption (except in the Developer tier).

0 commit comments

Comments
 (0)