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/configure-zone-redundancy.md
+18-14Lines changed: 18 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,21 +10,22 @@ ms.author: anaharris
10
10
---
11
11
# Configure App Service plans for zone redundancy
12
12
13
-
Azure App Service provides built-in reliability features to help ensure your applications are available and resilient. This article describes how to create your App Service plan with zone redundancy. It also covers how to disable and enable zone redundancy on existing plans, and how to check for zone redundancy support. For more information about how App Service supports zone redundancy, see [Reliability in App Service](../reliability/reliability-app-service.md).
13
+
Azure App Service provides built-in reliability features to help ensure that your applications remain available and resilient. This article describes how to create an App Service plan that includes zone redundancy. It also covers how to disable and enable zone redundancy on existing plans and how to check for zone redundancy support. For more information about zone redundancy, see [Reliability in App Service](../reliability/reliability-app-service.md).
14
14
15
-
## Create a new App Service plan with zone redundancy
15
+
## Create a new App Service plan that includes zone redundancy
16
16
17
-
To create a new App Service plan with zone redundancy, follow the appropriate steps.
17
+
To create a new App Service plan that includes zone redundancy, follow the appropriate steps.
18
18
19
19
# [Azure portal](#tab/portal)
20
20
21
-
Follow the guidance to [create an App Service plan](../app-service/app-service-plan-manage.md#create-an-app-service-plan). Make sure to select *Enabled* for **Zone redundancy**.
21
+
Follow the guidance to [create an App Service plan](../app-service/app-service-plan-manage.md#create-an-app-service-plan). Make sure to select **Enabled** for **Zone redundancy**.
22
22
23
23
:::image type="content" source="./media/configure-zone-redundancy/app-service-create-zr-plan.png" alt-text="Screenshot of zone redundancy enablement during App Service plan creation in the Azure portal.":::
24
24
25
25
# [Azure CLI](#tab/azurecli)
26
26
27
-
Set the `--zone-redundant` argument. You must also set the `--number-of-workers` argument, which is the number of instances, to a value of 2 or more.
27
+
- Set the `--zone-redundant` argument.
28
+
- Set the `--number-of-workers` argument, which is the number of instances, to a value of 2 or more.
28
29
29
30
```azurecli
30
31
az appservice plan create \
@@ -37,7 +38,8 @@ az appservice plan create \
37
38
38
39
# [Bicep](#tab/bicep)
39
40
40
-
Set the `zoneRedundant` property to `true`. You must also set the `sku.capacity` property to a value of 2 or more. If you don't define the `sku.capacity` property, the value defaults to 1.
41
+
- Set the `zoneRedundant` property to `true`.
42
+
- Set the `sku.capacity` property to a value of 2 or more. If you don't define the `sku.capacity` property, the value defaults to 1.
## Set zone redundancy for an existing App Service plan
61
63
62
64
1. To enable zone redundancy on an existing App Service plan, [check for zone redundancy support](#check-for-zone-redundancy-support-on-an-app-service-plan).
63
-
1. If your App Service plan supports zone redundancy, use the Azure portal, Azure CLI, or Bicep and Azure Resource Manager to enable or disable it.
65
+
1. If your App Service plan supports zone redundancy, use the Azure portal, the Azure CLI, or Bicep and Azure Resource Manager to enable or disable it.
64
66
65
67
# [Azure portal](#tab/portal)
66
68
67
69
1. In the [Azure portal](https://portal.azure.com), go to your App Service plan.
68
70
1. Select **Settings > Scale out (App Service plan)** in the left navigation pane.
69
-
1. Select **Zone redundancy** to enable zone redundancy. Deselect it to disable it.
71
+
1. Select **Zone Redundancy** to enable zone redundancy. Deselect it to disable it.
70
72
71
73
The zone redundancy status of an App Service plan changes almost instantaneously. No downtime or performance problems occur during the process.
- To *enable zone redundancy*, set the `zoneRedundant` property to `true`. You must also specify the `sku.capacity` argument, which is the number of instances, to a value of 2 or more.
82
+
- To *enable zone redundancy*, set the `zoneRedundant` property to `true`.
83
+
- Set the `sku.capacity` argument, which is the number of instances, to a value of 2 or more.
- To *enable zone redundancy*, set the `zoneRedundant` property to `true`. You must also define the `sku.capacity` property to a value of 2 or more. If you don't define the `sku.capacity` property, the value defaults to 1.
103
+
- To *enable zone redundancy*, set the `zoneRedundant` property to `true`.
104
+
- Set the `sku.capacity` property to a value of 2 or more. If you don't define the `sku.capacity` property, the value defaults to 1.
## Check for zone redundancy support on an App Service plan
123
127
124
-
To see whether an existing App Service plan supports zone redundancy, do the following steps:
128
+
To check whether an existing App Service plan supports zone redundancy, do the following steps:
125
129
126
130
1. Determine the maximum number of availability zones that the App Service plan supports by using the Azure portal, Azure CLI, or Bicep and Resource Manager.
127
131
@@ -131,7 +135,7 @@ To see whether an existing App Service plan supports zone redundancy, do the fol
131
135
132
136
1. Select **Scale out (App Service plan)**.
133
137
134
-
Under **Maximum available zones**, see the maximum number of zones that your App Service plan can use.
138
+
**Maximum available zones** shows the maximum number of zones that your App Service plan can use.
135
139
136
140
:::image type="content" source="./media/configure-zone-redundancy/app-service-plan-max-zones-portal.png" alt-text="Screenshot of the maximum available zones property in the scale-out section in the Azure portal for an App Service plan.":::
137
141
@@ -168,11 +172,11 @@ To see whether an existing App Service plan supports zone redundancy, do the fol
168
172
| More than 1 | Supported |
169
173
| Equal to 1 | Not supported* |
170
174
171
-
\* If you're on a plan or a stamp that doesn't support availability zones, you must create a new App Service plan in a new resource group. This setup ensures that your deployment lands on App Service infrastructure that supports availability zones.
175
+
\* If you use a plan or a stamp that doesn't support availability zones, you must create a new App Service plan in a new resource group. This setup ensures that your deployment lands on App Service infrastructure that supports availability zones.
172
176
173
177
## View physical zones for an App Service plan
174
178
175
-
When you have a zone-redundant App Service plan, the platform automatically places the instances across [physical availability zones](../reliability/availability-zones-overview.md#physical-and-logical-availability-zones). To verify that your instances are spread across zones, use the Azure portal or Azure CLI to check which physical availability zones your plan's instances use.
179
+
When you have a zone-redundant App Service plan, the platform automatically places the instances across [physical availability zones](../reliability/availability-zones-overview.md#physical-and-logical-availability-zones). To verify that your instances are spread across zones, use the Azure portal or the Azure CLI to check which physical availability zones your plan's instances use.
Copy file name to clipboardExpand all lines: articles/app-service/environment/overview.md
+25-22Lines changed: 25 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,51 +78,51 @@ An App Service Environment v3 in its subnet uses a variable number of addresses,
78
78
79
79
The apps in an App Service Environment can access resources on the same virtual network as App Service Environment without extra configuration. If the App Service Environment virtual network connects to another network, the apps in the App Service Environment can access resources in those extended networks. But user configuration on the network can block traffic.
80
80
81
-
The multitenant version of Azure App Service includes numerous features that let your apps connect to various networks. With these networking features, your apps function as if they're deployed on a virtual network. Apps in an App Service Environment v3 don't require added configuration to run on the virtual network.
81
+
The multitenant version of Azure App Service includes numerous features that let your apps connect to various networks. These networking features enable your apps to function as if they're deployed on a virtual network. Apps in an App Service Environment v3 don't require added configuration to run on the virtual network.
82
82
83
83
A key benefit of using an App Service Environment instead of a multitenant service is that network access controls for the App Service Environment-hosted apps exist outside the application configuration. In a multitenant service, you must enable the features on each app individually and use role-based access control or a policy to prevent configuration changes.
84
84
85
85
## Feature differences
86
86
87
87
App Service Environment v3 differs from earlier versions in the following ways:
88
88
89
-
-There are no networking dependencies on the customer's virtual network. You can secure all inbound and outbound traffic and route outbound traffic as you want.
89
+
-It has no networking dependencies on the customer's virtual network. You can secure all inbound and outbound traffic and route outbound traffic as needed.
90
90
91
-
- You can deploy an App Service Environment v3 with zone redundancy enabled. You set zone redundancy only in regions where all App Service Environment v3 dependencies support zone redundancy. You can enable zone redundancy at creation or anytime after deployment. With a zone-redundant App Service Environment, each App Service plan must have at least two instances so that they can be spread across zones. Each App Service plan's zone redundancy status is independent, so you can have a mix of zone-redundant and non-zone-redundant plans. To make plans zone redundant, the App Service Environment must have zone redundancy enabled. Non-zone-redundant plans can be scaled down to a single instance. For more information, see [Reliability in Azure App Service](../../reliability/reliability-app-service.md?pivots=isolated).
91
+
- You can deploy an App Service Environment v3 with zone redundancy enabled. You set zone redundancy only in regions where all App Service Environment v3 dependencies support zone redundancy. You can enable zone redundancy at creation or anytime after deployment. With a zone-redundant App Service Environment, each App Service plan must have at least two instances to distribute them across zones. Each App Service plan's zone redundancy status is independent, so you can use a mix of zone-redundant and non-zone-redundant plans. To make plans zone redundant, the App Service Environment must have zone redundancy enabled. You can scale non-zone-redundant plans down to a single instance. For more information, see [Reliability in Azure App Service](../../reliability/reliability-app-service.md?pivots=isolated).
92
92
93
93
- You can deploy an App Service Environment v3 on a dedicated host group. Host group deployments aren't zone redundant.
94
94
95
-
-Scaling is faster than with an App Service Environment v2. Scaling is much faster than in the multitenant service, but it isn't immediate.
95
+
-It scales faster than an App Service Environment v2. Scaling is much faster than in the multitenant service, but it isn't immediate.
96
96
97
-
-Front-end scaling adjustments are no longer required. App Service Environment v3 front ends automatically scale to meet your needs and are deployed on better hosts.
97
+
-It no longer requires front-end scaling adjustments. App Service Environment v3 front ends automatically scale to meet your needs and are deployed on improved hosts.
98
98
99
-
-Scaling no longer prevents other scale operations within App Service Environment v3. Only one scale operation runs at a time for a combination of OS and size. For example, while your Windows small App Service plan is scaling, you can start a scale operation for a Windows medium plan or any other plan except Windows small.
99
+
-It allows other scale operations to proceed while an operation is in progress, as long as they involve different OS and size combinations. For example, while your Windows small App Service plan scales, you can start a scale operation for a Windows medium plan or any other plan except Windows small.
100
100
101
-
-You can reach apps in an internal-VIP App Service Environment v3 across global peering. This access wasn't possible in earlier versions.
101
+
-It supports access to apps in an internal-VIP App Service Environment v3 across global peering. Earlier versions don't support this access.
102
102
103
-
A few features that were available in earlier versions of App Service Environment aren't available in App Service Environment v3. For example, you can no longer do the following actions:
103
+
Some features available in earlier versions of App Service Environment aren't available in App Service Environment v3. For example, you can no longer do the following actions:
104
104
105
105
- Perform a backup and restore operation on a storage account behind a firewall.
106
106
107
-
- Access the FTPS endpoint by using a custom domain suffix.
107
+
- Access the File Transfer Protocol Secure (FTPS) endpoint by using a custom domain suffix.
108
108
109
109
## Pricing
110
110
111
-
With App Service Environment v3, the pricing model varies depending on the type of App Service Environment deployment that you have. There are three pricing models:
111
+
The App Service Environment v3pricing model varies depending on the deployment type:
112
112
113
-
-**App Service Environment v3:** If the App Service Environment is empty, there's a charge as though you have one instance of Windows I1v2. The one instance charge isn't an additive charge but is applied only if the App Service Environment is empty.
113
+
-**App Service Environment v3:** If the environment is empty, you're charged as if you have one instance of Windows I1v2. This charge applies only when no instances are deployed.
114
114
115
115
-**Zone redundant App Service Environment v3:** There's no added charge for availability zone support. The pricing model is the same as an App Service Environment that isn't zone redundant.
116
116
117
-
-**Dedicated host App Service Environment v3:**With a dedicated host deployment, you pay for two dedicated hosts at the time of App Service Environment v3 creation, based on our pricing. As you scale, you're charged a specialized Isolated v2 rate for each vCore. I1v2 uses two vCores, I2v2 uses four vCores, and I3v2 uses eight vCores for each instance.
117
+
-**Dedicated host App Service Environment v3:**You pay for two dedicated hosts at the time of App Service Environment v3 creation, based on current pricing. As you scale, you're charged a specialized Isolated v2 rate for each vCore. For each instance, I1v2 uses two vCores, I2v2 uses four vCores, and I3v2 uses eight vCores.
118
118
119
-
Reserved Instance pricing for Isolated v2 is available and is described in [How reservation discounts apply to Azure App Service](../../cost-management-billing/reservations/reservation-discount-app-service.md). App Service and Reserved Instance pricing is available at [App Service pricing](https://azure.microsoft.com/pricing/details/app-service/windows/) under the Isolated v2 plan.
119
+
You can also use [reserved instance pricing for Isolated v2](../../cost-management-billing/reservations/reservation-discount-app-service.md). For more information, see [App Service pricing](https://azure.microsoft.com/pricing/details/app-service/windows/).
120
120
121
121
## Regions
122
122
123
-
App Service Environment v3 is available in the following regions:
123
+
App Service Environment v3 is available in the following regions.
124
124
125
-
### Azure Public
125
+
### Azure public regions
126
126
127
127
| Region | Regional deployment support | Availability zone support |
0 commit comments