Merge pull request #276433 from cephalin/dnl

v-regandowner · web-flow · commit 9eeaf8a40c89 · 2024-05-31T12:12:01.000-04:00
Dnl
diff --git a/articles/app-service/app-service-ip-restrictions.md b/articles/app-service/app-service-ip-restrictions.md
@@ -11,6 +11,8 @@ ms.author: madsd
 ---
 # Set up Azure App Service access restrictions
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 By setting 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. To learn more about access restrictions, go to the [access restrictions overview](./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 Functions.
diff --git a/articles/app-service/app-service-key-vault-references.md b/articles/app-service/app-service-key-vault-references.md
@@ -11,6 +11,8 @@ ms.custom: AppServiceConnectivity
 
 # Use Key Vault references as app settings in Azure App Service and Azure Functions
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 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 App Service or Azure Functions apps. 
 
 [Azure Key Vault](../key-vault/general/overview.md) 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 secret management capabilities, they should go into a key vault.
diff --git a/articles/app-service/app-service-plan-manage.md b/articles/app-service/app-service-plan-manage.md
@@ -12,6 +12,8 @@ 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,6 +13,8 @@ author: msangapu-msft
 
 # Map an existing custom DNS name to 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](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.
@@ -108,7 +110,7 @@ Create two records according to the following table:
 
 | Record type | Host | Value | Comments |
 | - | - | - |
-| CNAME | `<subdomain>` (for example, `www`) | `<app-name>.azurewebsites.net` | The domain mapping itself. |
+| CNAME | `<subdomain>` (for example, `www`) | `<app-name>.azurewebsites.net` (see [note at top](#dnl-note)) | The domain mapping itself. |
 | TXT | `asuid.<subdomain>` (for example, `asuid.www`) | The domain verification ID shown in the **Add custom domain** dialog. | App Service accesses the `asuid.<subdomain>` TXT record to verify your ownership of the custom domain. |
 
 ![Screenshot that shows the portal navigation to an Azure app.](./media/app-service-web-tutorial-custom-domain/cname-record.png)
@@ -119,7 +121,7 @@ For a wildcard name like `*` in `*.contoso.com`, create two records according to
 
 | Record type | Host | Value | Comments |
 | - | - | - | - |
-| CNAME | `*` | `<app-name>.azurewebsites.net` | The domain mapping itself. |
+| CNAME | `*` | `<app-name>.azurewebsites.net` (see [note at top](#dnl-note)) | The domain mapping itself. |
 | TXT | `asuid` | The domain verification ID shown in the **Add custom domain** dialog. | App Service accesses the `asuid` TXT record to verify your ownership of the custom domain. |
 
 ![Screenshot that shows the navigation to an Azure app.](./media/app-service-web-tutorial-custom-domain/cname-record-wildcard.png)
diff --git a/articles/app-service/configure-authentication-provider-aad.md b/articles/app-service/configure-authentication-provider-aad.md
@@ -11,6 +11,8 @@ 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
@@ -12,6 +12,8 @@ ms.author: cephalin
 ---
 # Configure an App Service app
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 This article explains how to configure common settings for web apps, mobile back end, or API app. For Azure Functions, see [App settings reference for Azure Functions](../azure-functions/functions-app-settings.md).
 
 ## Configure app settings
diff --git a/articles/app-service/configure-ssl-certificate.md b/articles/app-service/configure-ssl-certificate.md
@@ -12,6 +12,8 @@ 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 [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,6 +14,8 @@ author: cephalin
 
 **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 (CI) and continuous delivery (CD) using [Azure DevOps](/azure/devops/). 
 
 YAML pipelines are defined 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
@@ -12,6 +12,8 @@ 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 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
@@ -10,6 +10,8 @@ ms.author: cephalin
 
 # Continuous deployment to Azure App Service
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 [Azure App Service](overview.md) enables 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 Repos](/azure/devops/repos/git/creatingrepo) repositories by pulling in the latest updates.
 
 [!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
@@ -13,6 +13,8 @@ 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 when you're running in the **Standard**, **Premium**, or **Isolated** App Service plan tier. Deployment slots are live apps with their own host names. App content and configurations 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
@@ -10,6 +10,8 @@ ms.author: cephalin
 
 # Deploy files to 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 how to deploy individual files to App Service, separate from your application package.
 
 ## Prerequisites
@@ -37,7 +39,7 @@ This ZIP package deployment uses the same Kudu service that powers continuous in
 
 #### With zip deploy UI in Kudu
 
-In the browser, navigate to `https://<app_name>.scm.azurewebsites.net/ZipDeployUI`.
+In the browser, navigate to `https://<app_name>.scm.azurewebsites.net/ZipDeployUI` (see [note at top](#dnl-note)).
 
 Upload the ZIP package you created in [Create a project ZIP package](#create-a-project-zip-package) by dragging it to the file explorer area on the web page.
 
@@ -87,6 +89,9 @@ curl -X POST \
      "https://<app-name>.scm.azurewebsites.net/api/publish?type=zip"
 ```
 
+> [!NOTE]
+> For the actual fully qualified domain name to use in the URL, see [note at top](#dnl-note)
+
 # [ARM template](#tab/arm)
 
 ARM templates only support [deployments from remotely hosted packages](#deploy-to-network-secured-apps).
@@ -147,6 +152,9 @@ curl -X POST \
      "https://<app-name>.scm.azurewebsites.net/api/publish?type=<package-type>"
 ```
 
+> [!NOTE]
+> For the actual fully qualified domain name to use in the URL, see [note at top](#dnl-note)
+
 For more information, see [Kudu publish API reference](#kudu-publish-api-reference)
 
 # [ARM template](#tab/arm)
@@ -209,6 +217,9 @@ curl -X POST \
      "https://<app-name>.scm.azurewebsites.net/api/publish?type=startup"
 ```
 
+> [!NOTE]
+> For the actual fully qualified domain name to use in the URL, see [note at top](#dnl-note)
+
 ### Deploy a library file
 
 The following example uses the cURL tool to deploy a library file for the application. Replace the placeholders `<lib-file-path>` and `<app-name>`. If you choose basic authentication, supply the [deployment credentials](deploy-configure-credentials.md) in `<username>` and `<password>`.
@@ -229,6 +240,9 @@ curl -X POST \
      "https://<app-name>.scm.azurewebsites.net/api/publish?type=lib&path=/home/site/deployments/tools/my-lib.jar"
 ```
 
+> [!NOTE]
+> For the actual fully qualified domain name to use in the URL, see [note at top](#dnl-note)
+
 ### Deploy a static file
 
 The following example uses the cURL tool to deploy a config file for the application. Replace the placeholders `<config-file-path>` and `<app-name>`. If you choose basic authentication, supply the [deployment credentials](deploy-configure-credentials.md) in `<username>` and `<password>`.
@@ -249,6 +263,9 @@ curl -X POST \
      "https://<app-name>.scm.azurewebsites.net/api/publish?type=static&path=/home/site/deployments/tools/my-config.json"
 ```
 
+> [!NOTE]
+> For the actual fully qualified domain name to use in the URL, see [note at top](#dnl-note)
+
 # [ARM template](#tab/arm)
 
 ARM templates only support [deployments from remotely hosted packages](#deploy-to-network-secured-apps).
@@ -295,6 +312,9 @@ curl -X POST \
      "https://<app-name>.scm.azurewebsites.net/api/publish?type=zip"
 ```
 
+> [!NOTE]
+> For the actual fully qualified domain name to use in the URL, see [note at top](#dnl-note)
+
 # [ARM template](#tab/arm)
 
 Add the following JSON to your ARM template. Replace the placeholder `<app-name>`. 
diff --git a/articles/app-service/environment/overview.md b/articles/app-service/environment/overview.md
@@ -3,13 +3,15 @@ title: App Service Environment overview
 description: This article discusses the Azure App Service Environment feature of Azure App Service.
 author: madsd
 ms.topic: overview
-ms.date: 03/21/2024
+ms.date: 05/27/2024
 ms.author: madsd
 ms.custom: "UpdateFrequency3, references_regions"
 ---
 
 # App Service Environment overview
 
+[!INCLUDE [regionalization-note](../includes/regionalization-note.md)]
+
 An App Service Environment is an Azure App Service feature that provides a fully isolated and dedicated environment for running App Service apps securely at high scale.
 
 > [!NOTE]
diff --git a/articles/app-service/includes/regionalization-note.md b/articles/app-service/includes/regionalization-note.md
@@ -0,0 +1,18 @@
+---
+author: msangapu-msft
+ms.author: msangapu
+ms.topic: include
+ms.date: 05/31/2024
+ms.service: app-service
+ms.subservice: web-apps
+---
+
+<a name="dnl-note" ></a>
+
+> [!NOTE]
+> Beginning June 1, 2024, all newly created App Service apps will have the option to create a unique default hostname with a naming convention of `<app-name>`-`<random-hash>`.`<region>`.`azurewebsites.net`. The names of existing apps will not change.
+>
+> Example: myapp-ds27dh7271aah175.westus-01.azurewebsites.net 
+>    
+> For more information, refer to [Unique Default Hostname for App Service Resource](https://go.microsoft.com/fwlink/?linkid=2265728).
+>
diff --git a/articles/app-service/includes/tutorial-set-up-app-service-authentication/after.md b/articles/app-service/includes/tutorial-set-up-app-service-authentication/after.md
@@ -154,7 +154,7 @@ When you enabled the App Service authentication/authorization module in the prev
 1. Select the app registration that was created. 
 1. In the overview, verify that **Supported account types** is set to **My organization only**.
     
-1. To verify that access to your app is limited to users in your organization, go to your web app **Overview** and select the **Default domain** link.  Or, start a browser in incognito or private mode and go to `https://<app-name>.azurewebsites.net`.
+1. To verify that access to your app is limited to users in your organization, go to your web app **Overview** and select the **Default domain** link.  Or, start a browser in incognito or private mode and go to `https://<app-name>.azurewebsites.net` (see [note at top](#dnl-note)).
 
     :::image type="content" alt-text="Screenshot that shows verifying access." source="../../media/scenario-secure-app-authentication-app-service/verify-access.png":::
 
diff --git a/articles/app-service/monitor-instances-health-check.md b/articles/app-service/monitor-instances-health-check.md
@@ -11,6 +11,8 @@ ms.author: msangapu
 
 # Monitor App Service instances using Health check
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 This article uses 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 every minute a path of your web application of your choice. 
 
 ![Health check failure][1]
diff --git a/articles/app-service/overview-authentication-authorization.md b/articles/app-service/overview-authentication-authorization.md
@@ -11,6 +11,8 @@ ms.author: cephalin
 ---
 # Authentication and authorization in Azure App Service and Azure Functions
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 Azure App Service provides built-in authentication and authorization capabilities (sometimes referred to as "Easy Auth"), so you can sign in users and access data by writing minimal or no code in your web app, RESTful API, and mobile back end, and also [Azure Functions](../azure-functions/functions-overview.md). This article describes how App Service helps simplify authentication and authorization for your app.
 
 ## Why use the built-in authentication?
diff --git a/articles/app-service/overview-hosting-plans.md b/articles/app-service/overview-hosting-plans.md
@@ -12,6 +12,8 @@ ms.custom: UpdateFrequency3
 ---
 # Azure App Service plan overview
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 An app service always runs in an _App Service plan_. In addition, [Azure Functions](../azure-functions/dedicated-plan.md) also has the option of running in an _App Service plan_. An App Service plan defines a set of compute resources for a web app to run. 
 
 When you create an App Service plan in a certain region (for example, West Europe), a set of compute resources is created for that plan in that region. Whatever apps you put into this App Service plan run on these compute resources as defined by your App Service plan. Each App Service plan defines:
diff --git a/articles/app-service/overview-managed-identity.md b/articles/app-service/overview-managed-identity.md
@@ -12,6 +12,8 @@ ai-usage: ai-assisted
 
 # How to use managed identities for App Service and Azure Functions
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 This article shows you how to create a managed identity for App Service and Azure Functions applications and how to use it to access other resources. 
 
 > [!IMPORTANT] 
diff --git a/articles/app-service/overview-private-endpoint.md b/articles/app-service/overview-private-endpoint.md
@@ -11,6 +11,8 @@ ms.custom: msangapu
 
 # Using Private Endpoints for App Service apps
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 > [!IMPORTANT]
 > Private endpoint is available for Windows and Linux apps, containerized or not, hosted on these App Service plans : **Basic**, **Standard**, **PremiumV2**, **PremiumV3**, **IsolatedV2**, **Functions Premium** (sometimes referred to as the Elastic Premium plan). 
 
@@ -53,7 +55,7 @@ In the Web HTTP logs of your app, you find the client source IP. This feature is
 
 ## DNS
 
-When you use private endpoint for App Service apps, the requested URL must match the name of your app. By default mywebappname.azurewebsites.net.
+When you use private endpoint for App Service apps, the requested URL must match the name of your app. By default mywebappname.azurewebsites.net (see [note at top](#dnl-note)).
 
 By default, without private endpoint, the public name of your web app is a canonical name to the cluster.
 For example, the name resolution is:
diff --git a/articles/app-service/overview-vnet-integration.md b/articles/app-service/overview-vnet-integration.md
@@ -10,6 +10,8 @@ ms.custom: UpdateFrequency3
 ---
 # <a name="regional-virtual-network-integration"></a>Integrate your app with an Azure virtual network
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 This article describes the Azure App Service virtual network integration feature and how to set it up with apps in [App Service](./overview.md). With [Azure virtual networks](../virtual-network/virtual-networks-overview.md), you can place many of your Azure resources in a non-internet-routable network. The App Service virtual network integration feature enables your apps to access resources in or through a virtual network.
 
 >[!NOTE]
diff --git a/articles/app-service/overview.md b/articles/app-service/overview.md
@@ -12,6 +12,8 @@ author: msangapu-msft
 
 # App Service overview
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 *Azure App Service* is an HTTP-based service for hosting web applications, REST APIs, and mobile back ends. You can develop in your favorite language, be it .NET, .NET Core, Java, Node.js, PHP, and Python. Applications run and scale with ease on both Windows and [Linux](#app-service-on-linux)-based environments.
 
 App Service adds the power of Microsoft Azure to your application, such as security, load balancing, autoscaling, and automated management. Additionally, you can take advantage of its DevOps capabilities, such as continuous deployment from Azure DevOps, GitHub, Docker Hub, and other sources, package management, staging environments, custom domain, and TLS/SSL certificates.
diff --git a/articles/app-service/quickstart-dotnetcore.md b/articles/app-service/quickstart-dotnetcore.md
@@ -34,6 +34,8 @@ target cross-platform with .NET 7.0.
 
 # Quickstart: Deploy an ASP.NET web app
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 In this quickstart, you learn how to create and deploy your first ASP.NET web app to [Azure App Service](overview.md). App Service supports various versions of .NET apps, and provides a highly scalable, self-patching web hosting service. ASP.NET web apps are cross-platform and can be hosted on Linux or Windows. When you're finished, you have an Azure resource group consisting of an App Service hosting plan and an App Service with a deployed web application.
 
 Alternatively, you can deploy an ASP.NET web app as part of a [Windows or Linux container in App Service](quickstart-custom-container.md).
diff --git a/articles/app-service/quickstart-nodejs.md b/articles/app-service/quickstart-nodejs.md
diff --git a/articles/app-service/quickstart-python.md b/articles/app-service/quickstart-python.md
diff --git a/articles/app-service/reference-app-settings.md b/articles/app-service/reference-app-settings.md
diff --git a/articles/app-service/scenario-secure-app-authentication-app-service.md b/articles/app-service/scenario-secure-app-authentication-app-service.md
diff --git a/articles/app-service/troubleshoot-diagnostic-logs.md b/articles/app-service/troubleshoot-diagnostic-logs.md
diff --git a/articles/app-service/webjobs-create.md b/articles/app-service/webjobs-create.md
