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/availability-zones-service-support.md
+3-14Lines changed: 3 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,24 +16,15 @@ Azure [availability zones](./availability-zones-overview.md) are physically sepa
16
16
17
17
Azure is continually expanding the number of services that support availability zones, including zonal and zone-redundant offerings.
18
18
19
-
## Always-available services
20
-
21
-
Some Azure services don't support availability zones because they are:
22
-
23
-
- Available across multiple Azure regions within a geographic area, or even across all Azure regions globally.
24
-
- Resilient to zone-wide outages.
25
-
- Resilient to region-wide outages.
26
-
For more information on older-generation virtual machines, see [Previous generations of virtual machine sizes](/azure/virtual-machines/sizes-previous-gen).
27
-
28
19
## Azure services with availability zone support
29
20
30
-
The following tables provide a summary of the current offering of zonal and zone-redundant Azure services.
21
+
The following tables provide a summary of the current offering of zonal and zone-redundant Azure services. To learn more about zonal and zone-redudant services and how they work, see [Types of availability zone support](./availability-zones-overview.md#types-of-availability-zone-support).
31
22
32
23
Some Azure services are *nonregional*, which means that you don't deploy the service into a specific Azure region or configure availability zone support. To learn more, see [Nonregional Azure services](./regions-nonregional-services.md).
33
24
34
25
##### Legend
35
26
36
-
<!-- TODO redo as table, and remove always available -->
27
+

37
28
38
29
> [!IMPORTANT]
39
30
> Even though some services might support availability zones, they might have specific requirements to use them on your resources. For example, some may only support availability zones for certain tiers or regions. To get more information on a service's requirements for availability zone support, select that service in the following table.
@@ -97,8 +88,6 @@ Some Azure services are *nonregional*, which means that you don't deploy the ser
97
88
|[Azure VMware Solution](../azure-vmware/architecture-private-clouds.md)||
98
89
|[SQL Server on Azure Virtual Machines](/azure/azure-sql/database/high-availability-sla)||
99
90
100
-
\*VMs that support availability zones: AV2-series, B-series, DSv2-series, DSv3-series, Dv2-series, Dv3-series, ESv3-series, Ev3-series, F-series, FS-series, FSv2-series, and M-series.\*
101
-
102
91
### Containers
103
92
104
93
|**Product**|**Availability zone support**|
@@ -130,7 +119,7 @@ Some Azure services are *nonregional*, which means that you don't deploy the ser
130
119
131
120
|**Product**|**Availability zone support**|
132
121
| --- | --- |
133
-
|[Azure API Center](../api-center/overview.md)||
122
+
|[Azure API Center](../api-center/overview.md)||
134
123
|[Azure App Configuration](../azure-app-configuration/faq.yml#how-does-app-configuration-ensure-high-data-availability)||
135
124
|[Azure Monitor](/azure/azure-monitor/logs/availability-zones)||
136
125
|[Azure Monitor: Application Insights](/azure/azure-monitor/logs/availability-zones)||
0 commit comments