Thanks for raising your question here.
As you mentioned, when you configure Azure Bastion using the Basic SKU, 2 instances are created. If you use the Standard SKU, you can specify the number of instances between 2-50.
Expand table
Workload Type* | Session Limit per Instance** |
---|---|
Light | 25 |
Light | 25 |
Medium | 20 |
Heavy | 2 |
*These workload types are defined here: Remote Desktop workloads **These limits are based on RDP performance tests for Azure Bastion. The numbers may vary due to other on-going RDP sessions or other on-going SSH sessions.
Now, the issue arises with concurrent sessions to a VM, which cannot exceed 2. This restriction isn't a limitation of Azure Bastion but rather a limitation of RDP itself.
- By default, a server OS will allow 2 user sessions simultaneously and 1 user session on a client OS.
- To have more than 2 sessions on a server OS, you need to install the Remote Desktop Session Host role.
- After installing the Session Host role, you will have a 120-day grace period to procure the licenses, install the Remote Desktop Session Host role, activate the License server, and install Licenses.
You can follow the link below for step-by-step configuration: Install RDS role service without Connection Broker - Windows Server | Microsoft Learn Test Lab Guide: Remote Desktop Licensing | Microsoft Learn