> To use Microsoft Dev Box, each user must be licensed for Windows 11 Enterprise or Windows 10 Enterprise, Microsoft Endpoint Manager, and Azure Active Directory P1.
uh-huh. I suspect that's why the $138.20/month max charge is suspicious, as I bet that's just the VM cost. I'm not currently incentivized to use the "request quote" button to find out the real cost
The target audience is people who have to do everything in Azure to make infosec compliance less painful. I can't imagine a reason an individual dev (or most small companies) would use it.
Well their Windows 365 Virtual Desktops certainly do and they are running Windows 11 Enterprise. I'm sure these will too. Why would they leave any possible revenue source untapped?
I'm a huge believer in remote / cloud development, but this is not something I'll consider using. Here's why: with my current setup, VSCode + Remote SSH and development VMs on a proxmox bare metal box, I have a native IDE experience and don't experience any latency, even though I'm in Asia, and the box is in Germany (Hetzner). If I used an RDP connection, all of sudden this puts a higher demand on my internet connection, while as the VS code remote / code-server solution is quite tolerant of latency spikes / disconnections.
The only downside is that I have to re-do my client-side VScode configuration if I start working from a new desktop. Things like keybindings and preferences are synced to github. Or I could go the cloud route and use my hosted code-server instances, which works quite well.
6 comments
[ 0.26 ms ] story [ 23.1 ms ] thread> To use Microsoft Dev Box, each user must be licensed for Windows 11 Enterprise or Windows 10 Enterprise, Microsoft Endpoint Manager, and Azure Active Directory P1.
uh-huh. I suspect that's why the $138.20/month max charge is suspicious, as I bet that's just the VM cost. I'm not currently incentivized to use the "request quote" button to find out the real cost
https://learn.microsoft.com/en-us/azure/dev-box/tutorial-con... doubles-down on the fact they're just Windows instances over RDP, so I am 100% not the target audience for this
The only downside is that I have to re-do my client-side VScode configuration if I start working from a new desktop. Things like keybindings and preferences are synced to github. Or I could go the cloud route and use my hosted code-server instances, which works quite well.