edit pass: two-app-service-environment-migration-articles

ShawnJackson · ShawnJackson · commit 23d27fc6125f · 2024-02-01T15:15:26.000-06:00
diff --git a/articles/app-service/environment/how-to-migrate.md b/articles/app-service/environment/how-to-migrate.md
@@ -118,7 +118,7 @@ If your existing App Service Environment uses a custom domain suffix, you need t
 
 If your migration doesn't include a custom domain suffix and you aren't enabling zone redundancy, you can move on to migration.
 
-To set these configurations, create a file called *parameters.json* with the following details based on your scenario. Don't include the custom domain suffix properties if this feature doesn't apply to your migration. Pay attention to the value of the `zoneRedundant` property, because this configuration is irreversible after migration. Set the value of the `kind` property based on your existing App Service Environment version. Accepted values for the `kind` property are `ASEV1` and `ASEV2`.
+To set these configurations, create a file called *parameters.json* with the following details based on your scenario. Don't include the properties for a custom domain suffix if this feature doesn't apply to your migration. Pay attention to the value of the `zoneRedundant` property, because this configuration is irreversible after migration. Set the value of the `kind` property based on your existing App Service Environment version. Accepted values for the `kind` property are `ASEV1` and `ASEV2`.
 
 If you're migrating without a custom domain suffix and you're enabling zone redundancy, use this code:
 
@@ -211,7 +211,7 @@ az appservice ase show --name $ASE_NAME --resource-group $ASE_RG
 
 ## 1. Validate that migration is supported
 
-In the [Azure portal](https://portal.azure.com), go to the **Migration** page for the App Service Environment that you're migrating. You can get to the migration page by selecting the banner at the top of the **Overview** page for your App Service Environment, or by selecting the **Migration** item on the left menu.
+In the [Azure portal](https://portal.azure.com), go to the **Migration** page for the App Service Environment that you're migrating. You can get to the **Migration** page by selecting the banner at the top of the **Overview** page for your App Service Environment, or by selecting the **Migration** item on the left menu.
 
 :::image type="content" source="./media/migration/portal-overview.png" alt-text="Screenshot that shows migration access points.":::
 
@@ -225,7 +225,7 @@ If your App Service Environment isn't supported for migration at this time or yo
 
 :::image type="content" source="./media/migration/migration-not-supported.png" alt-text="Screenshot that shows an example portal message that says the migration feature doesn't support the App Service Environment.":::
 
-If migration is supported for your App Service Environment, proceed to the next step in the process. The migration page guides you through the series of steps to complete the migration.
+If migration is supported for your App Service Environment, proceed to the next step in the process. The **Migration** page guides you through the series of steps to complete the migration.
 
 :::image type="content" source="./media/migration/migration-ux-pre.png" alt-text="Screenshot that shows a sample migration page with unfinished steps in the process.":::
 
@@ -310,7 +310,7 @@ If your migration included a custom domain suffix, the domain appeared in the **
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Use an App Service Environment v3](using.md)
+> [Use an App Service Environment v3 instance](using.md)
 
 > [!div class="nextstepaction"]
 > [App Service Environment v3 networking](networking.md)
diff --git a/articles/app-service/environment/migration-alternatives.md b/articles/app-service/environment/migration-alternatives.md
@@ -61,15 +61,18 @@ You can select a custom backup and restore it to App Service in your App Service
 |You can integrate with [Azure Traffic Manager](../../traffic-manager/traffic-manager-overview.md) and [Azure Application Gateway](../../application-gateway/overview.md) to distribute traffic across old and new environments.          |Using a [storage account with private endpoints](../../storage/common/storage-private-endpoints.md) for backup and restore isn't supported.  |
 |You can create empty web apps to restore to in your new environment before you start restoring, to speed up the process.   | Only custom backups are supported.       |
 
-## Clone your app to an App Service Environment v3
+## Clone your app to App Service Environment v3
 
-[Cloning your apps](../app-service-web-app-cloning.md) is another feature that you can use to get your Windows apps onto App Service Environment v3. The limitations for cloning apps are the same as those for the App Service backup feature, though the feature is supported for App Service plans on Windows only. For more information, see [Back up an app in Azure App Service](../manage-backup.md#whats-included-in-an-automatic-backup).
+[Cloning your apps](../app-service-web-app-cloning.md) is another feature that you can use to get your *Windows* apps onto App Service Environment v3. The limitations for cloning apps are the same as those for the App Service backup feature. For more information, see [Back up an app in Azure App Service](../manage-backup.md#whats-included-in-an-automatic-backup).
 
-We recommend this solution for users who are using App Service in Windows and can't migrate by using the [migration feature](migrate.md). You need to set up your new App Service Environment v3 instance before you clone any apps. Cloning an app can take up to 30 minutes to complete.
+> [!NOTE]
+> Cloning apps is supported for App Service plans on Windows only.
+
+We recommend this solution for users who are using App Service on Windows and can't migrate by using the [migration feature](migrate.md). You need to set up your new App Service Environment v3 instance before you clone any apps. Cloning an app can take up to 30 minutes to complete.
 
 To clone an app by using PowerShell, see the [instructions](../app-service-web-app-cloning.md#cloning-an-existing-app-to-an-app-service-environment).
 
-To clone an app using the Azure portal:
+To clone an app by using the Azure portal:
 
 1. In the [Azure portal](https://portal.azure.com), go to your existing App Service plan. Under **Development Tools**, select **Clone App**.
 1. Fill in the required fields by using the details for your new App Service Environment v3 instance:
@@ -78,7 +81,7 @@ To clone an app using the Azure portal:
    1. For **Name**, give your app a name. This name can be the same as the old app, but the site's default URL for the new environment will be different. You need to update any custom DNS or connected resources to point to the new URL.
    1. For **Region**, use your App Service Environment v3 name.
    1. If you want to clone your deployment source, select the **Clone deployment source** checkbox.
-   1. For **Windows Plan**, you can use an existing App Service plan from your new environment if you created one already, or you can create a new one. The available App Service plans in your new App Service Environment v3 instance appear in the dropdown list.
+   1. For **Windows Plan**, you can use an existing App Service plan from your new environment if you created one already, or you can create a new plan. The available App Service plans in your new App Service Environment v3 instance appear in the dropdown list.
    1. For **Sku and size**, modify the memory and CPU as needed by using one of the Isolated v2 options if you're creating a new App Service plan. App Service Environment v3 uses Isolated v2 plans, which have more memory and CPU per corresponding instance size compared to the Isolated plans. For more information, see the [App Service Environment v3 pricing details](overview.md#pricing).
 
 :::image type="content" source="./media/migration/portal-clone-sample.png" alt-text="Screenshot that shows options for cloning an app to App Service Environment v3 by using the portal.":::
@@ -93,7 +96,7 @@ To clone an app using the Azure portal:
 
 If the migration feature doesn't support your apps or you want to take a more manual route, you can deploy your apps by following the same process that you used for your existing App Service Environment. You don't need to make updates when you deploy your apps to your new environment.
 
-You can export [Azure Resource Manager (ARM) templates](../../azure-resource-manager/templates/overview.md) of your existing apps, App Service plans, and any other supported resources and deploy them in or with your new environment. To export a template for just your app, go to your App Service plan. Under **Automation**, select **Export template**.
+You can export [Azure Resource Manager (ARM) templates](../../azure-resource-manager/templates/overview.md) of your existing apps, App Service plans, and any other supported resources and deploy them in or with your new environment. To export a template for just an app, go to your App Service plan. Under **Automation**, select **Export template**.
 
 :::image type="content" source="./media/migration/export-toc.png" alt-text="Screenshot of the option to export a template on the left pane of the Azure portal.":::
 
@@ -164,7 +167,7 @@ After your migration and any testing with your new environment are complete, del
   No. Apps that run on App Service Environment v1 and v2 shouldn't need any modifications to run on App Service Environment v3. If you're using IP SSL, you must remove the IP SSL bindings before migrating.
 - **What if my App Service Environment has a custom domain suffix?**  
   The migration feature supports this [migration scenario](./migrate.md#supported-scenarios). You can migrate by using a manual method if you don't want to use the migration feature. You can configure your [custom domain suffix](./how-to-custom-domain-suffix.md) when creating your App Service Environment v3 instance or any time after.
-- **What if my App Service Environment v2 is zone pinned?**  
+- **What if my App Service Environment v2 instance is zone pinned?**  
   Zone pinning isn't a supported feature on App Service Environment v3. You can choose to enable zone redundancy when creating your App Service Environment v3 instance.
 - **What properties of my App Service Environment will change?**  
   Review the [feature differences](overview.md#feature-differences) between App Service Environment v3 and previous versions. For ILB App Service Environments, you keep the same ILB IP address. For internet-facing App Service Environments, the public IP address and the outbound IP address change.
@@ -173,9 +176,9 @@ After your migration and any testing with your new environment are complete, del
 - **Is backup and restore supported for moving apps from App Service Environment v2 to v3?**
   The [back up and restore](../manage-backup.md) feature supports restoring apps between App Service Environment versions as long as you use a custom backup for the restoration. Automatic backup doesn't support restoration to different App Service Environment versions.
 - **What will happen to my App Service Environment v1 and v2 resources after August 31, 2024?**  
-  After August 31, 2024, if you haven't migrated to App Service Environment v3, your [App Service Environment v1 and v2 instances and the apps deployed in them will no longer be available](https://azure.microsoft.com/updates/app-service-environment-v1-and-v2-retirement-announcement/).
+  After August 31, 2024, if you haven't migrated to App Service Environment v3, your App Service Environment v1 and v2 instances and the apps deployed in them will no longer be available.
   
-  App Service Environment v1 and v2 are hosted on App Service scale units that run on [Azure Cloud Services (classic)](../../cloud-services/cloud-services-choose-me.md) architecture. Because this architecture will be [retired on August 31, 2024](https://azure.microsoft.com/updates/cloud-services-retirement-announcement/), App Service Environment v1 and v2 won't be available after that date. Migrate to App Service Environment v3 to keep your apps running, or save or back up any resources or data that you need to maintain.
+  App Service Environment v1 and v2 are hosted on App Service scale units that run on [Azure Cloud Services (classic)](../../cloud-services/cloud-services-choose-me.md) architecture. Because this architecture will be [retired on August 31, 2024](https://azure.microsoft.com/updates/cloud-services-retirement-announcement/), App Service Environment v1 and v2 [won't be available after that date](https://azure.microsoft.com/updates/app-service-environment-v1-and-v2-retirement-announcement/). Migrate to App Service Environment v3 to keep your apps running, or save or back up any resources or data that you need to maintain.
 
 ## Next steps
 
