![]() ![]() I created a video session for the Azure Advent Calender about Azure Bastion. The function is on the roadmap and will come, but I thought it would be available with GA release. That is a challenge from cost and management perspective. Today you have to enroll a Azure Bastion in each VNET in that you will arrive your VMs via the Bastion service. One of the important missed feature is support of VNET Peering. There are some features that I missed in Azure Bastion today. This makes the service more useful and avoid complexity for your infrastructure. Since mid of December 2020 Azure Bastion supports VNET peering. Some really missed feature since GA was support for VNET peering. Re-regestration is done within minutes, there is no need for leave unused Bastion host available. If you do not need Azure Bastion, delete the service to avoid costs. Please note: Azure Bastion price is based on an hourly basis. Microsoft guarantess an SLA for Azure Bastion of 99,95%. The price is for all regions the same.Īzure Bastion 0,081€ per Hour x 730 hours = 59,13€ The costs are ok, but I missed essential functions like the support of VNET-Peering. The cost of the service are not increased after the GA was announced. For this there is a feature request added at. This is not possible by design in the moment. ![]() Right now it is not possible to use Just-in-Time access (JIT) and Azure Bastion on the same Azure VMs together.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |