Skip to content

Commit f64b6b9

Browse files
committed
update
1 parent 7ff0ae6 commit f64b6b9

File tree

2 files changed

+9
-5
lines changed

2 files changed

+9
-5
lines changed

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

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use the migration feature to migrate your App Service Environment to App
33
description: Learn how to migrate your App Service Environment to App Service Environment v3 using the migration feature
44
author: seligj95
55
ms.topic: tutorial
6-
ms.date: 9/15/2022
6+
ms.date: 10/21/2022
77
ms.author: jordanselig
88
zone_pivot_groups: app-service-cli-portal
99
---
@@ -19,6 +19,10 @@ An App Service Environment v1 and v2 can be automatically migrated to an [App Se
1919

2020
Ensure you understand how migrating to an App Service Environment v3 will affect your applications. Review the [migration process](migrate.md#overview-of-the-migration-process-using-the-migration-feature) to understand the process timeline and where and when you'll need to get involved. Also review the [FAQs](migrate.md#frequently-asked-questions), which may answer some questions you currently have.
2121

22+
Ensure there are no locks on your virtual network. Virtual network locks will block platform operations during migration.
23+
24+
:::image type="content" source="./media/migration/vnet-locks.png" alt-text="Screenshot that shows where to find and update virtual network locks.":::
25+
2226
::: zone pivot="experience-azcli"
2327

2428
The recommended experience for the migration feature is using the [Azure portal](how-to-migrate.md?pivots=experience-azp). If you decide to use the Azure CLI to carry out the migration, you should follow the steps described here in order and as written since you'll be making Azure REST API calls. The recommended way for making these API calls is by using the [Azure CLI](/cli/azure/). For information about other methods, see [Getting Started with Azure REST](/rest/api/azure/).
@@ -175,11 +179,11 @@ From the [Azure portal](https://portal.azure.com), navigate to the **Migration**
175179

176180
On the migration page, the platform will validate if migration is supported for your App Service Environment. If your environment isn't supported for migration, a banner will appear at the top of the page and include an error message with a reason. See the [troubleshooting](migrate.md#troubleshooting) section for descriptions of the error messages you may see if you aren't eligible for migration. If your App Service Environment isn't supported for migration at this time or your environment is in an unhealthy or suspended state, you won't be able to use the migration feature. If your environment [won't be supported for migration with the migration feature](migrate.md#supported-scenarios) or you want to migrate to App Service Environment v3 without using the migration feature, see the [manual migration options](migration-alternatives.md).
177181

178-
:::image type="content" source="./media/migration/migration-not-supported.png" alt-text="Migration not supported sample.":::
182+
:::image type="content" source="./media/migration/migration-not-supported.png" alt-text="Screenshot that shows what the portal looks like when migration is not supported.":::
179183

180184
If migration is supported for your App Service Environment, you'll be able to proceed to the next step in the process. The migration page will guide you through the series of steps to complete the migration.
181185

182-
:::image type="content" source="./media/migration/migration-ux-pre.png" alt-text="Migration page sample.":::
186+
:::image type="content" source="./media/migration/migration-ux-pre.png" alt-text="Screenshot that shows a sample migration page.":::
183187

184188
## 2. Generate IP addresses for your new App Service Environment v3
185189

@@ -189,13 +193,13 @@ Under **Get new IP addresses**, confirm you understand the implications and star
189193

190194
When the previous step finishes, you'll be shown the IP addresses for your new App Service Environment v3. Using the new IPs, update any resources and networking components to ensure your new environment functions as intended once migration is complete. It's your responsibility to make any necessary updates. Don't move on to the next step until you confirm that you have made these updates.
191195

192-
:::image type="content" source="./media/migration/ip-sample.png" alt-text="Sample IPs generated during pre-migration.":::
196+
:::image type="content" source="./media/migration/ip-sample.png" alt-text="Screenshot that shows sample IPs generated during pre-migration.":::
193197

194198
## 4. Delegate your App Service Environment subnet
195199

196200
App Service Environment v3 requires the subnet it's in to have a single delegation of `Microsoft.Web/hostingEnvironments`. Previous versions didn't require this delegation. You'll need to confirm your subnet is delegated properly and/or update the delegation if needed before migrating. A link to your subnet is given so that you can confirm and update as needed.
197201

198-
:::image type="content" source="./media/migration/subnet-delegation-ux.png" alt-text="Subnet delegation using the portal.":::
202+
:::image type="content" source="./media/migration/subnet-delegation-ux.png" alt-text="Screenshot that shows subnet delegation using the portal.":::
199203

200204
## 5. Choose your configurations
201205

109 KB
Loading

0 commit comments

Comments
 (0)