Azure – You can now configure your own DNS on Azure Firewall and use DNS proxy (preview)
As you know, Azure Firewall is a cloud as a service (FWaaS) from Azure helping you to centrally managed traffic from Azure or to Azure.
1 min read
As you may know, Microsoft has released a solution allowing you to remotely connect with RDP or SSH to your virtual machines running on Azure without being obliged to have a public IP (and corresponding ports opened) called Azure Bastion (see https://t.co/UBOCpnMD2k)
Well, until know, if you had multiple Vnets, you had to deploy Bastion for each Vnets – even if they are peered with each other.
Good news, you can now use Azure Bastion to connect any virtual machine no matter to which Vnet they are connected to.
You have nothing to enable or implement – except off course 1 Azure Bastion instance and have the Vnet peered.
Few things:
- You can still deploy other Azure Bastion instance on the other Vnet; the VM you want to connect to will detect if a Bastion instance is running for the Vnet or not. If there is an instance for the Vnet, it will use this instance, otherwise it will use the Bastion instance from the other Vnet
- You can connect on virtual machine running on different subscription (as soon as the Vnet is peer with the virtual network where Bastion is deployed off course)
