Consistency edit.

TimShererWithAquent · TimShererWithAquent · commit e1d76a8510de · 2025-05-29T08:00:50.000-07:00
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
@@ -156,7 +156,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` (see [note at top](#dnl-note)).
+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.
 
     :::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/overview-hosting-plans.md b/articles/app-service/overview-hosting-plans.md
@@ -14,8 +14,6 @@ ms.custom: UpdateFrequency3
 
 An *Azure App Service plan* defines a set of compute resources for a web app to run. An app service always runs in an App Service plan. [Azure Functions](../azure-functions/dedicated-plan.md) also has the option of running in an App Service plan.
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 When you create an App Service plan in a certain region, you create a set of compute resources for that plan in that region. Whatever apps you put into the App Service plan run on those compute resources, as defined in the plan.
 
 Each App Service plan defines:
diff --git a/articles/app-service/overview-managed-identity.md b/articles/app-service/overview-managed-identity.md
@@ -15,11 +15,9 @@ ai-usage: ai-assisted
 
 This article shows you how to create a managed identity for Azure App Service and Azure Functions applications, and how to use it to access other resources.
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 [!INCLUDE [app-service-managed-identities](../../includes/app-service-managed-identities.md)]
 
-The managed identity configuration is specific to the slot. To configure a managed identity for a deployment slot in the portal, go to the slot first. To find the managed identity for your web app or deployment slot in your Microsoft Entra tenant from the Azure portal, search for it directly from the **Overview** page of your tenant. Usually, the slot name is similar to `<app-name>/slots/<slot-name>`.
+The managed identity configuration is specific to the slot. To configure a managed identity for a deployment slot in the portal, go to the slot first. To find the managed identity for your web app or deployment slot in your Microsoft Entra tenant from the Azure portal, search for it directly from the **Overview** page of your tenant.
 
 > [!NOTE]
 > Managed identities aren't available for [apps deployed in Azure Arc](overview-arc-integration.md).
diff --git a/articles/app-service/overview-private-endpoint.md b/articles/app-service/overview-private-endpoint.md
@@ -14,8 +14,6 @@ ms.assetid: 2dceac28-1ba6-4904-a15d-9e91d5ee162c
 
 # Use private endpoints for Azure App Service apps
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 You can use a private endpoint for your Azure App Service apps. The private endpoint allows clients located in your private network to securely access an app over Azure Private Link. The private endpoint uses an IP address from your Azure virtual network address space. Network traffic between a client on your private network and the app goes over the virtual network and Private Link on the Microsoft backbone network. This configuration eliminates exposure from the public internet.
 
 When you use a private endpoint for your app, you can:
@@ -57,9 +55,7 @@ You can find the client source IP in the web HTTP logs of your app. This feature
 
 ## DNS
 
-When you use private endpoint for App Service apps, the requested URL must match the name of your app, which is by default `<app-name>.azurewebsites.net`. When you use a [unique default hostname](#dnl-note), your app name has the format `<app-name>-<random-hash>.<region>.azurewebsites.net`. In the following examples, `mywebapp` could also represent the full regionalized unique hostname.
-
-By default, without a private endpoint, the public name of your web app is a canonical name to the cluster. For example, the name resolution is:
+When you use private endpoint for App Service apps, the requested URL must match the address of your app. By default, without a private endpoint, the public name of your web app is a canonical name to the cluster. For example, the name resolution is:
 
 | Name | Type | Value |
 |:-----|:-----|:------|
diff --git a/articles/app-service/overview-vnet-integration.md b/articles/app-service/overview-vnet-integration.md
@@ -10,8 +10,6 @@ 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/quickstart-dotnetcore.md b/articles/app-service/quickstart-dotnetcore.md
@@ -350,11 +350,7 @@ Follow these steps to create your App Service resources and publish your project
    - Replace `<os>` with either `linux` or `windows`.
    - You can optionally include the argument `--location <location-name>` where `<location-name>` is an available Azure region. To get a list of allowable regions for your Azure account, run the [az account list-locations](/cli/azure/appservice#az-appservice-list-locations) command.
 
-   The command might take a few minutes to complete. While it runs, the command provides messages about creating the resource group, the App Service plan, and hosting app, configuring logging, then performing ZIP deployment. Then it shows a message with the app's URL:
-
-   ```azurecli
-   You can launch the app at http://<app-name>.azurewebsites.net
-   ```
+   The command might take a few minutes to complete. While it runs, the command provides messages about creating the resource group, the App Service plan, and hosting app, configuring logging, then performing ZIP deployment. Then it shows a message with the app's URL.
 
 1. Open a web browser and navigate to the URL. You see the ASP.NET Core 8.0 web app displayed in the page.
 
diff --git a/articles/app-service/quickstart-nodejs.md b/articles/app-service/quickstart-nodejs.md
@@ -14,8 +14,6 @@ ai-usage: ai-assisted
 
 # Deploy a Node.js web app in Azure
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 In this quickstart, you'll learn how to create and deploy your first Node.js ([Express](https://www.expressjs.com)) web app to [Azure App Service](overview.md). App Service supports various versions of Node.js on both Linux and Windows. 
 
 This quickstart configures an App Service app in the Free tier and incurs no cost for your Azure subscription.
@@ -131,7 +129,7 @@ Before you continue, ensure that you have all the prerequisites installed and co
 # [Deploy to Linux](#tab/linux)
 
 2. Right-click **App Services** and select **Create new Web App**. A Linux container is used by default. 
-1. Type a globally unique name for your web app and select **Enter**. The name must be unique across all of Azure and use only alphanumeric characters ('A-Z', 'a-z', and '0-9') and hyphens ('-'). See [the note at the the start of this article](#dnl-note).
+1. Type a globally unique name for your web app and select **Enter**. The name must be unique across all of Azure and use only alphanumeric characters ('A-Z', 'a-z', and '0-9') and hyphens ('-').
 1. In **Select a runtime stack**, select the Node.js version you want. An LTS version is recommended.
 1. In **Select a pricing tier**, select **Free (F1)** and wait for the resources to be created in Azure.
 1. In the popup **Always deploy the workspace "myExpressApp" to \<app-name>"**, select **Yes**. Doing so ensures that, as long as you're in the same workspace, Visual Studio Code deploys to the same App Service app each time.
@@ -143,7 +141,7 @@ Before you continue, ensure that you have all the prerequisites installed and co
 # [Deploy to Windows](#tab/windows)
 
 2. Right-click **App Services** and select **Create new Web App... Advanced**.
-1. Type a globally unique name for your web app and select **Enter**. The name must be unique across all of Azure and use only alphanumeric characters ('A-Z', 'a-z', and '0-9') and hyphens ('-'). See [the note at start of this article](#dnl-note).
+1. Type a globally unique name for your web app and select **Enter**. The name must be unique across all of Azure and use only alphanumeric characters ('A-Z', 'a-z', and '0-9') and hyphens ('-').
 1. Select **Create a new resource group**, and then enter a name for the resource group, such as *AppServiceQS-rg*.
 1. Select the Node.js version you want. An LTS version is recommended.
 1. Select **Windows** for the operating system.
@@ -195,13 +193,13 @@ az webapp up --sku F1 --name <app-name> --os-type Windows
 -----
 
 - If the `az` command isn't recognized, ensure you have the Azure CLI installed as described in [Set up your initial environment](#set-up-your-initial-environment).
-- Replace `<app_name>` with a name that's unique across all of Azure. (*Valid characters are `a-z`, `0-9`, and `-`*.) See [the note at the start of this article](#dnl-note). A good pattern is to use a combination of your company name and an app identifier.
+- Replace `<app_name>` with a name that's unique across all of Azure. (*Valid characters are `a-z`, `0-9`, and `-`*.) A good pattern is to use a combination of your company name and an app identifier.
 - The `--sku F1` argument creates the web app on the Free pricing tier, which incurs no cost.
 - You can optionally include the argument `--location <location-name>` where `<location_name>` is an available Azure region. You can retrieve a list of allowable regions for your Azure account by running the [`az account list-locations`](/cli/azure/appservice#az-appservice-list-locations) command.
 - The command creates a Linux app for Node.js by default. To create a Windows app instead, use the `--os-type` argument. 
 - If you see the error, "Could not auto-detect the runtime stack of your app," ensure you're running the command in the *myExpressApp* directory (See [Troubleshooting auto-detect issues with az webapp up](https://github.com/Azure/app-service-linux-docs/blob/master/AzWebAppUP/runtime_detection.md).)
 
-The command might take a few minutes to complete. While running, it provides messages about creating the resource group, the App Service plan, and the app resource, configuring logging, and doing Zip deployment. It then gives the message, "You can launch the app at http://&lt;app-name&gt;.azurewebsites.net", which is the app's URL on Azure. (See [the note at the start of this article](#dnl-note).)
+The command might take a few minutes to complete. While running, it provides messages about creating the resource group, the App Service plan, and the app resource, configuring logging, and doing Zip deployment. It then returns a message which includes the app's URL on Azure.
 
 <pre>
 The webapp '&lt;app-name>' doesn't exist
@@ -214,9 +212,9 @@ Creating zip with contents of dir /home/cephas/myExpressApp ...
 Getting scm site credentials for zip deployment
 Starting zip deployment. This operation can take a while to complete ...
 Deployment endpoint responded with status code 202
-You can launch the app at http://&lt;app-name>.azurewebsites.net
+You can launch the app at '&lt;URL>'
 {
-  "URL": "http://&lt;app-name>.azurewebsites.net",
+  "URL": "&lt;URL>",
   "appserviceplan": "&lt;app-service-plan-name>",
   "location": "centralus",
   "name": "&lt;app-name>",
@@ -246,7 +244,7 @@ Sign in to the [Azure portal](https://portal.azure.com).
 
     :::image type="content" source="./media/quickstart-nodejs/project-details.png" alt-text="Screenshot of the Project Details section showing where you select the Azure subscription and the resource group for the web app.":::
 
-1. Under **Instance details**, type a globally unique name for your web app and select **Code**. (See [the note at the start of this article](#dnl-note).) Select **Node 18 LTS** in **Runtime stack**, an **Operating System**, and a **Region** you want to serve your app from.
+1. Under **Instance details**, type a globally unique name for your web app and select **Code**. Select **Node 18 LTS** in **Runtime stack**, an **Operating System**, and a **Region** you want to serve your app from.
 
     :::image type="content" source="./media/quickstart-nodejs/instance-details.png" alt-text="Screenshot of the Instance Details section.":::
 
@@ -323,15 +321,15 @@ You can deploy changes to this app by making edits in Visual Studio Code, saving
     
     This command uses values that are cached locally in the *.azure/config* file, such as the app name, resource group, and App Service plan.
     
-1. Once deployment is complete, refresh the webpage `http://<app-name>.azurewebsites.net`. (See [the note at the start of this article](#dnl-note).) You should see that the `Welcome to Express` message has been changed to `Welcome to Azure`.
+1. Once deployment is complete, refresh the webpage. You should see that the `Welcome to Express` message has been changed to `Welcome to Azure`.
 
 ::: zone-end
 
 :::zone target="docs" pivot="development-environment-azure-portal"
 
 2. Save your changes, then redeploy the app using your FTP client.
     
-1. Once deployment is complete, refresh the webpage `http://<app-name>.azurewebsites.net`. (See [note the at the start of this article](#dnl-note).) You should see that the `Welcome to Express` message has been changed to `Welcome to Azure`.
+1. Once deployment is complete, refresh the webpage. You should see that the `Welcome to Express` message has been changed to `Welcome to Azure`.
 
 ::: zone-end
 
diff --git a/articles/app-service/quickstart-python.md b/articles/app-service/quickstart-python.md
@@ -316,7 +316,7 @@ For FastAPI, you must configure a custom startup command for App Service to run
 
 ## Browse to the app
 
-Browse to the deployed application in your web browser by using the URL `http://<app-name>.azurewebsites.net`. If you see a default app page, wait a minute and refresh the browser.
+Browse to the deployed application in your web browser. You can follow a link from the Azure portal. Go to the **Overview** page and select **Default Domain**. If you see a default app page, wait a minute and refresh the browser.
 
 The Python sample code is running a Linux container in App Service using a built-in image.
 
diff --git a/articles/app-service/reference-app-settings.md b/articles/app-service/reference-app-settings.md
@@ -9,8 +9,6 @@ ms.author: cephalin
 
 # Environment variables and app settings in Azure App Service
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 In [Azure App Service](overview.md), certain settings are available to the deployment or runtime environment as environment variables. You can customize some of these settings when you set them manually as [app settings](configure-common.md#configure-app-settings). This reference shows the variables that you can use or customize.
 
 ## App environment
diff --git a/articles/app-service/scenario-secure-app-authentication-app-service.md b/articles/app-service/scenario-secure-app-authentication-app-service.md
@@ -17,8 +17,6 @@ ms.subservice: web-apps
 
 # Quickstart: Add app authentication to your web app running on Azure App Service
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 [!INCLUDE [start](./includes/tutorial-set-up-app-service-authentication/intro.md)]
 
 [!INCLUDE [start](./includes/tutorial-set-up-app-service-authentication/after.md)]
diff --git a/articles/app-service/troubleshoot-diagnostic-logs.md b/articles/app-service/troubleshoot-diagnostic-logs.md
@@ -15,8 +15,6 @@ ai-usage: ai-assisted
 
 Azure provides built-in diagnostics to assist with debugging an [Azure App Service app](overview.md). In this article, you learn how to enable diagnostic logging and add instrumentation to your application. You also learn how to access the information that Azure logs.
 
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 This article uses the [Azure portal](https://portal.azure.com) and the Azure CLI to work with diagnostic logs. For information on working with diagnostic logs by using Visual Studio, see [Troubleshoot an app in Azure App Service using Visual Studio](troubleshoot-dotnet-visual-studio.md).
 
 In addition to the logging instructions in this article, you can use the Azure Monitor integrated logging capability. For more information, see [Send logs to Azure Monitor](#send-logs-to-azure-monitor).
@@ -171,10 +169,10 @@ To stream logs in the local console, [install the Azure CLI](/cli/azure/install-
 
 If you configure the Azure Storage blobs option for a log type, you need a client tool that works with Azure Storage. For more information, see [Microsoft client tools for working with Azure Storage](../storage/common/storage-explorers.md).
 
-For logs stored in the App Service file system, the easiest way to access the files is to download the ZIP file in the browser at:
+For logs stored in the App Service file system, access them by using the Kudu engine.
 
-- Linux or custom containers: `https://<app-name>.scm.azurewebsites.net/api/logs/docker/zip`
-- Windows apps: `https://<app-name>.scm.azurewebsites.net/api/dump`
+1. Open your app in the Azure portal and select **Development Tools** > **Advanced Tools**, then select **Go**.
+1. In Kudu, select **Tools** > **Diagnostic dump**.
 
 For Linux or custom containers, the ZIP file contains console output logs for both the Docker host and the Docker container. For a scaled-out app, the ZIP file contains one set of logs for each instance. In the App Service file system, these log files are the contents of the `/home/LogFiles` directory. Deployment logs are stored in `/site/deployments/`.
 
