Skip to content

Commit 9b11244

Browse files
committed
Updates
1 parent 19abbb5 commit 9b11244

1 file changed

Lines changed: 5 additions & 3 deletions

File tree

articles/reliability/reliability-bastion.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,10 +26,12 @@ Azure Bastion is a fully managed platform as a service (PaaS) that you provision
2626
For production deployments, you should [enable zone redundancy](#availability-zone-support) if your bastion hosts are in a supported region.
2727

2828
## Reliability architecture overview
29-
<!-- TODO -->
3029

31-
- Bastion host
32-
- Instance
30+
When you use Azure Bastion, you deploy a *bastion host*. You must deploy it to a subnet that [meets Azure Bastion's requirements](/azure/bastion/configuration-settings#subnet).
31+
32+
A bastion host has a defined number of *instances*, which are also sometimes called *scale units*. The Standard SKU supports *host scaling*, where you configure the number of instances. Adding more instances helps to accommodate additional concurrent client connections. The Basic SKU supports exactly two instances.
33+
34+
Each instance represents a dedicated VM that handles traffic. One instance is equal to one VM. You don't see or manage the VMs directly. The platform automatically manages instance creation, health monitoring, and replacement of unhealthy instances.
3335

3436
## Transient faults
3537

0 commit comments

Comments
 (0)