Skip to content

Commit be7ecb7

Browse files
committed
Acrolinx
1 parent 87cce0e commit be7ecb7

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

articles/reliability/reliability-bastion.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ There's no additional cost to use availability zone support for Azure Bastion. C
9393

9494
[!INCLUDE [Availability zone numbering](./includes/reliability-availability-zone-numbering-include.md)]
9595

96-
- **Existing bastion hosts:** It's not possible to change the availability zone configuration of an existing bastion host. Instead, you need to create an bastion host with the new configuration and delete the old one.
96+
- **Existing bastion hosts:** It's not possible to change the availability zone configuration of an existing bastion host. Instead, you need to create a bastion host with the new configuration and delete the old one.
9797

9898
### Normal operations
9999

@@ -107,7 +107,7 @@ This section describes what to expect when bastion hosts are configured for avai
107107
:::image type="content" source="./media/reliability-bastion/bastion-instance-zone-traffic.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":::
108108

109109
> [!TIP]
110-
> In most scenarios, the amount of cross-zone latency isn't significant. However, if you have unusually stringent latency requirements your workloads, you should deploy a dedicated single-zone Azure Bastion instance in the virtual machine's availability zone. Keep in mind that this configuration doesn't provide zone redundancy, and we don't recommend it for most customers.
110+
> In most scenarios, the amount of cross-zone latency isn't significant. However, if you have unusually stringent latency requirements for your workloads, you should deploy a dedicated single-zone Azure Bastion instance in the virtual machine's availability zone. Keep in mind that this configuration doesn't provide zone redundancy, and we don't recommend it for most customers.
111111
112112
- **Data replication between zones:** Because Azure Bastion doesn't store state, there's no data to replicate between zones.
113113

@@ -119,7 +119,7 @@ This section describes what to expect when bastion hosts are configured for avai
119119

120120
For zone-redundant instances, Azure Bastion makes a best-effort attempt to replace any instances that are lost due to a zone outage. However, it isn't guaranteed that instances will be replaced.
121121

122-
- **Notification**: Azure Bastion doesn't notify you when a zone is down. However, you can use [Azure Resource Health](/azure/service-health/resource-health-overview) to monitor for the health of your basion host. You can also use [Azure Service Health](/azure/service-health/overview) to understand the overall health of the Azure Bastion service, including any zone failures.
122+
- **Notification**: Azure Bastion doesn't notify you when a zone is down. However, you can use [Azure Resource Health](/azure/service-health/resource-health-overview) to monitor for the health of your bastion host. You can also use [Azure Service Health](/azure/service-health/overview) to understand the overall health of the Azure Bastion service, including any zone failures.
123123

124124
Set up alerts on these services to receive notifications of zone-level problems. For more information, see [Create Service Health alerts in the Azure portal](/azure/service-health/alerts-activity-log-service-notifications-portal) and [Create and configure Resource Health alerts](/azure/service-health/resource-health-alert-arm-template-guide).
125125

0 commit comments

Comments
 (0)