Share via

Unable to create Developer SKU Bastion

Douglas Windom 25 Reputation points
2026-04-16T20:53:06.0766667+00:00

Initially I was having issues connecting to a virtual machine that I had already setup with a developer Bastion. That consistently returned "Internal server error while requesting session." As part of the troubleshooting, I decided to delete the Bastion and start over. Unfortunately, no matter which region I select, I cannot choose the Developer SKU.

I've reviewed the docs and tried all the US regions listed at https://learn.microsoft.com/en-us/azure/bastion/bastion-sku-comparison. I've attempted to deploy via Azure PowerShell and that results in an error "New-AzBastion: Cannot validate argument on parameter 'Sku'. The argument "Developer" does not belong to the set "Basic,Standard,Premium" specified by the ValidateSet attribute." I've even tried creating one on another subscription that is setup for enterprise billing with no luck.

Is the Developer Bastion still available?

Azure Bastion
Azure Bastion

An Azure service that provides private and fully managed Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to virtual machines.

Answer accepted by question author

  1. Q&A Assist
    2026-04-16T20:53:20.94+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Developer SKU Bastion is still available, but it is created and managed differently from the Basic/Standard/Premium SKUs, which is why the attempts with PowerShell and the regular Bastion create flow are failing.

    Key points based on current behavior and documentation:

    1. Developer SKU is not created via New-AzBastion or az network bastion create.
      • PowerShell only accepts Basic, Standard, or Premium for -Sku, as shown by the validation error.
      • Developer uses a shared pool architecture and is not a dedicated Bastion host resource like the other SKUs.
    2. Developer SKU is deployed automatically from the VM’s VNet blade in the portal:
      • Go to the virtual network that contains the VM.
      • In the left pane, select Connect > Bastion.
      • Choose the authentication type, enter credentials, and select Connect.
      • When Connect is selected, Bastion Developer is automatically deployed to the virtual network (in supported regions) using the shared pool model; there is no explicit SKU dropdown for “Developer” in the standard Bastion create experience.
    3. Region and prerequisites still apply:
      • The VM must be in a region that supports Bastion Developer.
      • A VNet and VM must already exist, and required roles/ports must be in place.
    4. Upgrading from Developer to a dedicated SKU requires creating a new Bastion host:
      • To move from Developer to Basic/Standard/Premium, delete the Developer instance and create a new Bastion host with the desired SKU (Basic/Standard/Premium) using CLI/PowerShell or the portal.

    So Developer Bastion is available, but only via the “inline” Bastion connect experience on the VNet/VM (shared pool), not via the standard Bastion resource creation commands or SKU parameter.

    References:

    Was this answer helpful?

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. TP 156.6K Reputation points Volunteer Moderator
    2026-04-16T21:42:49.2566667+00:00

    Hi Douglas,

    Yes, Developer SKU Bastion is still available in limited set of regions.

    You can tell if it is available by navigating to Bastion blade and then on right if it says "Creating new Bastion Developer SKU:" it will automatically create Developer SKU Bastion when you click on Connect button. Please see screenshot below:

    User's image

    Please click Accept Answer and upvote if the above was helpful.

    Thanks.

    -TP

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.