The subnet must have the following configuration: You must create this subnet in the same virtual network that you want to deploy Azure Bastion to. When you deploy Azure Bastion using any SKU except the Developer SKU, Bastion requires a dedicated subnet named AzureBastionSubnet. All Azure Bastion resources deployed in subnets of size /27 prior to this date are unaffected by this change and will continue to work, but we highly recommend increasing the size of any existing AzureBastionSubnet to /26 in case you choose to take advantage of host scaling in the future. The Developer SKU (Preview) is currently available in the following regions:įor Azure Bastion resources deployed on or after November 2, 2021, the minimum AzureBastionSubnet size is /26 or larger (/25, /24, etc.). See Deploy Bastion automatically - Developer SKU for more information and deployment steps. The Developer SKU has different requirements and limitations than the other SKU tiers. You can connect to one Azure VM at a time directly through the Virtual Machine connect page. This SKU is ideal for Dev/Test users who want to securely connect to their VMs and that don't need additional features or scaling.

The Bastion Developer SKU is a new, lower-cost, lightweight SKU. FeatureĬonnect to target VMs in same virtual networkĬonnect to target VMs in peered virtual networksĪccess Linux VM Private Keys in Azure Key Vault (AKV) The following table shows the availability of features per corresponding SKU. You decide the SKU tier based on the features that you want to use. When you configure Bastion, you select the SKU tier.

Azure Bastion supports multiple SKU tiers. The sections in this article discuss the resources and settings for Azure Bastion.

Bastion azure