More fixes.

Author: TimShererWithAquent

articles/app-service/configure-authentication-provider-aad.md

@@ -79,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:
 
@@ -166,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:
 
@@ -362,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**.
 

articles/app-service/deploy-staging-slots.md

@@ -66,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).
 
@@ -214,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.
 
@@ -392,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)
 
@@ -419,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 slote 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).
 
 -----

articles/app-service/deploy-zip.md

@@ -39,9 +39,9 @@ This ZIP package deployment uses the same Kudu service that powers continuous in
 
 ### Deploy with ZIP deploy UI in Kudu
 
-In the browser, go to `https://<app_name>.scm.azurewebsites.net/ZipDeployUI`. For the app name, see the [note at the beginning of the article](#dnl-note).
-
-Upload the ZIP package you created in [Create a project ZIP package](#create-a-project-zip-package). Drag it to the **File Explorer** area on the web page.
+1. Open your app in the Azure portal and select **Development Tools** > **Advanced Tools**, then select **Go**.
+1. In Kudu, select **Tools** > **Zip Push Deploy**.
+1. Upload the ZIP package you created in [Create a project ZIP package](#create-a-project-zip-package). Drag it to the file explorer area on the web page.
 
 When deployment is in progress, an icon in the top right corner shows you the progress percentage. The page also displays messages for the operation below the **File Explorer** area. When deployment finishes, the last message should say "Deployment successful."
 
@@ -63,15 +63,15 @@ This command restarts the app after deploying the ZIP package.
 
 # [Azure PowerShell](#tab/powershell)
 
-The following example uses [`Publish-AzWebapp`](/powershell/module/az.websites/publish-azwebapp) to upload the ZIP package. Replace the placeholders *\<group-name>*, *\<app-name>*, and *\<zip-package-path>*.
+The following example uses [`Publish-AzWebapp`](/powershell/module/az.websites/publish-azwebapp) to upload the ZIP package. Replace the placeholders for resource group, app name, and package path.
 
 ```azurepowershell
 Publish-AzWebApp -ResourceGroupName Default-Web-WestUS -Name MyApp -ArchivePath <zip-package-path> 
 ```
 
 # [Kudu API](#tab/api)
 
-The following example uses the client URL (cURL) tool to deploy a ZIP package. Replace the placeholders *\<zip-package-path>* and *\<app-name>*. If you choose basic authentication, supply the [deployment credentials](deploy-configure-credentials.md) in *\<username>* and *\<password>*.
+The following example uses the client URL (cURL) tool to deploy a ZIP package. If you choose basic authentication, supply the [deployment credentials](deploy-configure-credentials.md) in *\<username>* and *\<password>*.
 
 ```bash
 # Microsoft Entra authentication
@@ -80,17 +80,17 @@ TOKEN=$(az account get-access-token --query accessToken | tr -d '"')
 curl -X POST \
      -H "Authorization: Bearer $TOKEN" \
      -T @"<zip-package-path>" \
-     "https://<app-name>.scm.azurewebsites.net/api/publish?type=zip"
+     "https://<URL>/api/publish?type=zip"
 
 # Basic authentication
 curl -X POST \
      -u '<username>:<password>' \
      -T "<zip-package-path>" \
-     "https://<app-name>.scm.azurewebsites.net/api/publish?type=zip"
+     "https://<URL>/api/publish?type=zip"
 ```
 
 > [!NOTE]
-> Get the actual fully qualified domain name to use in the URL from the [note at the beginning of the article](#dnl-note).
+> Get the Kudu URL from the Azure portal: open your app and select **Development Tools** > **Advanced Tools**, then select **Go** to open the Kudu URL.
 
 # [ARM template](#tab/arm)
 
@@ -126,15 +126,15 @@ The CLI command uses the [Kudu publish API](#kudu-publish-api-reference) to depl
 
 # [Azure PowerShell](#tab/powershell)
 
-The following example uses [`Publish-AzWebapp`](/powershell/module/az.websites/publish-azwebapp) to upload the WAR file. Replace the placeholders *\<group-name>*, *\<app-name>*, and *\<package-path>*. Azure PowerShell supports only WAR and JAR files.
+The following example uses [`Publish-AzWebapp`](/powershell/module/az.websites/publish-azwebapp) to upload the WAR file. Replace the placeholders for resource group, app name, and package path. Azure PowerShell supports only WAR and JAR files.
 
 ```powershell
 Publish-AzWebapp -ResourceGroupName <group-name> -Name <app-name> -ArchivePath <package-path>
 ```
 
 # [Kudu API](#tab/api)
 
-The following example uses the cURL tool to deploy a WAR, JAR, or EAR file. Replace the placeholders *\<file-path>*, *\<app-name>*, and *\<package-type>* (`war`, `jar`, or `ear`). If you choose basic authentication, supply the [deployment credentials](deploy-configure-credentials.md) in *\<username>* and *\<password>*.
+The following example uses the cURL tool to deploy a WAR, JAR, or EAR file. Replace the placeholders *\<file-path>* and *\<package-type>* (`war`, `jar`, or `ear`). If you choose basic authentication, supply the [deployment credentials](deploy-configure-credentials.md) in *\<username>* and *\<password>*.
 
 ```bash
 # Microsoft Entra authentication
@@ -143,17 +143,17 @@ TOKEN=$(az account get-access-token --query accessToken | tr -d '"')
 curl -X POST \
      -H "Authorization: Bearer $TOKEN" \
      -T @"<file-path>" \
-     "https://<app-name>.scm.azurewebsites.net/api/publish?type=<package-type>"
+     "https://<URL>/api/publish?type=<package-type>"
 
 # Basic authentication
 curl -X POST \
      -u <username>:<password> \
      -T @"<file-path>" \
-     "https://<app-name>.scm.azurewebsites.net/api/publish?type=<package-type>"
+     "https://<URL>/api/publish?type=<package-type>"
 ```
 
 > [!NOTE]
-> Get the actual fully qualified domain name to use in the URL from the [note at the beginning of the article](#dnl-note).
+> Get the Kudu URL from the Azure portal: open your app and select **Development Tools** > **Advanced Tools**, then select **Go** to open the Kudu URL.
 
 For more information, see [Kudu publish API reference](#kudu-publish-api-reference).
 
@@ -199,7 +199,7 @@ Not supported. See the Azure CLI or Kudu API tabs.
 
 ### Deploy a startup script
 
-The following example uses the cURL tool to deploy a startup file for the application. Replace the placeholders *\<startup-file-path>* and *\<app-name>*. If you choose basic authentication, supply the [deployment credentials](deploy-configure-credentials.md) in *\<username>* and *\<password>*.
+The following example uses the cURL tool to deploy a startup file for the application. Replace the placeholder *\<startup-file-path>*. If you choose basic authentication, supply the [deployment credentials](deploy-configure-credentials.md) in *\<username>* and *\<password>*.
 
 ```bash
 # Microsoft Entra authentication
@@ -208,21 +208,21 @@ TOKEN=$(az account get-access-token --query accessToken | tr -d '"')
 curl -X POST \
      -H "Authorization: Bearer $TOKEN" \
      -T @"<startup-file-path>" \
-     "https://<app-name>.scm.azurewebsites.net/api/publish?type=startup"
+     "https://<URL>/api/publish?type=startup"
 
 # Basic authentication
 curl -X POST \
      -u <username>:<password> \
      -T @"<startup-file-path>" \
-     "https://<app-name>.scm.azurewebsites.net/api/publish?type=startup"
+     "https://<URL>/api/publish?type=startup"
 ```
 
 > [!NOTE]
-> Get the actual fully qualified domain name to use in the URL from the [note at the beginning of the article](#dnl-note).
+> Get the Kudu URL from the Azure portal: open your app and select **Development Tools** > **Advanced Tools**, then select **Go** to open the Kudu URL.
 
 ### 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>*.
+The following example uses the cURL tool to deploy a library file for the application. Replace the placeholder *\<lib-file-path>*. If you choose basic authentication, supply the [deployment credentials](deploy-configure-credentials.md) in *\<username>* and *\<password>*.
 
 ```bash
 # Microsoft Entra authentication
@@ -231,21 +231,21 @@ TOKEN=$(az account get-access-token --query accessToken | tr -d '"')
 curl -X POST \
      -H "Authorization: Bearer $TOKEN" \
      -T @"<lib-file-path>" \
-     "https://<app-name>.scm.azurewebsites.net/api/publish?type=lib&path=/home/site/deployments/tools/my-lib.jar"
+     "https://<URL>/api/publish?type=lib&path=/home/site/deployments/tools/my-lib.jar"
 
 # Basic authentication
 curl -X POST \
      -u <username>:<password> \
      -T @"<lib-file-path>" \
-     "https://<app-name>.scm.azurewebsites.net/api/publish?type=lib&path=/home/site/deployments/tools/my-lib.jar"
+     "https://<URL>/api/publish?type=lib&path=/home/site/deployments/tools/my-lib.jar"
 ```
 
 > [!NOTE]
-> Get the actual fully qualified domain name to use in the URL from the [note at the beginning of the article](#dnl-note).
+> Get the Kudu URL from the Azure portal: open your app and select **Development Tools** > **Advanced Tools**, then select **Go** to open the Kudu URL.
 
 ### 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>*.
+The following example uses the cURL tool to deploy a config file for the application. Replace the placeholder *\<config-file-path>*. If you choose basic authentication, supply the [deployment credentials](deploy-configure-credentials.md) in *\<username>* and *\<password>*.
 
 ```bash
 # Microsoft Entra authentication
@@ -254,17 +254,17 @@ TOKEN=$(az account get-access-token --query accessToken | tr -d '"')
 curl -X POST \
      -H "Authorization: Bearer $TOKEN" \
      -T @"<config-file-path>" \
-     "https://<app-name>.scm.azurewebsites.net/api/publish?type=static&path=/home/site/deployments/tools/my-config.json"
+     "https://<URL>/api/publish?type=static&path=/home/site/deployments/tools/my-config.json"
 
 # Basic authentication
 curl -X POST \
      -u <username>:<password> \
      -T @"<config-file-path>" \
-     "https://<app-name>.scm.azurewebsites.net/api/publish?type=static&path=/home/site/deployments/tools/my-config.json"
+     "https://<URL>/api/publish?type=static&path=/home/site/deployments/tools/my-config.json"
 ```
 
 > [!NOTE]
-> Get the actual fully qualified domain name to use in the URL from the [note at the beginning of the article](#dnl-note).
+> Get the Kudu URL from the Azure portal: open your app and select **Development Tools** > **Advanced Tools**, then select **Go** to open the Kudu URL.
 
 # [ARM template](#tab/arm)
 
@@ -302,18 +302,18 @@ curl -X POST \
      -H "Authorization: Bearer $TOKEN" \
      -H "Content-Type: application/json" \
      -d '{"packageUri": "https://storagesample.blob.core.windows.net/sample-container/myapp.zip?sv=2021-10-01&sb&sig=slk22f3UrS823n4kSh8Skjpa7Naj4CG3"}' \
-     "https://<app-name>.scm.azurewebsites.net/api/publish?type=zip"
+     "https://<URL>/api/publish?type=zip"
 
 # Basic authentication
 curl -X POST \
      -u '<username>:<password>' \
      -H "Content-Type: application/json" \
      -d '{"packageUri": "https://storagesample.blob.core.windows.net/sample-container/myapp.zip?sv=2021-10-01&sb&sig=slk22f3UrS823n4kSh8Skjpa7Naj4CG3"}' \
-     "https://<app-name>.scm.azurewebsites.net/api/publish?type=zip"
+     "https://<URL>/api/publish?type=zip"
 ```
 
 > [!NOTE]
-> Get the actual fully qualified domain name to use in the URL from the [note at the beginning of the article](#dnl-note).
+> Get the Kudu URL from the Azure portal: open your app and select **Development Tools** > **Advanced Tools**, then select **Go** to open the Kudu URL.
 
 # [ARM template](#tab/arm)
 

articles/app-service/overview-authentication-authorization.md

@@ -181,7 +181,7 @@ Disable [Azure Front Door caching](../frontdoor/front-door-caching.md) for the a
 
 ### Use the Azure Front Door endpoint for redirects
 
-App Service is usually not accessible directly when it's exposed by Azure Front Door. You can prevent this behavior, for example, by exposing App Service by using Azure Private Link in Azure Front Door Premium. To prevent the authentication workflow from redirecting traffic back to App Service directly, it's important to configure the application to redirect back to `https://<front-door-endpoint>/.auth/login/<provider>/callback`.
+App Service is usually not accessible directly when it's exposed by Azure Front Door. You can prevent this behavior, for example, by exposing App Service by using Azure Private Link in Azure Front Door Premium. To prevent the authentication workflow from redirecting traffic back to App Service directly. For more information, see [Redirect URI](/entra/identity-platform/reply-url).
 
 ### Ensure that App Service is using the right redirect URI