Bastion Emulator

Preview

During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in

Bastion Emulator

Available on Starter Standard Team Compare plans →

Azure Bastion lets you connect to a Virtual Machine over SSH or Remote Desktop, without it needing a public IP.

Locally supports both provisioning Bastion Hosts and connecting through them to your Virtual Machines, using locally connect - so you can check a Virtual Machine is reachable the way you expect.

What you connect to is the Virtual Machines Emulator's view of the Virtual Machine, rather than a shell - so you can check how it's set up, what its extensions did and what can reach it.

For a step-by-step walkthrough, see Provisioning an Azure Bastion.

Plugins required

Locally v2026.10+ automatically installs these Resource Provider plugins when their Resource Providers are registered, but you can also install them via:

$ locally plugin install --name Microsoft.Compute
$ locally plugin install --name Microsoft.Network

Finding the Emulator

Once a Bastion Host has been created, its resource page within the Locally Dashboard has a How to connect section, with the locally connect command ready to copy:

Screenshot of a Bastion Host in the Locally Dashboard, showing the How to connect section with the locally connect command

The Bastion Emulator

Running locally connect --bastion <name> lists the Virtual Machines you can reach through it (or, in an interactive terminal, asks you to pick one) - and adding --virtual-machine <name> connects to it:

Screenshot of a terminal session opened through a Bastion in Locally, showing the Virtual Machine's details and the available views

The session shows which Bastion it came through, alongside the Virtual Machine's details - see the Virtual Machines Emulator.

What's Supported

The Bastion emulator supports:

Basic, Standard & Developer SKUs SSH (Linux) Remote Desktop (Windows) Private-IP-Only Virtual Machines On-Demand Tunnels

Virtual Machines don't need a public IP - Locally checks each one has a network interface in the Bastion's Virtual Network (or, for a Developer SKU, the Virtual Network it's linked to), then opens a tunnel to it for the session.

Connecting uses the Virtual Machine's own credentials - its admin SSH key or password on Linux, or its password on Windows.

Differences from Azure

As of Locally v2026.11.03, the Bastion emulator has the following differences from Azure:

  • Connecting gives you a view of the Virtual Machine rather than a shell. To run something inside it, use an extension or a Run Command.
  • There's no in-browser session, and az network bastion ssh, rdp and tunnel aren't supported - use locally connect instead. Shareable links can be created, but don't open anything.
  • Only Virtual Machines in the Bastion's own Virtual Network can be reached - not ones in peered Virtual Networks.
  • Scale Set instances can't be reached through a Bastion. Connect to them directly with locally connect --virtual-machine-scale-set.
  • The Bastion's SKU and settings (such as native client support) aren't checked when connecting.

Should you encounter any issues, please take a look at the troubleshooting section, reach out in our Discord or open an issue and we'll take a look.

Preview

During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in

A local cloud for you and your AI agents.

Your Azure infrastructure, running on your machine. Deploy in seconds, break things freely, and ship to Azure when you're ready.