I think the tool is pretty good. It is like having a tool that just works. If there are better tools that Azure comes up with, then that is a separate thing. In the current scenario, Azure Bastion is not a bad product. In my company, we are not facing any challenges or limitations with the tool. Speaking of AI, having Microsoft Copilot in Azure Bastion would be good. As of now, Microsoft Copilot is not something that has been considered for Azure Bastion. It would be a good addition if it is done in the future.
Implementation-wise, a little bit of improvement is required because the tips they have provided are a little bit tricky. There are some challenges because Bastion is more compatible with Edge but not with the other browsers. As an organization, it doesn't make sense that we have to use only Edge. We should be able to access Bastion over Chrome, Mozilla, or Opera. It should be our choice. A little bit of improvement is required for Linux because we can add Bastion on the Windows machine, but PuTTY is implemented for Linux. We have to log in to Bastion, and through that, we have to go to the PuTTY service.
Senior Microsoft System Engineer at a tech vendor with 201-500 employees
Real User
2022-01-05T08:16:06Z
Jan 5, 2022
It's like an RDP gateway. It will let you access the virtual machines and have a full RDP experience. It's not full, however, for example, you cannot copy content inside, due to the RDP not being on the browser. It's HTML-based, where you cannot copy, for example, the full RDP experience to copy data from your computer to the server. That is the only limitation on the Azure Bastion. If we can copy content and drag and drop it on the HTML, this would be helpful. There's something called UDR on Azure. We cannot apply, as, when you deploy Azure Bastion, the networking part of the Azure Bastion, it needs a separate subnet for it. When you create the Azure Bastion, you need the subnet, like a network range for this subnet. The issue with that is you cannot manage this subnet on a way to control the traffic and to route the traffic from Azure Bastion, for example, to your firewall. Each virtual network should have its own subnet. This is maybe the problem. It's the networking part and applying the routing table on it that is where the issue lies. If they can make the Azure console, or the VM console, available on the Azure Bastion, so when you reboot the VM, you can still see what's happening during the reboot, maybe it will be better. You could even troubleshoot issues if you have boot issues on the virtual machine, which is not available in Azure Bastion, as Azure Bastion will just give you access when the VM restarts and when you have the login page of Windows. However, when the VM restarts, you will not have this visibility on what's happening on the reboot, and we face many issues in the boot. When you have a boot issue on Windows, you cannot use Azure Bastion to fix it. You have to use the Azure console or the VM console, and it is very limited. To make Bastion the best product as a management tool or an RDP tool, it will be better to bring the features of the hypervisor, local hypervisor, Hyper-V console, to Azure Bastion.
Managing Director at Evenor Info Solutions Pvt Ltd
Real User
Top 10
2021-11-15T07:22:00Z
Nov 15, 2021
This is a cloud-based solution. When we are dumping data into the cloud, it's free of cost. When we retrieve that data from the cloud, they require some amount of money. That is the main drawback of this cloud solution. You are charged for retrieving your own data.
Azure Bastion is a service you deploy that lets you connect to a virtual machine using your browser and the Azure portal. The Azure Bastion service is a fully platform-managed PaaS service that you provision inside your virtual network. It provides secure and seamless RDP/SSH connectivity to your virtual machines directly from the Azure portal over TLS. When you connect via Azure Bastion, your virtual machines do not need a public IP address, agent, or special client software.
I think the tool is pretty good. It is like having a tool that just works. If there are better tools that Azure comes up with, then that is a separate thing. In the current scenario, Azure Bastion is not a bad product. In my company, we are not facing any challenges or limitations with the tool. Speaking of AI, having Microsoft Copilot in Azure Bastion would be good. As of now, Microsoft Copilot is not something that has been considered for Azure Bastion. It would be a good addition if it is done in the future.
We are not able to copy and paste files directly into the server over the patch host. We have to transfer files over to Azure Storage.
The solution breaks down sometimes.
The protocol speed could be faster.
Implementation-wise, a little bit of improvement is required because the tips they have provided are a little bit tricky. There are some challenges because Bastion is more compatible with Edge but not with the other browsers. As an organization, it doesn't make sense that we have to use only Edge. We should be able to access Bastion over Chrome, Mozilla, or Opera. It should be our choice. A little bit of improvement is required for Linux because we can add Bastion on the Windows machine, but PuTTY is implemented for Linux. We have to log in to Bastion, and through that, we have to go to the PuTTY service.
It's like an RDP gateway. It will let you access the virtual machines and have a full RDP experience. It's not full, however, for example, you cannot copy content inside, due to the RDP not being on the browser. It's HTML-based, where you cannot copy, for example, the full RDP experience to copy data from your computer to the server. That is the only limitation on the Azure Bastion. If we can copy content and drag and drop it on the HTML, this would be helpful. There's something called UDR on Azure. We cannot apply, as, when you deploy Azure Bastion, the networking part of the Azure Bastion, it needs a separate subnet for it. When you create the Azure Bastion, you need the subnet, like a network range for this subnet. The issue with that is you cannot manage this subnet on a way to control the traffic and to route the traffic from Azure Bastion, for example, to your firewall. Each virtual network should have its own subnet. This is maybe the problem. It's the networking part and applying the routing table on it that is where the issue lies. If they can make the Azure console, or the VM console, available on the Azure Bastion, so when you reboot the VM, you can still see what's happening during the reboot, maybe it will be better. You could even troubleshoot issues if you have boot issues on the virtual machine, which is not available in Azure Bastion, as Azure Bastion will just give you access when the VM restarts and when you have the login page of Windows. However, when the VM restarts, you will not have this visibility on what's happening on the reboot, and we face many issues in the boot. When you have a boot issue on Windows, you cannot use Azure Bastion to fix it. You have to use the Azure console or the VM console, and it is very limited. To make Bastion the best product as a management tool or an RDP tool, it will be better to bring the features of the hypervisor, local hypervisor, Hyper-V console, to Azure Bastion.
This is a cloud-based solution. When we are dumping data into the cloud, it's free of cost. When we retrieve that data from the cloud, they require some amount of money. That is the main drawback of this cloud solution. You are charged for retrieving your own data.