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/reliability/includes/reliability-availability-zone-description-include.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,11 @@
4
4
author: anaharris-ms
5
5
ms.service: azure
6
6
ms.topic: include
7
-
ms.date: 06/21/2022
7
+
ms.date: 11/12/2024
8
8
ms.author: anaharris
9
9
ms.custom: include file
10
10
---
11
11
12
-
Azure availability zones are at least three physically separate groups of datacenters within each Azure region. Datacenters within each zone are equipped with independent power, cooling, and networking infrastructure. In the case of a local zone failure, availability zones are designed so that if the one zone is affected, regional services, capacity, and high availability are supported by the remaining two zones.
12
+
Availability zones are physically separate groups of datacenters within each Azure region. When one zone fails, services can fail over to one of the remaining zones.
13
13
14
-
Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Tolerance to failures is achieved with redundancy and logical isolation of Azure services. For more detailed information on availability zones in Azure, see [Regions and availability zones](/azure/reliability/availability-zones-overview).
15
-
16
-
Azure availability zones-enabled services are designed to provide the right level of reliability and flexibility. They can be configured in two ways. They can be either zone redundant, with automatic replication across zones, or zonal, with instances pinned to a specific zone. You can also combine these approaches. For more information on zonal vs. zone-redundant architecture, see [Recommendations for using availability zones and regions](/azure/well-architected/resiliency/regions-availability-zones).
14
+
For more information on availability zones in Azure, see [What are availability zones?](/azure/reliability/availability-zones-overview).
Transient faults are short, intermittent failures in components. They occur frequently in a distributed environment like the cloud, and they're a normal part of operations. They correct themselves after a short period of time. It's important that your applications handle transient faults, usually by retrying affected requests.
13
+
14
+
All cloud-hosted applications should follow Azure's transient fault handling guidance when communicating with any cloud-hosted APIs, databases, and other components. To learn more about handling transient faults, see [Recommendations for handing transient faults](/azure/well-architected/reliability/handle-transient-faults).
Copy file name to clipboardExpand all lines: articles/reliability/reliability-app-service.md
+16-11Lines changed: 16 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
---
2
2
title: Reliability in Azure App Service
3
-
description: Find out about reliability in Azure App Service, including availability zones and multi-region deployments.
3
+
description: Find out about reliability in Azure App Service, including availability zones and multi-region deployments.
4
4
author: anaharris-ms
5
5
ms.author: anaharris
6
6
ms.topic: reliability-article
7
7
ms.custom: subject-reliability
8
8
ms.service: azure-app-service
9
-
ms.date: 11/08/2024
9
+
ms.date: 11/12/2024
10
10
zone_pivot_groups: app-service-sku
11
11
---
12
12
@@ -39,9 +39,7 @@ For production deployments, you should:
39
39
40
40
## Transient faults
41
41
42
-
Transient faults are short, intermittent failures in components. They occur frequently in a distributed environment like the cloud, and they're a normal part of operations. They correct themselves after a short period of time. It's important that your applications handle transient faults, usually by retrying affected requests.
43
-
44
-
All cloud-hosted applications should follow Azure's transient fault handling guidance when communicating with any cloud-hosted APIs, databases, and other components. To learn more about handling transient faults, see [Recommendations for handing transient faults](/azure/well-architected/reliability/handle-transient-faults).
Although Microsoft-provided SDKs usually handle transient faults, because you host your own applications on Azure App Service, you need to consider how to avoid causing transient faults by making sure that you:
47
45
@@ -53,6 +51,8 @@ Although Microsoft-provided SDKs usually handle transient faults, because you ho
53
51
54
52
## Availability zone support
55
53
54
+
[!INCLUDE [AZ support description](includes/reliability-availability-zone-description-include.md)]
55
+
56
56
Azure App Service can be configured as *zone redundant*, which means that your resources are spread across multiple [availability zones](../reliability/availability-zones-overview.md). Spreading across multiple zones helps your production workloads achieve resiliency and reliability. <!-- Not sure what this means --> Availability zone support is a property of the App Service plan.
57
57
58
58
Instance spreading with a zone-redundant deployment is determined inside the following rules, even as the app scales in and out:
@@ -65,7 +65,7 @@ When the App Service platform allocates instances for a zone-redundant App Servi
65
65
66
66
For App Service plans that aren't configured as zone redundant, VM instances are not resilient to availability zone failures. They can experience downtime during an outage in any zone in that region.
67
67
68
-
### Requirements
68
+
### Regions supported
69
69
70
70
::: zone pivot="free-shared-basic"
71
71
@@ -83,21 +83,26 @@ You must use either the [Premium v2 or Premium v3 plan types](/azure/app-service
83
83
84
84
- You must deploy a minimum of three instances of your plan.
85
85
86
-
### Regions supported
86
+
87
+
To see which regions support availability zones for App Service Environment v3, see [Regions](../app-service/environment/overview.md#regions).
88
+
89
+
::: zone-end
90
+
91
+
### Requirements
87
92
88
93
::: zone-end
89
94
90
95
::: zone pivot="premium"
91
96
92
-
Zone-redundant App Service plans can be deployed in [any region that supports availability zones](./availability-zones-service-support.md#azure-regions-with-availability-zone-support).
97
+
- You must use either the [Premium v2 or Premium v3 plan types](/azure/app-service/overview-hosting-plans).
98
+
<!-- Is footprint a technical term here?-->
99
+
- Availability zones are only supported on the newer App Service footprint. Even if you're using one of the supported regions, you'll receive an error if availability zones aren't supported for your resource group. To ensure your workloads land on a stamp that supports availability zones, you may need to create a new resource group, App Service plan, and App Service.
93
100
94
101
::: zone-end
95
102
96
-
::: zone pivot="isolated"
103
+
- You must deploy a minimum of three instances of your plan.
97
104
98
-
To see which regions support availability zones for App Service Environment v3, see [Regions](../app-service/environment/overview.md#regions).
@@ -27,12 +27,14 @@ For production deployments, you should [enable zone redundancy](#availability-zo
27
27
28
28
## Transient faults
29
29
30
-
*Transient faults* are short intermittent failures in components. They occur frequently in a distributed environment like the cloud, and they're a normal part of operations. They correct themselves after a short period of time. It's important that your applications handle transient faults, usually by retrying affected requests.
If transient faults affect your virtual machine or Azure Bastion host, clients using the secure sockets host (SSH) and Remote Desktop Protocol (RDP) protocols typically retry automatically.
33
33
34
34
## Availability zone support
35
35
36
+
[!INCLUDE [AZ support description](includes/reliability-availability-zone-description-include.md)]
37
+
36
38
You can configure Azure Bastion to be *zone redundant* so that your resources are spread across multiple [availability zones](../reliability/availability-zones-overview.md). When you spread resources across availability zones, you can achieve resiliency and reliability for your production workloads.
37
39
38
40
You can specify which availability zone or zones an Azure Bastion resource should be deployed to. Azure Bastion spreads your instances across those zones. The following diagram shows Azure Bastion instances spread across three zones:
@@ -42,12 +44,6 @@ You can specify which availability zone or zones an Azure Bastion resource shoul
42
44
> [!NOTE]
43
45
> If you specify more availability zones than you have instances, Azure Bastion spreads instances across as many zones as it can. If an availability zone is unavailable, the instance in the faulty zone is replaced with another instance in a healthy zone.
44
46
45
-
### Requirements
46
-
47
-
To configure Azure Bastion resources with zone redundancy, you must deploy with the Basic, Standard, or Premium SKUs.
48
-
49
-
Bastion requires a Standard SKU zone-redundant Public IP.
50
-
51
47
### Regions supported
52
48
53
49
Zone-redundant Azure Bastion resources can be deployed into the following regions:
@@ -62,6 +58,15 @@ Zone-redundant Azure Bastion resources can be deployed into the following region
62
58
| East US 2 EUAP | Italy North |||
63
59
| Mexico Central| Spain Central |||
64
60
61
+
62
+
### Requirements
63
+
64
+
To configure Azure Bastion resources with zone redundancy, you must deploy with the Basic, Standard, or Premium SKUs.
65
+
66
+
Bastion requires a Standard SKU zone-redundant Public IP.
67
+
68
+
69
+
65
70
### Cost
66
71
67
72
There's no additional cost to use zone redundancy for Azure Bastion.
@@ -18,12 +18,13 @@ Because resiliency is a shared responsibility between you and Microsoft, this ar
18
18
19
19
## Transient faults
20
20
21
-
Transient faults are short, intermittent failures in components. They occur frequently in a distributed environment like the cloud, and they're a normal part of operations. They correct themselves after a short period of time.
22
-
It's important that your applications handle transient faults, usually by retrying affected requests.
[!INCLUDE [AZ support description](includes/reliability-availability-zone-description-include.md)]
27
+
27
28
Azure Device Registry is zone-redundant, which means that it automatically replicates across multiple [availability zones](../reliability/availability-zones-overview.md). This setup enhances the resiliency of the service by providing high availability. If there's a failure in one zone, the service can continue to operate seamlessly from another zone.
28
29
29
30
Microsoft manages setup and configuration for zone redundancy in Azure Device Registry. You don't need to perform any more configuration to enable this zone redundancy. Microsoft ensures that the service is configured to provide the highest level of availability and reliability.
@@ -52,7 +53,7 @@ There's no extra cost to use zone redundancy for Azure Device Registry.
52
53
53
54
### Zone-down experience
54
55
55
-
During a zone-wide outage, you don't need to take any action to failover to a healthy zone. The service automatically self-heals and rebalances itself to take advantage of the healthy zone automatically.
56
+
During a zone-wide outage, you don't need to take any action to fail over to a healthy zone. The service automatically self-heals and rebalances itself to take advantage of the healthy zone automatically.
56
57
57
58
**Detection and response:** Because Azure Device Registry detects and responds automatically to failures in an availability zone, you don't need to do anything to initiate an availability zone failover.
0 commit comments