In progress.

TimShererWithAquent · TimShererWithAquent · commit ddc33fb1076e · 2025-05-28T07:43:07.000-07:00
diff --git a/articles/app-service/app-service-ip-restrictions.md b/articles/app-service/app-service-ip-restrictions.md
@@ -13,8 +13,6 @@ ms.assetid: 3be1f4bd-8a81-4565-8a56-528c037b24bd
 ---
 # Set up Azure App Service access restrictions
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 When you set up access restrictions, you can define a priority-ordered allow/deny list that controls network access to your app. The list can include IP addresses or Azure Virtual Network subnets. When there are one or more entries, an implicit *deny all* exists at the end of the list. For more information, see [Azure App Service access restrictions](./overview-access-restrictions.md).
 
 The access restriction capability works with all Azure App Service-hosted workloads. The workloads can include web apps, API apps, Linux apps, Linux custom containers, and Azure Functions apps.
diff --git a/articles/app-service/app-service-key-vault-references.md b/articles/app-service/app-service-key-vault-references.md
@@ -14,8 +14,6 @@ ms.custom: AppServiceConnectivity
 
 This article shows you how to use secrets from Azure Key Vault as values of [app settings](configure-common.md#configure-app-settings) or [connection strings](configure-common.md#configure-connection-strings) in your Azure App Service or Azure Functions apps.
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 [Key Vault](/azure/key-vault/general/overview) is a service that provides centralized secrets management, with full control over access policies and audit history. When an app setting or connection string is a Key Vault reference, your application code can use it like any other app setting or connection string. This way, you can maintain secrets apart from your app's configuration. App settings are securely encrypted at rest, but if you need capabilities for managing secrets, they should go into a key vault.
 
 ## Grant your app access to a key vault
diff --git a/articles/app-service/app-service-plan-manage.md b/articles/app-service/app-service-plan-manage.md
@@ -12,8 +12,6 @@ ms.custom: "UpdateFrequency3"
 ---
 # Manage an App Service plan in Azure
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 An [Azure App Service plan](overview-hosting-plans.md) provides the resources that an App Service app needs to run. This guide shows how to manage an App Service plan.
 
 ## Create an App Service plan
diff --git a/articles/app-service/app-service-web-tutorial-custom-domain.md b/articles/app-service/app-service-web-tutorial-custom-domain.md
@@ -13,8 +13,6 @@ author: msangapu-msft
 
 # Set up an existing custom domain in Azure App Service
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 [Azure App Service](overview.md) provides a highly scalable, self-patching web hosting service. This guide shows you how to map an existing custom Domain Name System (DNS) name to App Service. To migrate a live site and its DNS domain name to App Service with no downtime, see [Migrate an active DNS name to Azure App Service](manage-custom-dns-migrate-domain.md).
 
 The DNS record type you need to add with your domain provider depends on the domain you want to add to App Service.
diff --git a/articles/app-service/configure-authentication-provider-aad.md b/articles/app-service/configure-authentication-provider-aad.md
@@ -12,8 +12,6 @@ ms.author: cephalin
 
 # Configure your App Service or Azure Functions app to use Microsoft Entra sign-in
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 Select another authentication provider to jump to it.
 
 [!INCLUDE [app-service-mobile-selector-authentication](../../includes/app-service-mobile-selector-authentication.md)]
diff --git a/articles/app-service/configure-common.md b/articles/app-service/configure-common.md
@@ -16,8 +16,6 @@ ms.author: cephalin
 
 This article explains how to configure common settings for web apps, a mobile back end, or an API app. For Azure Functions, see [App settings reference for Azure Functions](../azure-functions/functions-app-settings.md).
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 ## Configure app settings
 
 In Azure App Service, app settings are variables passed as environment variables to the application code. The following conditions apply to app settings:
diff --git a/articles/app-service/configure-ssl-certificate.md b/articles/app-service/configure-ssl-certificate.md
@@ -13,8 +13,6 @@ author: msangapu-msft
 
 # Add and manage TLS/SSL certificates in Azure App Service
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 You can add digital security certificates to [use in your application code](configure-ssl-certificate-in-code.md) or to [help secure custom DNS names](configure-ssl-bindings.md) in [Azure App Service](overview.md), which provides a highly scalable, self-patching web hosting service. Currently called Transport Layer Security (TLS) certificates, also previously known as Secure Socket Layer (SSL) certificates, these private or public certificates help you secure internet connections by encrypting data sent between your browser, websites that you visit, and the website server.
 
 The following table lists the options for you to add certificates in App Service:
diff --git a/articles/app-service/deploy-azure-pipelines.md b/articles/app-service/deploy-azure-pipelines.md
@@ -14,8 +14,6 @@ ms.custom: "devops-pipelines-deploy"
 
 **Azure DevOps Services | Azure DevOps Server 2020 | Azure DevOps Server 2019**
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 Use [Azure Pipelines](/azure/devops/pipelines/) to automatically deploy your web app to [Azure App Service](./overview.md) on every successful build. Azure Pipelines lets you build, test, and deploy with continuous integration and continuous delivery (CI/CD) by using [Azure DevOps](/azure/devops/).
 
 YAML pipelines are defined by using a YAML file in your repository. A step is the smallest building block of a pipeline and can be a script or task (prepackaged script). [Learn about the key concepts and components that make up a pipeline](/azure/devops/pipelines/get-started/key-pipelines-concepts).
diff --git a/articles/app-service/deploy-best-practices.md b/articles/app-service/deploy-best-practices.md
@@ -13,8 +13,6 @@ ms.author: cephalin
 
 # Deployment best practices
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 Every development team has unique requirements that can make implementing an efficient deployment pipeline difficult on any cloud service. This article introduces the three main components of deploying to Azure App Service: *deployment sources*, *build pipelines*, and *deployment mechanisms*. This article also covers some best practices and tips for specific language stacks.
 
 ## Deployment components
diff --git a/articles/app-service/deploy-continuous-deployment.md b/articles/app-service/deploy-continuous-deployment.md
@@ -11,8 +11,6 @@ ms.assetid: 6adb5c84-6cf3-424e-a336-c554f23b4000
 
 # Configure continuous deployment to Azure App Service
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 You can configure continuous deployment from [GitHub](https://help.github.com/articles/create-a-repo), [Bitbucket](https://confluence.atlassian.com/get-started-with-bitbucket/create-a-repository-861178559.html), and [Azure](/azure/devops/repos/git/creatingrepo) repositories by using [Azure App Service](overview.md), which pulls in the latest updates. This guide provides you with everything you need to get started.
 
 [!INCLUDE [Prepare repository](../../includes/app-service-deploy-prepare-repo.md)]
diff --git a/articles/app-service/deploy-staging-slots.md b/articles/app-service/deploy-staging-slots.md
@@ -14,8 +14,6 @@ ai-usage: ai-assisted
 # Set up staging environments in Azure App Service
 <a name="Overview"></a>
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 When you deploy your web app, web app on Linux, mobile back end, or API app to [Azure App Service](./overview.md), you can use a separate deployment slot instead of the default production slot. This approach is available if you run in the Standard, Premium, or Isolated tier of an App Service plan. Deployment slots are live apps with their own host names. App content and configuration elements can be swapped between two deployment slots, including the production slot.
 
 Deploying your application to a nonproduction slot has the following benefits:
diff --git a/articles/app-service/deploy-zip.md b/articles/app-service/deploy-zip.md
@@ -12,8 +12,6 @@ ms.custom: devx-track-azurecli
 
 # Deploy files to Azure App Service
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 This article shows you how to deploy your code as a ZIP, WAR, JAR, or EAR package to [Azure App Service](overview.md). It also shows you how to deploy individual files to App Service, separate from your application package.
 
 ## Prerequisites
diff --git a/articles/app-service/monitor-instances-health-check.md b/articles/app-service/monitor-instances-health-check.md
@@ -11,8 +11,6 @@ ms.author: msangapu
 
 # Monitor App Service instances by using Health check
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 This article describes how to use Health check in the Azure portal to monitor App Service instances. Health check increases your application's availability by rerouting requests away from unhealthy instances and replacing instances if they remain unhealthy. It does that by pinging your web application every minute, via a path that you choose.
 
 ![Diagram that shows how Health check works.][1]
diff --git a/articles/app-service/overview-authentication-authorization.md b/articles/app-service/overview-authentication-authorization.md
@@ -14,8 +14,6 @@ ms.author: cephalin
 
 Azure App Service provides built-in authentication (signing in users) and authorization (providing access to secure data) capabilities. These capabilities are sometimes called *Easy Auth*. You can use them to sign in users and access data by writing little or no code in your web app, RESTful API, mobile server, and [functions](../azure-functions/functions-overview.md).
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 This article describes how App Service helps simplify authentication and authorization for your app.
 
 ## Reasons to use built-in authentication
