Can an Azure Bastion be created per virtual network?

An Azure Bastion can indeed be created for each virtual network, enabling secure, seamless RDP and SSH connectivity to virtual machines located within that network. This service provides a more secure way of connecting to VMs without exposing them to the public internet, thus enhancing the security posture of your Azure architecture.

When you deploy Azure Bastion, it is tied to a specific virtual network and allows access to all VMs within that network. This design helps in simplifying the management and improving the security of remote connectivity to your resources. Each virtual network can have its own Bastion deployment, allowing for flexible and isolated access management tailored to the needs of different projects or environments.

Other options such as limitations based on subscription type, or dependencies on the number of VMs, do not reflect the architecture of Azure Bastion, which is allocated per virtual network rather than being bound by usage or plan.