You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/environment/migrate.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ App Service can now automate migration of your App Service Environment v1 and v2
17
17
18
18
## Supported scenarios
19
19
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:
21
21
22
22
### Azure Public:
23
23
@@ -28,16 +28,12 @@ At this time, App Service Environment migrations to v3 don't support migrations
28
28
### Azure Government:
29
29
30
30
- US DoD Central
31
-
- US DoD East
32
31
- US Gov Arizona
33
-
- US Gov Iowa
34
32
35
33
### Azure China:
36
34
37
35
- China East 2
38
-
- China East 3
39
36
- China North 2
40
-
- China North 3
41
37
42
38
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.
0 commit comments