Skip to content

Commit 1c2f8cc

Browse files
authored
ordering alphabetically
1 parent ece25de commit 1c2f8cc

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

articles/reliability/migrate-app-service.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -33,28 +33,28 @@ Availability zone support is a property of the App Service plan. The following a
3333
- Minimum instance count of three is enforced.
3434
- The platform will enforce this minimum count behind the scenes if you specify an instance count fewer than three.
3535
- Can be enabled in any of the following regions:
36-
- West US 2
37-
- West US 3
36+
- Australia East
37+
- Brazil South
38+
- Canada Central
39+
- Central India
3840
- Central US
41+
- East Asia
3942
- East US
4043
- East US 2
41-
- South Central US
42-
- Canada Central
43-
- Brazil South
44+
- France Central
45+
- Germany West Central
46+
- Japan East
4447
- North Europe
45-
- West Europe
48+
- Qatar Central
49+
- South Central US
50+
- Southeast Asia
4651
- Sweden Central
47-
- Germany West Central
48-
- France Central
49-
- UK South
5052
- Switzerland North
5153
- UAE North
52-
- Japan East
53-
- East Asia
54-
- Southeast Asia
55-
- Qatar Central
56-
- Central India
57-
- Australia East
54+
- UK South
55+
- West Europe
56+
- West US 2
57+
- West US 3
5858
- Availability zones can only be specified when creating a **new** App Service plan. A pre-existing App Service plan can't be converted to use availability zones.
5959
- Availability zones are only supported in the newer portion of the App Service footprint.
6060
- Currently, if you're running on Pv3, then it's possible that you're already on a footprint that supports availability zones. In this scenario, you can create a new App Service plan and specify zone redundancy.

0 commit comments

Comments
 (0)