Virtual Machines
-
Support Windows 10 with Azure Accelerated Networking. Please!
Currently Windows 2012 and 2016 support Azure Accelerated Networking. Can you please add Windows 10 to the list. As more and more virtual desktops are deployed to Azure this is coming an increased important.
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
Automatically generalize VM's upon image creation
In the Azure Gov online portal, if you create an image from a VM it will enter a fail state because it is an unprepared image. Microsoft will direct you to these docs for creating a generalized VM: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/upload-generalized-managed. All of this should be done during image creation, and new VM's created from those images should work out of the box
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
Add ability to set VM resolution on creation
VM resolution by default is 1024 x 768
We use the VM's to run automation on a desktop application which requires a larger resolution to appear correctly.
Please add the ability to set a default resolution on creation.
Appreciate there are still limits on a VM resolution but should allow the freedom we need upto the limits.
We currently use a workaround with RDPwrap but this is far from ideal and does not work in all circumstances.
Providing the requested feature would eliminate a huge pain point and provide a much needed improvement to our user experience.
5 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
Add option to control VM agent log placement and rotation
Currently all the agents that can be deployed onto an Azure Windows VM log into two hardwired folders: C:\WindowsAzure and C:\Packages\Plugins.
Also, much (all?) of the actual agent binaries are also placed in these files, including any newer versions.
Unfortunately neither the logs, nor the older defunct binaries are removed. Using 30+ Windows VMs for around a year, with Diagnostic Agents, Backup Agents, DSC lcm, and others. Neither of these clean up any of their "litters" generated during their operation.
This means, the above folders (especially WIndowsAzure) continues to grow indefinitely. Currently these are on around 3-5GB of size for…
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
Have Azure Update Manager update itself for installations on premises.
We've had vm's drop from inventory and were notified that the Azure Update Manager installed on premises needed to be manually updated. It would be great if the agent could reach out and check for new updates and update itself automatically.
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
Show VM shutdown timestamp on portal
Customer always need to query vm shotdown timestamp. It would be convenient for users to view the time on portal directly.
4 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
Basic_A0 size should not list out when create Windows 2016 server from Azure portal
The least RAM required for Windows 2016 server deployment is 512MB to boot. while Basic_A0 size VM has only 768MB Memory size. This size is not suitable for Windows 2016 server deployment in Azure. Since it will require more than 768 MB to login and operate normal things.
Can you please move the Basic_A0 size out of the VM size list when we are creating Windows 2016 servers? this can avoid some issue.
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sizes-previous-gen
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
You really gotta fix those machines.. If Paperspace has AIR machine with graphics card, 4 GB RAM, 2cores processor, hardware
Thanks, dear.. You really gotta fix those machines.. If Paperspace has AIR machine with graphics card, 4 GB RAM, 2cores processor, hardware encoding, for 18$ flat price.. AZURE should have 4 high performance processors for 3$, + 4 GB RAM + 3$, + Storage usage + 0.10 cent per GB :)
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
Azure don't give any warning and providing size which will not work for the image we select
Azure don't give any warning and providing size which will not work for the image we select:
You can provision a windows Server 2016 with Basic_A0. But the size is below requirement and you won't be able to login and make that server work.
Most of the time server will go in the failed state.
I recommend, if azure can give some kind of warning of totally don't provide the size. when the selected size don't meet the minimum requirement for the selected server.
Regarding the Case - 119052422002805
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
Automatic snapshot before Windows Update installation (IaaS)
Sometimes Windows Update problems can cause major issues with Azure VMs, therefore is it possible to create functionality where the OS can notify Azure before it installs updates, and then at this point Azure can take an automatic snapshot?
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
1 vote
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
Support osDisk swap for encrypted VMs
Today Azure provides a way to swap the osDisk of the VM only when the VM's osDisk is not encrypted.
https://docs.microsoft.com/en-us/azure/security/azure-security-disk-encryption-overviewShould be able to support this even when the VM is encrypted using Azure Disk Encryption.
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
remote desktop
Facilitate using remote desktop on new VMs.
This serial console is junk.1 voteThanks for the suggestion. Your feedback is now open for the user community to up-vote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
-
Swapping the unhealthy physical node at starting VM
For running VM, "Service healing" will prevents down-time.
On the other hands, for initiation of VM, user have to wait for VM fully starts and user cannot detect the reason why VM starts slowly.I would propose that Azure automatically retry starting VM on another node in case Azure detect unhealthy node events.
1 votevalid suggestion subject to customer upvote
-
Support for Teams & SFB on Windows Virtual Desktop
With the release of Windows Virtual desktops on Azure, the multisession W10 offering does not support either of the Collaboration Tools, SFB or Teams. The support of these office apps with pass through support for peripherals is vital to make this offering viable. Please can this be looked at and delivered when the service goes public on Azure
https://docs.microsoft.com/en-us/azure/virtual-desktop/set-up-customize-master-image
11 votesValid suggestion subject to upvote
-
Protected settings available in Clear text in Deployment options
When I use ARM template and Custom Script Extensions with protected settings, these options are available in clear text in Deployment option.
Can you fix it?
1 vote -
Allow RG / Subscription move for VM in Availability Zones
Actually is not possibile to move Managed Disks and IP Addresses for VM located in Availability Zones
1 vote -
Add "VM JIT Requestor" role to Resource/RG level role list
Quite often, I want to grant users login access to an Azure VM without giving them contributor access to modify the metadata associated with the VM itself. However, while Reader access gives users access to the Azure portal, and Virtual Machine User Login access allows users to login to the VM once in the portal, neither the aforementioned roles nor any other predefined role provides the ability to request JIT access to the VM.
My workaround has been to create a cusotm role with the following allowed action: Microsoft.Security/locations/jitNetworkAccessPolicies/initiate/action
However, this seems like an action that should either be allowed…
2 votes -
Successfully perform Windows Updates on General Purpose VM's
When creating a Standard A1 v2 virtual machine in Azure, Windows Updates do not perform correctly. Azure Support have advised that the Virtual Machine needs to be increased in size, but i would expect all virtual machines offered in the Azure Portal to be able to perform Windows Updates...
1 vote -
If user configured a domain controller and user forget the account & password.
If user configured a domain controller and user forget the account & password. user can not get VM's data anytime. user can not reset account & password, too.
1 vote
- Don't see your idea?