Skip to content

Commit b659199

Browse files
committed
edit
1 parent 8527dd4 commit b659199

File tree

3 files changed

+107
-1
lines changed

3 files changed

+107
-1
lines changed
Lines changed: 103 additions & 0 deletions
Loading
Binary file not shown.

articles/reliability/reliability-bastion.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,10 @@ You can configure Azure Bastion to be *zone redundant* so that your resources ar
3737

3838
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:
3939

40+
<!-- Art Library Source# ConceptArt-0-000-015- -->
4041
:::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":::
4142

43+
4244
> [!NOTE]
4345
> 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.
4446
@@ -83,7 +85,8 @@ When you initiate an SSH or RDP session, it can be routed to an Azure Bastion in
8385

8486
A session might be sent to an Azure Bastion instance in an availability zone that's different from the virtual machine you're connecting to. In the following diagram, a request from the user is sent to an Azure Bastion instance in zone 2, although the virtual machine is in zone 1:
8587

86-
:::image type="content" source="./media/reliability-bastion/bastion-cross-zone.png" alt-text="Diagram that shows Azure Bastion with three instances. A user request goes to an Azure Bastion instance in zone 2 and is sent to a VM in zone 1." border="false":::
88+
<!-- Art Library Source# ConceptArt-0-000-015- -->
89+
:::image type="content" source="./media/reliability-bastion/bastion-cross-zone.svg" alt-text="Diagram that shows Azure Bastion with three instances. A user request goes to an Azure Bastion instance in zone 2 and is sent to a VM in zone 1." border="false":::
8790

8891
In most scenarios, the small amount of cross-zone latency isn't significant. However, if you have unusually stringent latency requirements for your Azure Bastion workloads, you should deploy a dedicated single-zone Azure Bastion instance in the virtual machine's availability zone. This configuration doesn't provide zone redundancy, and we don't recommend it for most customers.
8992

0 commit comments

Comments
 (0)