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/overview.md
+91-4Lines changed: 91 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ A benefit of using an App Service Environment instead of a multitenant service i
69
69
App Service Environment v3 differs from earlier versions in the following ways:
70
70
71
71
- 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.
72
-
- You can deploy an App Service Environment v3 that's enabled for zone redundancy. You set zone redundancy only during creation and only in regions where all App Service Environment v3 dependencies are zone redundant. In this case, each App Service Plan on the App Service Environment will need to have a minimum of three instances so that they can be spread across zones. For more information, see [Migrate App Service Environment to availability zone support](../../availability-zones/migrate-app-service-environment.md).
72
+
- You can deploy an App Service Environment v3 that's enabled for zone redundancy. You set zone redundancy only during creation and only in regions where all App Service Environment v3 dependencies are zone redundant. This is a deployment time only decision. Changing zone redundancy is not possible after it has been deployed. With zone redundant App Service Environment, each App Service Plan on the App Service Environment will need to have a minimum of three instances so that they can be spread across zones. For more information, see [Migrate App Service Environment to availability zone support](../../availability-zones/migrate-app-service-environment.md).
73
73
- You can deploy an App Service Environment v3 on a dedicated host group. Host group deployments aren't zone redundant.
74
74
- Scaling is much faster than with an App Service Environment v2. Although scaling still isn't immediate, as in the multitenant service, it's a lot faster.
75
75
- 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.
@@ -165,6 +165,7 @@ App Service Environment v3 is available in the following regions:
165
165
| Southeast Asia | ✅ | ✅ |
166
166
| Spain Central | ✅ | ✅**|
167
167
| Sweden Central | ✅ | ✅ |
168
+
| Sweden South | ✅ ||
168
169
| Switzerland North | ✅ | ✅ |
169
170
| Switzerland West | ✅ ||
170
171
| UAE Central | ✅ ||
@@ -188,23 +189,109 @@ App Service Environment v3 is available in the following regions:
188
189
| US DoD Central | ✅ ||
189
190
| US DoD East | ✅ ||
190
191
| US Gov Arizona | ✅ ||
191
-
| US Gov Iowa |||
192
192
| US Gov Texas | ✅ ||
193
193
| US Gov Virginia | ✅ |✅ |
194
194
195
195
### Microsoft Azure operated by 21Vianet
196
196
197
197
| Region | Single zone support | Availability zone support |
|| App Service Environment v3| App Service Environment v3|
200
200
| China East 3 | ✅ ||
201
-
| China North 2 |||
202
201
| China North 3 | ✅ | ✅ |
203
202
204
203
### In-region data residency
205
204
206
205
An App Service Environment will only store customer data including app content, settings and secrets within the region where it's deployed. All data is guaranteed to remain in the region. For more information, see [Data residency in Azure](https://azure.microsoft.com/explore/global-infrastructure/data-residency/#overview).
207
206
207
+
## Pricing tiers
208
+
209
+
The following sections list the regional pricing tiers (SKUs) availability for App Service Environment v3.
210
+
211
+
> [!NOTE]
212
+
> Windows Container plans currently do not support memory intensive SKUs.
0 commit comments