Enable browser-based connection to the student VMs, instead of RDP/SSH
Marc-Andre Moreau commented
Is it possible to expose ports other than the non-standard RDP and SSH ports in the custom range? If it were just possible to expose a new port for a web server, I guess one DIY solution would be to deploy Apache Guacamole (https://guacamole.apache.org/) inside the Lab VM and use it for browser-based access.
For lab Services VMs you're looking at one public IP per lab but a huge port range for RDP (49152-65535). No admin will ever drill that many holes in their firewall.
That makes Lab Service VMs unusable for most commercial users behind a firewall..
This feature is now planned for 1.5 years - any release date available?
I'm assuming this will be the same as Azure Bastion for DevTest Labs?
I guess the nice thing about RDP files is that you can potentially get multi-monitor support and clipboard sharing just the same as using an on prem server RDP connection.
But https in a browser as an option would also be great, not everywhere will allow outbound port 3389 to the internet.
Sean Murthy commented
I welcome browser-based connections for any lab user because it eliminates the need to frequently download the RDP file.
I'm not really sure why the RDP file becomes unusable after a while: the only reason could be the domain/port changes (but why?). It is particularly painful because users customize RDP properties and they will need to redo that each time the RDP file changes.