Skip to content

Commit 2b9b349

Browse files
committed
Match template
1 parent 7bf3c08 commit 2b9b349

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/reliability/reliability-bastion.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,9 @@ ms.date: 10/22/2024
1111

1212
# Reliability in Azure Bastion
1313

14-
This article describes reliability support in Azure Bastion and covers both intra-regional resiliency with [availability zones](#availability-zone-support) and information on [multi-region deployments](#multi-region-support). Because resiliency is a shared responsibility between you and Microsoft, this article also covers ways for you to build a resilient solution that meets your needs.
14+
This article describes reliability support in Azure Bastion and covers both intra-regional resiliency with [availability zones](#availability-zone-support) and information on [multi-region deployments](#multi-region-support).
15+
16+
Because resiliency is a shared responsibility between you and Microsoft, this article also covers ways for you to build a resilient solution that meets your needs.
1517

1618
> [!IMPORTANT]
1719
> Zone redundancy features for Azure Bastion resources are currently in PREVIEW.
@@ -85,7 +87,7 @@ When you initiate an SSH or RDP session, it can be routed to an Azure Bastion in
8587

8688
It's possible that 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, while the virtual machine is in zone 1:
8789

88-
:::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 virtual machine in zone 1." border="false":::
90+
:::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 virtual machine in zone 1." border="false":::
8991

9092
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. However, this configuration doesn't provide zone redundancy, and we don't recommend it for most customers.
9193

0 commit comments

Comments
 (0)