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/reliability-bastion.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,22 +38,20 @@ If transient faults affect your virtual machine or Azure Bastion host, clients u
38
38
39
39
Azure Bastion supports availability zones in both zonal and zone-redundant configurations:
40
40
41
-
<!-- Art Library Source# ConceptArt-0-000-015- -->
42
-
:::image type="content" source="media/bastion/bastion-instances-zones.svg" alt-text="Diagram that shows Azure Bastion with three instances, each in a separate availability zone." border="false":::
43
-
44
41
-*Zonal:* You can select a single availability zone for an Azure Bastion resource.
45
42
46
43
> [!NOTE]
47
44
> Pinning to a single zone doesn’t increase resiliency. To improve resiliency, you need to either use a zone-redundant configuration or explicitly deploy resources into multiple zones.
48
45
49
46
-*Zone-redundant:* Enabling zone redundancy for an Azure Bastion resource spreads your instances 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.
50
-
51
-
The following diagram shows a zone-redundant Azure Bastion resource, with its instances spread across three zones:
52
-
53
-
:::image type="content" source="media/reliability-bastion/bastion-instances-zones.png" alt-text="Diagram that shows a zone-redundant Azure Bastion resource with three instances, each in a separate availability zone." border="false":::
54
-
55
-
> [!NOTE]
56
-
> 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.
47
+
48
+
The following diagram shows a zone-redundant Azure Bastion resource, with its instances spread across three zones:
49
+
50
+
<!-- Art Library Source# ConceptArt-0-000-015- -->
51
+
:::image type="content" source="media/bastion/bastion-instances-zones.svg" alt-text="Diagram that shows Azure Bastion with three instances, each in a separate availability zone." border="false":::
52
+
53
+
> [!NOTE]
54
+
> 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.
0 commit comments