updating images

Author: seligj95

articles/app-service/environment/how-to-migrate.md

@@ -60,7 +60,7 @@ Run the following command to check the status of this step.
 az rest --method get --uri "${ASE_ID}?api-version=2021-02-01" --query properties.status
 ```
 
-If it's in progress, you'll get a status of "Migrating". Once you get a status of "Ready", run the following command to get your new IPs. If you don't see the new IPs immediately, wait a few minutes and try again.
+If it's in progress, you'll get a status of "Migrating". Once you get a status of "Ready", run the following command to view your new IPs. If you don't see the new IPs immediately, wait a few minutes and try again.
 
 ```azurecli
 az rest --method get --uri "${ASE_ID}/configurations/networking?api-version=2021-02-01"

articles/app-service/environment/media/migration/back-up-restore-sample.png

@@ -39,9 +39,9 @@ App Service Environment v3 uses Isolated v2 App Service plans that are priced an
 
 The [back up and restore](../manage-backup.md) feature allows you to keep your app configuration, file content, and database connected to your app when migrating to your new environment. Make sure you review the [details](../manage-backup.md#automatic-vs-custom-backups) of this feature.
 
-The step-by-step instructions in the current documentation for [backup and restore](../manage-backup.md) should be sufficient to allow you to use this feature. When restoring, the **Storage** option lets you select any backup ZIP file from any existing Azure Storage account container in your subscription. A sample of a restore configuration is given in the following screenshot.
+The step-by-step instructions in the current documentation for [backup and restore](../manage-backup.md) should be sufficient to allow you to use this feature. You can select a backup and use that to restore the app to an App Service in your App Service Environment v3.
 
-![back up and restore sample](./media/migration/back-up-restore-sample.png)
+:::image type="content" source="./media/migration/back-up-restore-sample.png" alt-text="Use backup to restore App Service in App Service Environment v3.":::
 
 |Benefits     |Limitations    |
 |---------|---------|
@@ -71,7 +71,7 @@ To clone an app using the [Azure portal](https://www.portal.azure.com), navigate
 1. You can use an existing Windows **App Service plan** from your new environment if you created one already, or create a new one. The available Windows App Service plans in your new App Service Environment v3, if any, will be listed in the dropdown.
 1. Modify **SKU and size** as needed using one of the Isolated v2 options if creating a new App Service plan. Note App Service Environment v3 uses Isolated v2 plans, which have more memory and CPU per corresponding instance size compared to the Isolated plan. For more information, see [App Service Environment v3 SKU details](overview.md#pricing).
 
-![clone sample](./media/migration/portal-clone-sample.png)
+:::image type="content" source="./media/migration/portal-clone-sample.png" alt-text="Clone an app to App Service Environment v3 using the portal.":::
 
 |Benefits     |Limitations     |
 |---------|---------|
@@ -81,19 +81,19 @@ To clone an app using the [Azure portal](https://www.portal.azure.com), navigate
 
 ## Manually create your apps on an App Service Environment v3
 
-If the above features don't support your apps or you're looking to take a more manual route, you have the option of deploying your apps following the same process you used for your existing App Service Environment. You don't need to make updates when you deploy your apps to your new environment unless you want to make changes or take advantage of App Service Environment v3's dedicated features.
+If the above features don't support your apps or you're looking to take a more manual route, you have the option of deploying your apps following the same process 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, head over to your App Service and go to **Export template** under **Automation**.
+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, navigate to your App Service and go to **Export template** under **Automation**.
 
-![export from toc](./media/migration/export-toc.png)
+:::image type="content" source="./media/migration/export-toc.png" alt-text="Export App Service from TOC.":::
 
 You can also export templates for multiple resources directly from your resource group by going to your resource group, selecting the resources you want a template for, and then selecting **Export template**.
 
-![export template sample](./media/migration/export-template-sample.png)
+:::image type="content" source="./media/migration/export-template-sample.png" alt-text="Export template for resources from resource group.":::
 
 The following initial changes to your Azure Resource Manager templates are required to get your apps onto your App Service Environment v3:
 
-- Update SKU parameters for App Service plan to an Isolated v2 plan as shown below
+- Update SKU parameters for App Service plan to an Isolated v2 plan:
 
     ```json
     "type": "Microsoft.Web/serverfarms",
@@ -153,7 +153,7 @@ Once your migration and any testing with your new environment is complete, delet
 - **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 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 or any time after that. 
 - **What if my App Service Environment is zone pinned?**  
-  Zone pinning isn't a supported feature on App Service Environment v3. Use [zone redundancy](overview-zone-redundancy.md) instead.
+  Zone pinning isn't a supported feature on App Service Environment v3.
 - **What properties of my App Service Environment will change?**  
   You'll now be on App Service Environment v3 so be sure to review the [features and feature differences](overview.md#feature-differences) compared to previous versions. For ILB App Service Environment, you'll keep the same ILB IP address. For internet facing App Service Environment, the public IP address and the outbound IP address will change. Note for internet facing App Service Environment, previously there was a single IP for both inbound and outbound. For App Service Environment v3, they're separate. For more information, see [App Service Environment v3 networking](networking.md#addresses).
 - **What will happen to my App Service Environment v1/v2 resources after 31 August 2024?**