Virtual Machines
-
Accelerate VM startup time
Startup time of a Windows VM in AWS is 1-1.5 minutes. In Azure this takes at least 5 minutes. VM Startup time is a big deal!
181 votesstarted ·
AdminAzure IaaS Engineering Team
(Azure IaaS Engineering Team, Microsoft, Microsoft Azure)
responded
Startup times for VMs continues to be a focus in Azure. I am leaving this item in the “Started” state because we still have work to be done, but the current deployment time we are seeing for Windows Server on average is 2 minutes (1 minute for Linux). We’ll continue to invest resources in driving down this number.
-
Azure's status board availability
The Microsoft Azure status board should live outside Azure's ecosystem just because when there is a problem with some Azure´s service, the Microsoft Azure status page may not be available for the same issue.
29 votes -
Support adding NICs in the portal
Please support an option to add extra NICs directly to virtual machines from the Azure Portal
12 votesQuick update on supporting adding NICs in the Azure portal. We’re in final testing for this feature, and hoping to make it available soon.
Stay tuned!
-
Need to update existing Azure Classic or ARM VM's WinServer licenseType property.
Need to update existing Azure Classic or ARM VM's WinServer licenseType property. Because users / customers created VM earlier than get Win SA/Hybrid Use Benefit message or purchase Win Server with SA after the VMs already created in Azure. At least can update from NULL to specfic value in licenseType property.
Thanks
7 votesYou can now modify license type in VMs via the portal for platform create images. Updating license type for custom images is coming soon.
-
Update Disk count in VM Selection to match documented maximums
Available Data Disk is showing incorrect number during VM creation size selection versus documented data disk availabilities.
5 votesThanks. We’ve done some work to make these consistent now, and to make sure everything stays in sync going forward.
-
Improve availability and speed.
This is electronic suicide to be on this platform. I do not know from where you obtain your availability numbers, but when users cannot access their VMs using remote desktop it is very bad! Please look at my support incidents for an example and feel free to contact me any time for in-person feedback.
In addition to availability; when a new VM is created, I notice that it isn't immediately available. It takes several minutes before I can access it.
Also speed needs to be improved. Remote Desktop speed, change in which settings are propagated.
2 votesI will reach out and chat more!! Thanks for the note.
Corey
-
Improve Load Balancing Wizard
I find the process for creating a load balanced endpoint in the new azure portal to be completely counter intuitive. It's unfortunate because it's a big sore spot on an otherwise smooth experience.
My problem is that creating a load balanced endpoint doesn't behave at all the way I would expect it to. In the case where I have multiple machines and I'm setting up a load balanced endpoint for the first time why can't I just create a load balanced endpoint from the wizard without having a pre-existing endpoint?
Also why can't I edit an existing single-machine endpoint…
2 votesThis is an area we are hoping to improve soon. Stay tuned.
-
Kazumi HIROSE
Subscription japanese name.
Subscription directory filter has Garbage chars.
Please see attach file.1 voteWe will get this bug fixed.
- Don't see your idea?