Skip to content

Commit a9498c9

Browse files
committed
edit
1 parent 939b520 commit a9498c9

File tree

1 file changed

+8
-10
lines changed

1 file changed

+8
-10
lines changed

articles/reliability/reliability-bastion.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -38,22 +38,20 @@ If transient faults affect your virtual machine or Azure Bastion host, clients u
3838

3939
Azure Bastion supports availability zones in both zonal and zone-redundant configurations:
4040

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-
4441
- *Zonal:* You can select a single availability zone for an Azure Bastion resource.
4542

4643
> [!NOTE]
4744
> 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.
4845
4946
- *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.
5755
5856
### Regions supported
5957

0 commit comments

Comments
 (0)