Skip to content

Commit 828610c

Browse files
committed
Updates to text
1 parent a3bc5d7 commit 828610c

File tree

1 file changed

+22
-8
lines changed

1 file changed

+22
-8
lines changed

articles/reliability/reliability-app-service.md

Lines changed: 22 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -23,13 +23,13 @@ When you deploy Azure App Service, you can create multiple instances of an *App
2323

2424
::: zone pivot="free-shared-basic"
2525

26-
For production deployments, [use premium v3 or v4 App Service plans](reliability-app-service.md) to enable zone redundancy.
26+
- [Enable zone redundancy](#availability-zone-support), which requires that you use Premium v3 or Isolated v2 App Service plans and that you have at minimum three instances of the plan. To view more information, make sure that you select the appropriate tier at the top of this page.
2727

2828
::: zone-end
2929

3030
::: zone pivot="premium,isolated"
3131

32-
[Enable zone redundancy](#availability-zone-support), which requires your App Service plan to use a minimum of three instances.
32+
- [Enable zone redundancy](#availability-zone-support), which requires your App Service plan to use a minimum of three instances.
3333

3434
::: zone-end
3535

@@ -67,9 +67,15 @@ For App Service plans that aren't configured as zone redundant, virtual machine
6767

6868
### Regions supported
6969

70-
::: zone pivot="free-shared-basic,premium"
70+
::: zone pivot="free-shared-basic"
71+
72+
Zone-redundant App Service plans require that you use the Premium v2 or v3 tier and can be deployed in [any region that supports availability zones](./regions-list.md). To view more information, make sure that you select the appropriate tier at the top of this page.
73+
74+
::: zone-end
75+
76+
::: zone pivot="premium"
7177

72-
Zone-redundant App Service Premium plans can be deployed in [any region that supports availability zones](./regions-list.md).
78+
Zone-redundant App Service plans can be deployed in [any region that supports availability zones](./regions-list.md).
7379

7480
::: zone-end
7581

@@ -81,25 +87,33 @@ To see which regions support availability zones for App Service Environment v3,
8187

8288
### Requirements
8389

90+
::: zone pivot="free-shared-basic"
8491

85-
- Availability zones are only supported on the Premium v2, Premium v3, or Premium v4 plans, even if the region supports availability zones. Fpr more information, [select the Premium SKU at the top of this article](./reliability-app-service.md).
92+
- You must use either the [Premium v2 or Premium v3 plan types](/azure/app-service/overview-hosting-plans). To view more information, make sure that you select the appropriate tier at the top of this page.
93+
94+
::: zone-end
8695

8796
::: zone pivot="premium,isolated"
8897

98+
- Availability zones are only supported on the newer App Service stamps. Even if you're using one of the supported regions, if availability zones aren't supported for your resource group, you receive an error. To ensure that your workloads land on a stamp that supports availability zones, you might need to create a new resource group, App Service plan, and App Service app.
99+
89100
- You must deploy a minimum of three instances of your plan.
90101

91102
::: zone-end
92103

93104
::: zone pivot="premium,isolated"
94105

106+
### Considerations
107+
108+
Applications that are deployed in a zone-redundant App Service plan continue to run and serve traffic even if multiple zones in the region suffer an outage. However, nonruntime behaviors might still be impacted during an availability zone outage. These behaviors include App Service plan scaling, application creation, application configuration, and application publishing.
95109

96110
### Cost
97111

98112
::: zone-end
99113

100114
::: zone pivot="premium"
101115

102-
When you're using App Service Premium v3 or Premium v4 plans, there's no extra cost associated with enabling availability zones as long as you have three or more instances in your App Service plan. You're charged based on your App Service plan SKU, the capacity you specify, and any instances you scale to based on your autoscale criteria.
116+
When you're using App Service Premium v2 or Premium v3 plans, there's no extra cost associated with enabling availability zones as long as you have three or more instances in your App Service plan. You're charged based on your App Service plan SKU, the capacity you specify, and any instances you scale to based on your autoscale criteria.
103117

104118
If you enable availability zones but specify a capacity less than three, the platform enforces a minimum instance count of three. The platform charges you for those three instances.
105119

@@ -129,12 +143,12 @@ To deploy a new zone-redundant Azure App Service Environment, see [Create an App
129143

130144
Zone redundancy can only be configured when you create a new App Service plan. If you have an existing App Service plan that isn't zone-redundant, replace it with a new zone-redundant plan. You can't convert an existing App Service plan to use availability zones. Similarly, you can't disable zone redundancy on an existing App Service plan.
131145

132-
133146
::: zone pivot="premium,isolated"
134147

148+
135149
### Capacity planning and management
136150

137-
To prepare for availability zone failure, consider *over-provisioning* the capacity of your integration runtime. Over-provisioning allows the solution to tolerate some degree of capacity loss and still continue to function without degraded performance. To learn more about over-provisioning, see [Manage capacity with over-provisioning](./concept-redundancy-replication-backup.md#manage-capacity-with-over-provisioning).
151+
To prepare for availability zone failure, consider *over-provisioning* the capacity of your App Service plan. Over-provisioning allows the solution to tolerate some degree of capacity loss and still continue to function without degraded performance. To learn more about over-provisioning, see [Manage capacity with over-provisioning](./concept-redundancy-replication-backup.md#manage-capacity-with-over-provisioning).
138152

139153

140154
### Normal operations

0 commit comments

Comments
 (0)