Merge pull request #300522 from TimShererWithAquent/us423405-01

v-ccolin · web-flow · commit 18635027d580 · 2025-06-04T17:00:06.000+01:00
App Service apps: Consistency edit on URL formatting references (1 of 2)
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
@@ -38,7 +36,7 @@ You can create an empty App Service plan, or you can create a plan as part of ap
 6. Select **Review + create** to create the App Service plan.
 
 > [!IMPORTANT]
-> When you create an new App Service plan in an existing resource group, certain conditions with existing apps can trigger these errors:
+> When you create a new App Service plan in an existing resource group, certain conditions with existing apps can trigger these errors:
 > - `The pricing tier is not allowed in this resource group`
 > - `<SKU_NAME> workers are not available in resource group <RESOURCE_GROUP_NAME>`
 > 
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.
@@ -110,7 +108,7 @@ Create two records, as described in the following table:
 
 | Record type | Host | Value | Comments |
 | - | - | - |-|
-| CNAME | `<subdomain>` (for example, `www`) | `<app-name>.azurewebsites.net`. (See [the note at the start of this article](#dnl-note).) | The domain mapping itself. |
+| CNAME | `<subdomain>` (for example, `www`) | (See the value in the Azure portal **Overview** page for your app.) | 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)
@@ -121,7 +119,7 @@ For a wildcard name, like `*` in `*.contoso.com`, create two records, as describ
 
 | Record type | Host | Value | Comments |
 | - | - | - | - |
-| CNAME | `*` | `<app-name>.azurewebsites.net`. (See [the note at the start of this article](#dnl-note).) | The domain mapping itself. |
+| CNAME | `*` | (See the value in the Azure portal **Overview** page for your app.) | 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
@@ -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)]
@@ -81,7 +79,7 @@ To use an existing registration, select either:
 
 If you need to manually create an app registration in a workforce tenant, see [Register an application with the Microsoft identity platform](/entra/identity-platform/quickstart-register-app). As you go through the registration process, be sure to note the application (client) ID and client secret values.
 
-During the registration process, in the **Redirect URIs** section, select **Web** for platform and enter `<app-url>/.auth/login/aad/callback`. For example, enter `https://contoso.azurewebsites.net/.auth/login/aad/callback`.
+During the registration process, in the **Redirect URIs** section, select **Web** for platform, and enter a redirect URI. For example, enter `https://contoso.azurewebsites.net/.auth/login/aad/callback`.
 
 Now, modify the app registration:
 
@@ -168,7 +166,7 @@ To use an existing registration, select **Provide the details of an existing app
 
 If you need to manually create an app registration in an external tenant, see [Register an app in your external tenant](/entra/external-id/customers/how-to-register-ciam-app?tabs=webapp#register-your-web-app).
 
-During the registration process, in the **Redirect URIs** section, select **Web** for platform and enter `<app-url>/.auth/login/aad/callback`. For example, enter `https://contoso.azurewebsites.net/.auth/login/aad/callback`.
+During the registration process, in the **Redirect URIs** section, select **Web** for platform, and enter a redirect URI. For example, enter `https://contoso.azurewebsites.net/.auth/login/aad/callback`.
 
 Now, modify the app registration:
 
@@ -364,7 +362,7 @@ You can register native clients to request access to your App Service app's APIs
 
 1. On the **Register an application** pane, for **Name**, enter a name for your app registration.
 
-1. In **Redirect URI**, select **Public client/native (mobile & desktop)** and enter the URL `<app-url>/.auth/login/aad/callback`. For example, enter `https://contoso.azurewebsites.net/.auth/login/aad/callback`.
+1. In **Redirect URI**, select **Public client/native (mobile & desktop)** and enter the redirect URL. For example, enter `https://contoso.azurewebsites.net/.auth/login/aad/callback`.
 
 1. Select **Register**.
 
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:
@@ -55,7 +53,7 @@ App settings are always encrypted when they're stored (encrypted at rest).
    By default, values for app settings are hidden in the portal for security. To see a hidden value of an app setting, under **Value**, select **Show value**. To see the hidden values of all app settings, select **Show values**.
 
    > [!NOTE]
-   > Read/Write user permimssions are required to view this section in the Azure portal. RBAC built-in roles with sufficient permissions are Owner, Contributor, and Website Contributor. The Reader role alone would not be allowed to access this page. 
+   > Read/Write user permissions are required to view this section in the Azure portal. RBAC built-in roles with sufficient permissions are Owner, Contributor, and Website Contributor. The Reader role alone would not be allowed to access this page. 
 
 1. To add a new app setting, select **Add**. To edit a setting, select the setting.
 1. In the dialog, you can [stick the setting to the current slot](deploy-staging-slots.md#which-settings-are-swapped).
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:
@@ -69,7 +67,7 @@ The free App Service managed certificate is a turn-key solution for helping to s
 >
 > Free certificates are issued by DigiCert. For some domains, you must explicitly allow DigiCert as a certificate issuer by creating a [CAA domain record](https://wikipedia.org/wiki/DNS_Certification_Authority_Authorization) with the value: `0 issue digicert.com`.
 >
-> Azure fully manages the certificates on your behalf, so any aspect of the managed certificate, including the root issuer, can change at anytime. Certificate renewals change both public and private key parts.  All of these certificate changes are outside your control. Make sure to avoid hard dependencies and "pinning" practice certificates to the managed certificate or any part of the certificate hierarchy. If you need the certificate pinning behavior, add a certificate to your custom domain using any other available method in this article.
+> Azure fully manages the certificates on your behalf, so any aspect of the managed certificate, including the root issuer, can change at any time. Certificate renewals change both public and private key parts.  All of these certificate changes are outside your control. Make sure to avoid hard dependencies and "pinning" practice certificates to the managed certificate or any part of the certificate hierarchy. If you need the certificate pinning behavior, add a certificate to your custom domain using any other available method in this article.
 
 The free certificate comes with the following limitations:
 
@@ -148,7 +146,7 @@ The service principal app ID or assignee value is the ID for the App Service res
 
 | Resource provider | Service principal app ID | Key vault secret permissions | Key vault certificate permissions |
 |--|--|--|--|
-| **Microsoft Azure App Service** or **Microsoft.Azure.WebSites** | - `abfa0a7c-a6b6-4736-8310-5855508787cd` for public Azure cloud environment <br><br>- `6a02c803-dafd-4136-b4c3-5a6f318b4714` for Azure Government cloud environment | Get | Get |
+| **Microsoft Azure App Service** or **Microsoft.Azure.WebSites** | - `abfa0a7c-a6b6-4736-8310-5855508787cd` for global Azure cloud environment <br><br>- `6a02c803-dafd-4136-b4c3-5a6f318b4714` for Azure Government cloud environment | Get | Get |
 
 The service principal app ID or assignee value is the ID for the App Service resource provider. To learn how to authorize key vault permissions for the App Service resource provider using an access policy, see the [assign a Key Vault access policy documentation](/azure/key-vault/general/assign-access-policy?tabs=azure-portal).
 
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:
@@ -68,7 +66,7 @@ For you to enable multiple deployment slots, the app must be running in the Stan
 
     :::image type="content" source="media/web-sites-staged-publishing/open-deployment-slot.png" alt-text="Screenshot that shows how to open a deployment slot's management page in the portal." lightbox="media/web-sites-staged-publishing/open-deployment-slot.png":::
 
-    The staging slot has a management page just like any other App Service app. You can change the slot's configuration. To remind you that you're viewing the deployment slot, the app name appears as *\<app-name>/\<slot-name>*. The app type is **App Service (Slot)**. You can also see the slot as a separate app in your resource group, with the same designations.
+    The staging slot has a management page just like any other App Service app. You can change the slot's configuration. To remind you that you're viewing the deployment slot, the app name and the slot name appear in the URL. The app type is **App Service (Slot)**. You can also see the slot as a separate app in your resource group, with the same designations.
 
 1. On the slot's resource page, select the app URL. The deployment slot has its own host name and is also a live app. To limit public access to the deployment slot, see [Set up Azure App Service access restrictions](app-service-ip-restrictions.md).
 
@@ -216,7 +214,7 @@ If you cancel the swap, App Service reapplies configuration elements to the sour
 
 1. When you're ready to start the swap, select **Start Swap**.
 
-   When the first phase finishes, the dialog notifies you. Preview the swap in the source slot by going to `https://<app_name>-<source-slot-name>.azurewebsites.net`.
+   When the first phase finishes, the dialog notifies you.
 
 1. When you're ready to complete the pending swap, select **Complete Swap** in **Swap action**, and then select the **Complete Swap** button.
 
@@ -394,7 +392,7 @@ For more information, see [Get-AzLog](/powershell/module/az.monitor/get-azlog).
 
 ## Route production traffic automatically
 
-By default, all client requests to the app's production URL (`http://<app_name>.azurewebsites.net`) are routed to the production slot. You can route a portion of the traffic to another slot. This feature is useful if you need user feedback for a new update but you're not ready to release it to production.
+By default, all client requests to the app's production URL are routed to the production slot. You can route a portion of the traffic to another slot. This feature is useful if you need user feedback for a new update but you're not ready to release it to production.
 
 # [Azure portal](#tab/portal)
 
@@ -421,9 +419,11 @@ For more information, see [az webapp traffic-routing set](/cli/azure/webapp/traf
 To add a routing rule on a slot and transfer 15% of production traffic to it, run the following command:
 
 ```azurepowershell-interactive
-Add-AzWebAppTrafficRouting -ResourceGroupName "<group-name>" -WebAppName "<app-name>" -RoutingRule @{ActionHostName='<app-name>-<slot-name>.azurewebsites.net';ReroutePercentage='15';Name='<slot-name>'}
+Add-AzWebAppTrafficRouting -ResourceGroupName "<group-name>" -WebAppName "<app-name>" -RoutingRule @{ActionHostName='<URL>';ReroutePercentage='15';Name='<slot-name>'}
 ```
 
+Get the URL for that deployment slot from the **Deployment slots** page in the Azure portal.
+
 For more information, see [Add-AzWebAppTrafficRouting](/powershell/module/az.websites/add-azwebapptrafficrouting). To update an existing rule, use [Update-AzWebAppTrafficRouting](/powershell/module/az.websites/update-azwebapptrafficrouting).
 
 -----
diff --git a/articles/app-service/deploy-zip.md b/articles/app-service/deploy-zip.md
diff --git a/articles/app-service/monitor-instances-health-check.md b/articles/app-service/monitor-instances-health-check.md
diff --git a/articles/app-service/overview-authentication-authorization.md b/articles/app-service/overview-authentication-authorization.md
