Introduction
This article describes how to scale Azure Bastion to support more concurrent SSH and RDP sessions, outlines the impact of scaling, and clarifies the reasons manual intervention by support might be necessary. It also covers practical steps for scaling via the Azure portal, notes on session limits by SKU, and important considerations regarding cost and connection disruptions.
The maximum number of concurrent sessions varies depending on what each user is doing and the number of Bastion instances. For example, for "medium" workload each instance can support 20 concurrent RDP and 40 concurrent SSH sessions. For Azure Bastion Basic SKU, you are limited to 2 instances, whereas with Standard SKU you can have up to 50 instances.
If each user is performing tasks that involve lots of data transfer then less sessions per Bastion instance will be supported.
How to Scale:
- Log in to Azure Portal
- Go to Subscriptions > ANDREA-Shared-Demo-0001 (Tenant)

- Resource groups > rg-demo-bastion

- rg-demo-bastion

- Sessions Here you can see how many sessions are running all at the same time.

- Configuration
Here is where you can scale.

Changing the Instance count involves costs per extra instance per hour!
Why does support need to manually scale?
The number of Azure Bastion units can be set via power-shell, however:
"Any changes to the host scale units will disrupt active bastion connections." source Microsoft Docs.
Here you can learn more about Instances and host scaling and Azure Bastion limits
Add Link to - Instances and host scaling - https://learn.microsoft.com/en-us/azure/bastion/configuration-settings#instance Azure Bastion limits - https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-bastion-limits