Revise articles

cdpark · cdpark · commit 22ba76d2ba60 · 2025-05-02T20:32:15.000-07:00
diff --git a/articles/app-service/app-service-web-app-cloning.md b/articles/app-service/app-service-web-app-cloning.md
@@ -1,9 +1,9 @@
 ---
-title: Clone an App with PowerShell
+title: Clone an App by Using PowerShell
 description: Learn how to clone your App Service app to a new app by using PowerShell. Learn about various cloning scenarios, including Traffic Manager integration.
 ms.assetid: f9a5cfa1-fbb0-41e6-95d1-75d457347a35
 ms.topic: how-to
-ms.date: 01/14/2016
+ms.date: 05/02/2025
 ms.custom: devx-track-azurepowershell
 author: msangapu-msft
 ms.author: msangapu
@@ -12,9 +12,9 @@ ms.author: msangapu
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
-With the release of Microsoft Azure PowerShell version 1.1.0, there's a new option for `New-AzWebApp`. By using this option, you can clone an existing App Service app to a newly created app in a different region or in the same region. You can deploy multiple apps across different regions quickly and easily.
+This article explains how you can clone an existing App Service app to a newly created app in a different region or in the same region. You can deploy multiple apps across different regions quickly and easily.
 
-App cloning is supported for Standard, Premium, Premium V2, and Isolated App Service plans. The feature uses the same limitations as the App Service Backup feature, see [Back up an app in Azure App Service](manage-backup.md).
+App cloning is supported in **Standard**, **Premium**, **Premium V2**, and **Isolated** pricing tiers. The feature uses the same limitations as the App Service Backup feature, see [Back up an app in Azure App Service](manage-backup.md).
 
 ## Clone an existing app
 
@@ -109,8 +109,9 @@ After you have the Traffic Manager ID, the following command demonstrates how to
 ```powershell
 $destapp = New-AzWebApp -ResourceGroupName <Resource group name> -Name dest-webapp -Location "South Central US" -AppServicePlan DestinationAppServicePlan -SourceWebApp $srcapp -TrafficManagerProfileId $TMProfileID
 ```
+
 > [!NOTE]
-> If you're receiving an error that states "SSL validation on the traffic manager hostname is failing," we suggest you use the `-IgnoreCustomHostNames` attribute in the PowerShell cmdlet while you perform the clone operation. The alternative is that you can use the portal.
+> If you receive an error that states **SSL validation on the traffic manager hostname is failing**, we suggest that you use the `-IgnoreCustomHostNames` attribute in the PowerShell cmdlet while you perform the clone operation. Alternatively, you can use the Azure portal.
 
 ## Current restrictions
 
@@ -125,14 +126,13 @@ Here are the known restrictions of app cloning:
 * TiP rules aren't cloned.
 * Database content isn't cloned.
 * Outbound IP addresses change if you clone to a different scale unit.
-* Linux apps: not available.
+* Linux apps aren't available.
 * Managed identities aren't cloned.
-* Function apps: not available.
+* Function apps aren't available.
 
 ## Related content
 
-* [Clone an app in Azure App Service](app-service-web-app-cloning.md)
-* [Back up an app in Azure App Service](manage-backup.md)
-* [Learn about Azure Resource Manager support for Azure Traffic Manager Preview](../traffic-manager/traffic-manager-powershell-arm.md)
-* [Get an introduction to App Service Environment](environment/intro.md)
-* [Use Azure PowerShell with Azure Resource Manager](../azure-resource-manager/management/manage-resources-powershell.md)
+* [Back up and restore your app in Azure App Service](manage-backup.md)
+* [Using PowerShell to manage Traffic Manager](../traffic-manager/traffic-manager-powershell-arm.md)
+* [App Service Environment overview](environment/intro.md)
+* [Manage Azure resources by using Azure PowerShell](../azure-resource-manager/management/manage-resources-powershell.md)
diff --git a/articles/app-service/deploy-ci-cd-custom-container.md b/articles/app-service/deploy-ci-cd-custom-container.md
@@ -1,30 +1,30 @@
 ---
 title: Configure CI/CD to Custom Containers
-description: Set up continuous deployment to a custom Windows or Linux container in Azure App Service.
+description: Set up continuous integration and continuous delivery (CI/CD) to a custom Windows or Linux container in Azure App Service.
 keywords: azure app service, linux, docker, acr, oss
 author: msangapu-msft
 ms.assetid: a47fb43a-bbbd-4751-bdc1-cd382eae49f8
 ms.topic: how-to
-ms.date: 11/18/2022
+ms.date: 05/02/2025
 ms.author: msangapu
 ms.custom: devx-track-azurecli, linux-related-content
 zone_pivot_groups: app-service-containers-windows-linux
 ---
 
 # Continuous deployment with custom containers in Azure App Service
 
-Learn how to configure continuous integration and continuous delivery (CI/CD) for a custom container image from managed [Azure Container Registry](https://azure.microsoft.com/services/container-registry/) repositories or [Docker Hub](https://hub.docker.com).
+This article explains how to configure continuous integration and continuous delivery (CI/CD) for a custom container image from managed [Azure Container Registry](https://azure.microsoft.com/services/container-registry/) repositories or [Docker Hub](https://hub.docker.com).
 
 ## 1. Go to the Deployment Center
 
 In the [Azure portal](https://portal.azure.com), go to the management pane for your Azure App Service app.
 
-From the left menu, select **Deployment Center** > **Settings**.
+In the sidebar menu under **Deployment**, select **Deployment Center**. Choose the **Settings** tab.
 
 ::: zone pivot="container-linux"
-## 2. Choose deployment source
+## 2. Select code source
 
-Choose the deployment source based on the following criteria:
+From the **Source** dropdown menu, select the deployment source based on the following criteria:
 
 * **Container registry** sets up CI/CD between your container registry and App Service.
 * Choose the **GitHub Actions** option if you maintain the source code for your container image in GitHub. New commits to your GitHub repository trigger the deploy action, which can run `docker build` and `docker push` directly to your container registry. It then updates your App Service app to run the new image. For more information, see [How CI/CD works with GitHub Actions](#how-cicd-works-with-github-actions).
@@ -50,7 +50,7 @@ To deploy a multi-container (Docker Compose) app, select **Docker Compose** in *
 If you don't see the **Container Type** dropdown list, scroll back up to **Source** and select **Container Registry**.
 ::: zone-end
 
-In **Registry source**, select where your container registry is. If it's not Azure Container Registry or Docker Hub, select **Private Registry**.
+In **Registry source**, select where your container registry is. If it's not Azure Container Registry or Docker Hub, select **Private registry**.
 
 ::: zone pivot="container-linux"
 > [!NOTE]
@@ -63,7 +63,7 @@ Follow the next steps by selecting the tab that matches your choice.
 
 The **Registry** dropdown list displays the registries in the same subscription as your app. Select the registry you want.
 
-To deploy from a registry in a different subscription, select **Private Registry** in **Registry source** instead.
+To deploy from a registry in a different subscription, select **Private registry** in **Registry source** instead.
 
 To use managed identities to lock down Azure Container Registry access, see: 
 
diff --git a/articles/app-service/manage-scale-per-app.md b/articles/app-service/manage-scale-per-app.md
@@ -1,34 +1,34 @@
 ---
-title: Per-app scaling for high-density hosting
+title: Per-App Scaling for High-Density Hosting
 description: Scale apps independently from the App Service plans and optimize the scaled-out instances in your plan.
 author: msangapu-msft
 
 ms.assetid: a903cb78-4927-47b0-8427-56412c4e3e64
 ms.topic: article
-ms.date: 06/29/2023
+ms.date: 05/02/2025
 ms.author: msangapu
 ms.custom: devx-track-azurepowershell, devx-track-arm-template
 ---
 # High-density hosting on Azure App Service using per-app scaling
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
-When using App Service, you can scale your apps by scaling the [App Service plan](overview-hosting-plans.md) they run on. When multiple apps are running in the same App Service plan, each scaled-out instance runs all the apps in the plan.
+You can scale your apps by scaling the [App Service plan](overview-hosting-plans.md) they run on. When multiple apps are running in the same App Service plan, each scaled-out instance runs all the apps in the plan.
 
-*Per-app scaling* can be enabled at the App Service plan level to allow for scaling an app independently from the
+In contrast, *per-app scaling* can be enabled at the App Service plan level to scale an app independently from the
 App Service plan that hosts it. This way, an App Service plan can be scaled to 10 instances, but an app can be set to use only five.
 
 > [!NOTE]
 > Per-app scaling is available only for **Standard**, **Premium**, **Premium V2**, **Premium V3**, and **Isolated** pricing tiers.
 >
 
-Apps are allocated to available App Service plan using a best effort approach for an even distribution across instances. While an even distribution is not guaranteed, the platform will make sure that two instances of the same app will not be hosted on the same App Service plan instance.
+Apps are allocated to the available App Service plan using a best-effort approach for an even distribution across instances. While an even distribution isn't guaranteed, the platform makes sure that two instances of the same app aren't hosted on the same App Service plan instance.
 
-The platform does not rely on metrics to decide on worker allocation. Applications are rebalanced only when instances are added or removed from the App Service plan.
+The platform doesn't rely on metrics to decide on worker allocation. Applications are rebalanced only when instances are added or removed from the App Service plan.
 
-## Per app scaling using PowerShell
+## Per-app scaling using PowerShell
 
-Create a plan with per-app scaling by passing in the ```-PerSiteScaling $true``` parameter to the ```New-AzAppServicePlan``` cmdlet.
+Create a plan with per-app scaling by passing in the `-PerSiteScaling $true` parameter to the `New-AzAppServicePlan` cmdlet.
 
 ```powershell
 New-AzAppServicePlan -ResourceGroupName $ResourceGroup -Name $AppServicePlan `
@@ -37,29 +37,25 @@ New-AzAppServicePlan -ResourceGroupName $ResourceGroup -Name $AppServicePlan `
                             -NumberofWorkers 5 -PerSiteScaling $true
 ```
 
-Enable per-app scaling with an existing App Service Plan
-by passing in the `-PerSiteScaling $true` parameter to the
-```Set-AzAppServicePlan``` cmdlet.
+Enable per-app scaling with an existing App Service Plan by passing in the `-PerSiteScaling $true` parameter to the `Set-AzAppServicePlan` cmdlet.
 
 ```powershell
-# Enable per-app scaling for the App Service Plan using the "PerSiteScaling" parameter.
 Set-AzAppServicePlan -ResourceGroupName $ResourceGroup `
    -Name $AppServicePlan -PerSiteScaling $true
 ```
 
 At the app level, configure the number of instances the app can use in the App Service plan.
 
-In the example below, the app is limited to two instances regardless 
-of how many instances the underlying app service plan scales out to.
+In the following example, the app is limited to two instances regardless of how many instances the underlying app service plan scales out to.
 
 ```powershell
 # Get the app we want to configure to use "PerSiteScaling"
 $newapp = Get-AzWebApp -ResourceGroupName $ResourceGroup -Name $webapp
 
-# Modify the NumberOfWorkers setting to the desired value.
+# Modify the NumberOfWorkers setting to the desired value
 $newapp.SiteConfig.NumberOfWorkers = 2
 
-# Post updated app back to azure
+# Post updated app back to Azure
 Set-AzWebApp $newapp
 ```
 
@@ -70,12 +66,10 @@ Set-AzWebApp $newapp
 
 The following Azure Resource Manager template creates:
 
-- An App Service plan that's scaled out to 10 instances
-- an app that's configured to scale to a max of five instances.
+- An App Service plan that's scaled out to 10 instances.
+- An app that's configured to scale to a max of five instances.
 
-The App Service plan is setting the **PerSiteScaling** property 
-to true `"perSiteScaling": true`. The app is setting the **number of workers** 
-to use to 5 `"properties": { "numberOfWorkers": "5" }`.
+The App Service plan is setting the `PerSiteScaling` property to true `"perSiteScaling": true`. The app is setting the `number of workers` to use to 5 `"properties": { "numberOfWorkers": "5" }`.
 
 ```json
 {
@@ -126,20 +120,20 @@ to use to 5 `"properties": { "numberOfWorkers": "5" }`.
 
 ## Recommended configuration for high-density hosting
 
-Per app scaling is a feature that is enabled in both global Azure regions and [App Service Environments](environment/app-service-app-service-environment-intro.md). However, the recommended strategy is to use App Service Environments to take advantage of their advanced features and the larger App Service plan capacity.  
+Per-app scaling is a feature that's enabled in both global Azure regions and [App Service Environments](environment/app-service-app-service-environment-intro.md). However, the recommended strategy is to use App Service Environments to take advantage of their advanced features and the larger App Service plan capacity.  
 
 Follow these steps to configure high-density hosting for your apps:
 
 1. Designate an App Service plan as the high-density plan and scale it out to the desired capacity.
 1. Set the `PerSiteScaling` flag to true on the App Service plan.
-1. New apps are created and assigned to that App Service plan with the **numberOfWorkers** property set to **1**.
+1. New apps are created and assigned to that App Service plan with the `numberOfWorkers` property set to *1*.
    - Using this configuration yields the highest density possible.
 1. The number of workers can be configured independently per app to grant additional resources as needed. For example:
-   - A high-use app can set **numberOfWorkers** to **3** to have more processing capacity for that app.
-   - Low-use apps would set **numberOfWorkers** to **1**.
+   - A high-use app can set `numberOfWorkers` to *3* to have more processing capacity for that app.
+   - Low-use apps would set `numberOfWorkers` to *1*.
 
-## Next steps
+## Related content
 
-- [Azure App Service plans in-depth overview](overview-hosting-plans.md)
-- [Introduction to App Service Environment](environment/app-service-app-service-environment-intro.md)
+- [What are Azure App Service plans?](overview-hosting-plans.md)
+- [App Service Environment overview](environment/overview.md)
 - [Tutorial: Run a load test to identify performance bottlenecks in a web app](../load-testing/tutorial-identify-bottlenecks-azure-portal.md)
