Merge pull request #295989 from MicrosoftDocs/main

3/7/2025 PM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -5450,6 +5450,11 @@
       "redirect_url": "/azure/virtual-wan/virtual-wan-about",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/virtual-wan/azure-vpn-client-optional-configurations-windows.md",
+      "redirect_url": "/azure/virtual-wan/azure-vpn-client-optional-configurations",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/virtual-wan/openvpn-azure-ad-client.md",
       "redirect_url": "/azure/virtual-wan/point-to-site-entra-vpn-client-windows",

articles/api-management/set-edit-policies.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 10/18/2023
+ms.date: 03/06/2025
 ms.author: danlep
 ---
 

articles/api-management/transform-api.md

@@ -155,6 +155,8 @@ The rest of this section tests policy transformations that you set in this artic
 
 1. Wait for 15 seconds or more and then select **Send** again. This time you should get a **200 OK** response.
 
+[!INCLUDE [api-management-policies-azure-copilot](../../includes/api-management-policies-azure-copilot.md)]
+
 ## Summary
 
 In this tutorial, you learned how to:

articles/app-service/environment/app-service-app-service-environment-custom-settings.md

@@ -16,10 +16,6 @@ ms.custom: mvc, devx-track-arm-template
 
 Because App Service Environments are isolated to a single customer, there are certain configuration settings that can be applied exclusively to App Service Environments. This article documents the various specific customizations that are available for App Service Environments.
 
-> [!NOTE]
-> This article covers the features, benefits, and use cases of App Service Environment v3, which is used with App Service Isolated v2 plans.
->
-
 If you do not have an App Service Environment, see [How to Create an App Service Environment v3](./creation.md).
 
 You can store App Service Environment customizations by using an array in the new **clusterSettings** attribute. This attribute is found in the "Properties" dictionary of the *hostingEnvironments* Azure Resource Manager entity.

articles/app-service/environment/auto-migration.md

@@ -10,29 +10,19 @@ ms.custom: references_regions
 # Prevent and resolve issues caused by an auto-migration of an App Service Environment
 
 > [!IMPORTANT]
-> App Service Environment v1 and v2 are retired and no longer supported. If you have an App Service Environment v1 or v2, you must migrate to App Service Environment v3. For more information, see [Upgrade to App Service Environment v3](upgrade-to-asev3.md).
+> App Service Environment v1 and v2 are retired and no longer supported.
 >
-> Auto-migrations are migrations that are initiated by Microsoft. As of September 1, 2024, the platform will attempt to auto-migrate any remaining App Service Environment v1 and v2 on a best-effort basis using the [in-place migration feature](migrate.md), but Microsoft makes no claim or guarantees about application availability after auto-migration. You may need to perform manual configuration to complete the migration and to optimize your App Service plan SKU choice to meet your needs. If auto-migration is not feasible, your resources and associated app data will be deleted. We strongly urge you to act now to avoid either of these extreme scenarios.
+> Auto-migrations are migrations that are initiated by Microsoft. As of September 1, 2024, the platform auto-migrated any remaining App Service Environment v1 and v2 on a best-effort basis using the [in-place migration feature](migrate.md), but Microsoft makes no claim or guarantees about application availability after auto-migration. You may need to perform manual configuration to complete the migration and to optimize your App Service plan SKU choice to meet your needs. If auto-migration is not feasible, your resources and associated app data were deleted.
 >
 
 If you have an App Service Environment v1 or v2 that was auto-migrated to App Service Environment v3, you might encounter issues with your apps or services. This article provides guidance on how to address these issues.
 
 ## Overview
 
-After September 1, 2024, all App Service Environments v1 and v2 are eligible to be automatically migrated (auto-migrated) to App Service Environment v3 at any given time unless otherwise stated. The platform initiates auto-migrations, which are necessary to ensure that your App Service Environment is running on a supported platform.
-
-> [!NOTE]
-> Auto-migrations and deletions are done in batches. If your App Service Environment isn't auto-migrated yet, it's subject to auto-migration or deletion at any time.
->
+After September 1, 2024, all App Service Environments v1 and v2 were automatically migrated (auto-migrated) to App Service Environment v3. The platform initiated auto-migrations, which are necessary to ensure that your App Service Environment is running on a supported platform.
 
 Auto-migrations are done using the [in-place migration feature](migrate.md). There's about one hour of downtime during the migration process. The inbound and outbound IP addresses of your App Service Environment might change during the migration process. Downtime might be longer if you have dependencies on these IP addresses. Downtime might also be longer if you use features that aren't supported in App Service Environment v3.
 
-## Grace period
-
-> [!NOTE]
-> As of January 1, 2025, grace periods aren't available. Migrate immediately or open a support ticket to discuss your options.
->
-
 ## Auto-migration limitations
 
 Auto-migrations are done using the [in-place migration feature](migrate.md). The following limitations apply to auto-migrations, similar to the [limitations of in-place migrations](migrate.md#in-place-migration-feature-limitations):
@@ -188,8 +178,6 @@ We encourage you to complete migration to Azure App Service Environment v3 as so
 
 ## Frequently asked questions
 
-- **Why am I experiencing temporary application outages on my App Service Environment v1/v2?**  
-  The Azure platform is preparing for the retirement of Cloud Services (Classic), which is the infrastructure that App Service Environment v1 and v2 run on. As part of this preparation, you should expect temporary outages and service disruptions. To minimize the effect of these disruptions, we recommend that you migrate to App Service Environment v3 as soon as possible.
 - **Why was my App Service Environment auto-migrated?**  
   App Service Environment v1 and v2 are retired and no longer supported. The supporting infrastructure for App Service Environment v1 and v2 is being decommissioned. To ensure that your App Service Environment is running on a supported platform, Microsoft initiates auto-migrations to App Service Environment v3.
 - **Why are my apps not working after auto-migration?**  

articles/app-service/environment/configure-network-settings.md

@@ -14,9 +14,6 @@ ms.author: madsd
 
 Because App Service Environments are isolated to the individual customer, there are certain configuration settings that can be applied exclusively to App Service Environments. This article documents the various specific network customizations that are available for App Service Environment v3.
 
-> [!NOTE]
-> This article is about App Service Environment v3, which is used with isolated v2 App Service plans.
-
 If you don't have an App Service Environment, see [How to Create an App Service Environment v3](./creation.md).
 
 App Service Environment network customizations are stored in a subresource of the *hostingEnvironments* Azure Resource Manager entity called networking.

articles/app-service/environment/creation.md

@@ -11,9 +11,6 @@ ms.author: madsd
 
 [App Service Environment][Intro] is a single-tenant deployment of Azure App Service. You use it with an Azure virtual network. You need one subnet for a deployment of App Service Environment, and this subnet can't be used for anything else. 
 
-> [!NOTE]
-> This article is about App Service Environment v3, which is used with Isolated v2 App Service plans.
-
 ## Before you create your App Service Environment
 
 After you create your App Service Environment, you can't change any of the following:

articles/app-service/environment/how-to-create-from-template.md

@@ -11,9 +11,6 @@ ms.author: madsd
 
 App Service Environment can be created using an Azure Resource Manager template allowing you to do repeatable deployment.
 
-> [!NOTE]
-> This article is about App Service Environment v3, which is used with Isolated v2 App Service plans.
-
 ## Overview
 
 Azure App Service Environment can be created with an internet-accessible endpoint or an endpoint on an internal address in an Azure Virtual Network. When created with an internal endpoint, that endpoint is provided by an Azure component called an internal load balancer (ILB). The App Service Environment on an internal IP address is called an ILB ASE. The App Service Environment with a public endpoint is called an External ASE. 

articles/app-service/environment/how-to-custom-domain-suffix.md

@@ -15,10 +15,6 @@ An App Service Environment is an Azure App Service feature that provides a fully
 
 If you don't have an App Service Environment, see [How to Create an App Service Environment v3](./creation.md).
 
-> [!NOTE]
-> This article covers the features, benefits, and use cases of App Service Environment v3, which is used with App Service Isolated v2 plans.
-> 
-
 The custom domain suffix defines a root domain used by the App Service Environment. In the public variation of Azure App Service, the default root domain for all web apps is *azurewebsites.net*. For ILB App Service Environments, the default root domain is *appserviceenvironment.net*. However, since an ILB App Service Environment is internal to a customer's virtual network, customers can use a root domain in addition to the default one that makes sense for use within a company's internal virtual network. For example, a hypothetical Contoso Corporation might use a default root domain of *internal.contoso.com* for apps that are intended to only be resolvable and accessible within Contoso's virtual network. An app in this virtual network could be reached by accessing *APP-NAME.internal.contoso.com*.
 
 The custom domain suffix is for the App Service Environment. This feature is different from a custom domain binding on an App Service. For more information on custom domain bindings, see [Map an existing custom DNS name to Azure App Service](../app-service-web-tutorial-custom-domain.md).

articles/app-service/environment/how-to-upgrade-preference.md

@@ -14,10 +14,6 @@ Azure App Service is regularly updated to provide new features, new runtime vers
 
 If you don't have an App Service Environment, see [How to Create an App Service Environment v3](./creation.md).
 
-> [!NOTE]
-> This article covers the features, benefits, and use cases of App Service Environment v3, which is used with App Service Isolated v2 plans.
-> 
-
 With App Service Environment v3, you can specify your preference for when and how the planned maintenance is applied. The upgrade can be applied automatically or manually. Even with your preference set to automatic, you have some options to influence the timing.
 
 ## Automatic upgrade preference