Azure Bastion SKUs explained

Azure Bastion comes in four tiers — Developer, Basic, Standard, Premium — and the feature you most often need (using your own RDP/SSH client) only arrives at Standard. Here's the full matrix from Microsoft's documentation, and how to choose.

1. Feature comparison

FeatureDeveloperBasicStandardPremium
Requires AzureBastionSubnetNoYesYesYes
Requires public IPNoYesYesNo (private-only option)
Dedicated hostNo (shared)YesYesYes
Connect to VMs in the same VNetYesYesYesYes
Connect to VMs in peered VNetsNoYesYesYes
Concurrent connectionsNo (1 VM at a time)YesYesYes
RDP to Windows / SSH to LinuxYesYesYesYes
RDP to Linux / SSH to WindowsNoNoYesYes
Kerberos authenticationYesYesYesYes
Linux private keys from Key Vault (portal)YesYesYesYes
Portal-based connectionsYesYesYesYes
Native client (Azure CLI)NoNoYesYes
Custom inbound portNoNoYesYes
IP-based connection (IP-Connect)NoNoYesYes
Shareable linkNoNoYesYes
Upload/download files (native client)NoNoYesYes
Disable copy/paste (web client)NoNoYesYes
Host scaling (2–50 instances)NoNoYesYes
Session recordingNoNoNoYes
Private-only deploymentNoNoNoYes
Hourly chargeFreePaidPaidPaid
Outbound data transferFreePaid (first 5 GB/month free)Paid (first 5 GB free)Paid (first 5 GB free)

2. Capacity

DeveloperBasicStandardPremium
DeploymentShared resourceDedicatedDedicatedDedicated
InstancesN/A2 (fixed)2–502–50
Per-instance capacity20 RDP + 40 SSH20 RDP + 40 SSH20 RDP + 40 SSH
Max concurrent RDP sessions1401,000 (at 50 instances)1,000
Max concurrent SSH sessions1802,0002,000

3. Which one?

  • Developer — dev/test only. Free, deploys in seconds, no AzureBastionSubnet, but one VM at a time, no peering, portal only, and only in select regions. Microsoft warns it "isn't suitable for production workloads".
  • Basic — production with modest needs: dedicated two-instance host, peering, Kerberos, but portal connections only.
  • Standard — the tier most teams want. Native client (az network bastion rdp/ssh/ tunnel), custom ports, IP-based connection, shareable links, file transfer, host scaling to 50 instances.
  • Premium — Standard plus session recording (portal sessions; not available for native client) and private-only deployment with no public IP. Microsoft's own tip: "The cost difference between Standard and Premium is marginal. Premium SKU is the recommended choice for production deployments."

4. Upgrades and downgrades

  • Upgrading to a higher SKU is supported through the portal and takes about 10 minutes; you can enable features (native client, etc.) during the upgrade.
  • Developer → dedicated requires creating an AzureBastionSubnet (/26+) and a Standard static public IP first.
  • Downgrading isn't supported — you delete and redeploy.

5. Pricing model

Hourly per SKU from the moment of deployment, whether or not anyone connects. Standard and Premium base pricing includes two instances; additional instances are billed per hour. Outbound data transfer is tiered, with the first 5 GB per month free. Figures are region-dependent — see the pricing page.

Common questions

Is the Developer SKU really free?

Yes — no hourly charge and no data-transfer charge. The trade-offs are one VM at a time, no VNet peering, portal-only connections and limited regions.

Do I need Premium for compliance?

Only if you need session recording (graphical recordings of portal RDP/SSH sessions stored in your storage account) or a private-only Bastion with no public IP. Otherwise Standard covers the same connectivity features.

Can I scale Basic?

No — Basic is fixed at two instances (40 RDP / 80 SSH sessions). Host scaling starts at Standard.

Sources