Skip to content

Commit 67c8a33

Browse files
committed
updates
1 parent ed2dedb commit 67c8a33

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

articles/app-service/environment/migrate.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ App Service can now automate migration of your App Service Environment v1 and v2
1717
1818
## Supported scenarios
1919

20-
At this time, App Service Environment migrations to v3 don't support migrations in the following regions:
20+
At this time, the migration feature doesn't support migrations to App Service Environment v3 in the following regions:
2121

2222
### Azure Public:
2323

@@ -28,16 +28,12 @@ At this time, App Service Environment migrations to v3 don't support migrations
2828
### Azure Government:
2929

3030
- US DoD Central
31-
- US DoD East
3231
- US Gov Arizona
33-
- US Gov Iowa
3432

3533
### Azure China:
3634

3735
- China East 2
38-
- China East 3
3936
- China North 2
40-
- China North 3
4137

4238
The following App Service Environment configurations can be migrated using the migration feature. The table gives the App Service Environment v3 configuration you'll end up with when using the migration feature based on your existing App Service Environment. All supported App Service Environments can be migrated to a [zone redundant App Service Environment v3](../../availability-zones/migrate-app-service-environment.md) using the migration feature as long as the environment is [in a region that supports zone redundancy](./overview.md#regions). You can [configure zone redundancy](#choose-your-app-service-environment-v3-configurations) during the migration process.
4339

0 commit comments

Comments
 (0)