Merge pull request #298874 from MicrosoftDocs/main

4/25/2025 AM Publish

Author: Albertyang0

articles/api-management/TOC.yml

@@ -80,7 +80,6 @@
       href: configure-custom-domain.md
     - name: Use an external cache
       href: api-management-howto-cache-external.md
-    - name: Migrate from stv1 to stv2 platform
     - name: Configure update settings
       href: configure-service-update-settings.md
     - name: Move instances between regions

articles/api-management/api-management-howto-autoscale.md

@@ -24,6 +24,8 @@ The article walks through the process of configuring autoscale and suggests opti
 > * An API Management service in the **Consumption** tier scales automatically based on the traffic - without any additional configuration needed.
 > * Currently, autoscale is not supported for the [workspace gateway](workspaces-overview.md#workspace-gateway) in API Management workspaces.
 
+[!INCLUDE [api-management-service-update-behavior](../../includes/api-management-service-update-behavior.md)]
+
 ## Prerequisites
 
 To follow the steps from this article, you must:
@@ -38,7 +40,6 @@ To follow the steps from this article, you must:
 Certain limitations and consequences of scaling decisions need to be considered before configuring autoscale behavior.
 
 + The [pricing tier](api-management-features.md) of your API Management instance determines the [maximum number of units](upgrade-and-scale.md#upgrade-and-scale) you may scale to. For example, the **Standard tier** can be scaled to 4 units. You can add any number of units to the **Premium** tier.
-+ The scaling process takes at least 20 minutes.
 + If the service is locked by another operation, the scaling request will fail and retry automatically.
 + If your service instance is deployed in multiple regions (locations), only units in the **Primary location** can be autoscaled with Azure Monitor autoscale. Units in other locations can only be scaled manually.
 + If your service instance is configured with [availability zones](zone-redundancy.md) in the **Primary location**, be aware of the number of zones when configuring autoscaling. The number of API Management units in autoscale rules and limits must be a multiple of the number of zones. 
@@ -73,7 +74,7 @@ Follow these steps to configure autoscale for an Azure API Management service:
     |*Action*              |                   |                                                                                                                                                                                                                                                                                 |
     | Operation             | Increase count by |                                                                                                                                                                                                                                                                                 |
     | Instance count        | 1                 | Scale out the Azure API Management instance by 1 unit.                                                                                                                                                                                                                          |
-    | Cool down (minutes)   | 60                | It takes at least 20 minutes for the API Management service to scale out. In most cases, the cool down period of 60 minutes prevents from triggering many scale-outs.                                                                                                  |
+    | Cool down (minutes)   | 60                | In most cases, the cool down period of 60 minutes prevents from triggering many scale-outs.                                                                                                  |
 
 1. Select **Add** to save the rule.
 1. To add another rule, select **Add a rule**.

articles/api-management/api-management-howto-ca-certificates.md

@@ -42,8 +42,7 @@ Follow the steps below to upload a new CA certificate. If you have not created a
 1. Select **Save**. This operation may take a few minutes.
 
 > [!NOTE]
-> - The process of assigning the certificate might take 15 minutes or more depending on the size of the deployment. The Developer SKU has downtime during the process. The Basic and higher SKUs don't have downtime during the process.
-> - You can also upload a CA certificate using the `New-AzApiManagementSystemCertificate` PowerShell command.
+> You can also upload a CA certificate using the `New-AzApiManagementSystemCertificate` PowerShell command.
 
 ## <a name="step1a"> </a>Delete a CA certificate
 

articles/api-management/api-management-howto-deploy-multi-region.md

@@ -23,9 +23,12 @@ When adding a region, you configure:
 
 * [Virtual network](virtual-network-concepts.md) settings in the added region, if networking is configured in the existing region or regions.
 
->[!IMPORTANT]
+> [!IMPORTANT]
 > The feature to enable storing customer data in a single region is currently only available in the Southeast Asia Region (Singapore) of the Asia Pacific Geo. For all other regions, customer data is stored in Geo.
 
+[!INCLUDE [api-management-service-update-behavior](../../includes/api-management-service-update-behavior.md)]
+
+
 ## About multi-region deployment
 
 [!INCLUDE [api-management-multi-region-concepts](../../includes/api-management-multi-region-concepts.md)]

articles/api-management/api-management-howto-disaster-recovery-backup-restore.md

@@ -34,6 +34,9 @@ This article shows how to automate backup and restore operations of your API Man
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
+[!INCLUDE [api-management-service-update-behavior](../../includes/api-management-service-update-behavior.md)]
+
+
 ## Prerequisites
 
 * An API Management service instance. If you don't have one, see [Create an API Management service instance](get-started-create-service-instance.md).
@@ -291,8 +294,6 @@ Restore-AzApiManagement -ResourceGroupName $apiManagementResourceGroup -Name $ap
     -SourceBlobName $blobName -AccessType "UserAssignedManagedIdentity" ` -identityClientId $identityid
 ```
 
-Restore is a long-running operation that may take up to 45 minutes or more to complete. 
-
 ### [CLI](#tab/cli)
 
 In the following examples, 
@@ -320,8 +321,6 @@ az apim restore --resource-group $apiManagementResourceGroup --name $apiManageme
     --storage-account-name $storageAccountName --storage-account-key $storageKey --storage-account-container $containerName --backup-name $backupName
 ```
 
-Restore is a long-running operation that may take up to 45 minutes or more to complete. 
-
 ### [REST](#tab/rest)
 
 To restore an API Management service from a previously created backup, make the following HTTP request:
@@ -380,7 +379,7 @@ In the body of the request, specify the existing storage account name, blob cont
 
 Set the value of the `Content-Type` request header to `application/json`.
 
-Restore is a long-running operation that may take up to 30 or more minutes to complete. If the request succeeded and the restore process began, you receive a `202 Accepted` response status code with a `Location` header. Make `GET` requests to the URL in the `Location` header to find out the status of the operation. While the restore is in progress, you continue to receive a `202 Accepted` status code. A response code of `200 OK` indicates successful completion of the restore operation.
+Restore is a long-running operation that may take several minutes to complete. If the request succeeded and the restore process began, you receive a `202 Accepted` response status code with a `Location` header. Make `GET` requests to the URL in the `Location` header to find out the status of the operation. While the restore is in progress, you continue to receive a `202 Accepted` status code. A response code of `200 OK` indicates successful completion of the restore operation.
 
 ---
 

articles/api-management/api-management-using-with-internal-vnet.md

@@ -40,6 +40,8 @@ For configurations specific to the *external* mode, where the API Management end
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
+[!INCLUDE [api-management-service-update-behavior](../../includes/api-management-service-update-behavior.md)]
+
 [!INCLUDE [api-management-virtual-network-prerequisites](../../includes/api-management-virtual-network-prerequisites.md)]
 
 ## Enable VNet connection
@@ -59,8 +61,6 @@ For configurations specific to the *external* mode, where the API Management end
 1. Continue configuring VNet settings for the remaining locations of your API Management instance.
 1. In the top navigation bar, select **Save**.
 
-    It can take 15 to 45 minutes to update the API Management instance. The Developer tier has downtime during the process. The Basic and higher SKUs don't have downtime during the process.
-
 After successful deployment, you should see your API Management service's **private** virtual IP address and **public** virtual IP address on the **Overview** blade. For more information about the IP addresses, see [Routing](#routing) in this article.
 
 :::image type="content" source="media/api-management-using-with-internal-vnet/api-management-internal-vnet-dashboard.png" alt-text="Public and private IP addressed in Azure portal"::: 

articles/api-management/api-management-using-with-vnet.md

@@ -26,6 +26,8 @@ For configurations specific to the *internal* mode, where the endpoints are acce
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
+[!INCLUDE [api-management-service-update-behavior](../../includes/api-management-service-update-behavior.md)]
+
 [!INCLUDE [api-management-virtual-network-prerequisites](../../includes/api-management-virtual-network-prerequisites.md)]
 
 ## Enable VNet connection
@@ -49,9 +51,7 @@ For configurations specific to the *internal* mode, where the endpoints are acce
 
 1. Continue configuring VNet settings for the remaining locations of your API Management instance.
 
-7. In the top navigation bar, select **Save**.
-
-It can take 15 to 45 minutes to update the API Management instance. Instances in the Developer tier have downtime during the process. Instances in the Premium tier don't have downtime during the process. 
+1. In the top navigation bar, select **Save**.
 
 ### Enable connectivity using a Resource Manager template (`stv2` compute platform)
 

articles/api-management/configure-custom-domain.md

@@ -27,6 +27,8 @@ When you create an Azure API Management service instance in the Azure cloud, Azu
 > [!NOTE]
 > Currently, custom domain names aren't supported in a [workspace gateway](workspaces-overview.md#workspace-gateway).
 
+[!INCLUDE [api-management-service-update-behavior](../../includes/api-management-service-update-behavior.md)]
+
 ## Prerequisites
 
 -   An API Management instance. For more information, see [Create an Azure API Management instance](get-started-create-service-instance.md).
@@ -167,11 +169,6 @@ Choose the steps according to the [domain certificate](#domain-certificate-optio
 1. Select **Add**, or select **Update** for an existing endpoint.
 1. Select **Save**.
 
-> [!NOTE]
-> The process of assigning the certificate may take 15 minutes or more depending on size of deployment. Developer tier has downtime, while Basic and higher tiers do not.
-
-
-
 ---
 
 ## DNS configuration

articles/api-management/upgrade-and-scale.md

@@ -26,6 +26,9 @@ The throughput and price of each unit depend on the [service tier](api-managemen
 > [!NOTE]
 > See [API Management pricing](https://azure.microsoft.com/pricing/details/api-management/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio) for features, scale limits, and estimated throughput in each tier. To get more accurate throughput numbers, you need to look at a realistic scenario for your APIs. See [Capacity of an Azure API Management instance](api-management-capacity.md).
 
+[!INCLUDE [api-management-service-update-behavior](../../includes/api-management-service-update-behavior.md)]
+
+
 ## Prerequisites
 
 To follow the steps from this article, you must:
@@ -53,8 +56,6 @@ You can choose between the following dedicated tiers: **Developer**, **Basic**,
 
     Downgrading can remove some features. For example, downgrading to **Standard** or **Basic** from the **Premium** tier can remove virtual networks or multi-region deployment.
 
-> [!NOTE]
-> The upgrade or scale process can take up to 15 to 45 minutes to apply. You get notified when it is done.
 
 ## Scale your API Management instance
 

articles/app-service/configure-language-dotnet-framework.md

@@ -37,6 +37,8 @@ For CLR 2 runtime versions (.NET Framework 3.5 and below):
 ls "D:\Program Files (x86)\Reference Assemblies\Microsoft\Framework"
 ```
 
+If the runtime your application requires isn't supported, you can deploy it with a custom container.
+
 ## Show current .NET Framework runtime version
 
 Run the following command in the [Cloud Shell](https://shell.azure.com):
@@ -55,6 +57,8 @@ By default, App Service uses the latest supported .NET Framework version to run
 az webapp config set --resource-group <resource-group-name> --name <app-name> --net-framework-version v2.0
 ```
 
+[!INCLUDE [outdated-runtimes](includes/outdated-runtimes.md)]
+
 ## Access environment variables
 
 In App Service, you can [set app settings](configure-common.md#configure-app-settings) and connection strings outside of your app code. Then you can access them in any class using the standard ASP.NET pattern: