Skip to content

Commit b7ed549

Browse files
Merge pull request #268110 from seligj95/patch-2
add migration statuses
2 parents 6e66ccd + 0ebfee5 commit b7ed549

File tree

2 files changed

+12
-1
lines changed

2 files changed

+12
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -305,7 +305,7 @@ This step takes three to six hours for v2 to v3 migrations and up to six hours f
305305
>
306306
> :::image type="content" source="./media/migration/migration-error-2.png" alt-text="Screenshot that shows the potential error notification after migration starts.":::
307307
308-
At this time, detailed migration statuses are available only when you're using the Azure CLI. For more information, see the [Azure CLI section for migrating to App Service Environment v3](#8-migrate-to-app-service-environment-v3-and-check-status).
308+
At this time, detailed migration statuses are available only when you're using the Azure CLI. For more information, see the Azure CLI section for migrating to App Service Environment v3. You can check the status of the migration with the CLI even if you use the portal to do the migration.
309309

310310
When migration is complete, you have an App Service Environment v3 resource, and all of your apps are running in your new environment. You can confirm the environment's version by checking the **Configuration** page for your App Service Environment.
311311

articles/app-service/environment/migrate.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -151,6 +151,17 @@ Migration requires a three to six hour service window for App Service Environmen
151151
- If you can't support downtime, see the [side-by-side migration feature](side-by-side-migrate.md) or the [migration-alternatives](migration-alternatives.md#migrate-manually).
152152
- The public addresses that are used by the App Service Environment change to the IPs generated during the IP generation step.
153153

154+
The following statuses are available during the migration process:
155+
156+
|Status |Description |
157+
|------------|-------------|
158+
|Validating and preparing the migration. |The platform is validating migration support and performing necessary checks. |
159+
|Deploying App Service Environment v3 infrastructure. |Your new App Service Environment v3 infrastructure is provisioning. |
160+
|Waiting for infrastructure to complete. |The platform is validating your new infrastructure and performing necessary checks. |
161+
|Setting up networking. Migration downtime period has started. Applications are not accessible. |The platform is deleting your old infrastructure and moving all of your apps to your new App Service Environment v3. Your apps are down and aren't accepting traffic. |
162+
|Running post migration validations. |The platform is performing necessary checks to ensure the migration succeeded. |
163+
|Finalizing migration. |The platform is finalizing the migration. |
164+
154165
As in the IP generation step, you can't scale, modify your App Service Environment, or deploy apps to it during this process. When migration is complete, the apps that were on the old App Service Environment are running on the new App Service Environment v3.
155166

156167
## Pricing

0 commit comments

Comments
 (0)