Virtual Machines
-
On AWS, the user can control CoreCount of EC2(VMs). I hope that Microsoft Azure provide more flexible options to control vCPUs for VM Size.
On AWS, the user can control CoreCount of EC2(VMs). I hope that Microsoft Azure provide more flexible options to control vCPUs for VM Size.
Specifying CPU Options for Your Instance
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-optimize-cpu.html
To disable multithreading during instance launch (AWS CLI)Use the run-instances AWS CLI command and specify a value of 1 for ThreadsPerCore for the --cpu-options parameter. For CoreCount, specify the number of CPU cores. In this example, to specify the default CPU core count for an r4.4xlarge instance, specify a value of 8.
aws ec2 run-instances --image-id ami-1a2b3c4d --instance-type r4.4xlarge --cpu-options "CoreCount=8,ThreadsPerCore=1" --key-name MyKeyPair2 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 backlog and also gives us insight into the potential impact of implementing the suggested feature.
-
Disable Server Manager on startup
Please configure Windows Server images on Azure not to load Server Manager on startup (as EC2 does). This is a slow loading and resource consuming app that's mostly unnecessary for Azure VMs, and it's slowing down connecting to the machine via RDP.
3 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 backlog and also gives us insight into the potential impact of implementing the suggested feature.
-
show size of VM images and which VM sizes they fit in
I went through a hot or miss effort to find a VM size that would not present the warning "The selected image is too large for the OS cache of the selected instance". It would be helpful to see the size of the images when selecting and a filter option when selecting VM sizes for the chosen image that fit into OS cache.
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
-
Allow Multiple disk attach/detach to VM simultaneously.
Right now API virtual_machines.create_or_update is single threaded can we make it multi threaded or can we throttle request coming to server at server end by keeping semaphore or any another approach which is suitable to design . Currently it shows error like GenericError: Changing property 'dataDisk.managedDisk.id' is not allowed which so generic and naive it should have some kind of intelligence at back end .
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
-
Build feature for offline patching of VMs and VHDs
It would be great to have the ability to patch virtual machines and VHDs offline, this would enhance security and tremendously ease management of VHDs in a shared image gallery!
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
-
An easy way to copy VM
Hope there's an easy way in Azure portal for VM copy, for example: A Copy Button. When I click the button, it will create a new VM same configration as the original one.
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
-
Get notify on non-impacting update for some business/mission critical Azure VMs
Some servers is network sensitive can't afford few seconds of network outage caused by Azure non-impacting update.
The 2 Azure NetApp HA instances in our environment suffer unexpected reboot every time non-impacting update happens and also lead to other third-party replication services failed and halted.
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
-
RI Recomendations
As of now, Recommendations are not available based on the instance size flexibility, can we have this feature enabled?
3 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
-
A feature to deny the internet access from Azure Virtual machine and also wanted to manually upgrade the window patching
A feature to deny the internet access from Azure Virtual machine and also wanted to manually upgrade the window patching
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
-
VMSS scaleset /VM creation validation is successful the images that were not generalized.
Customer's are feeling mislead when the validation shows successful although they are using images captured from ungeneralized VM's. if there is possibilty to validate if the OS is good or corrupted it would be great.
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
-
Fix the recently broken time entry field for automation schedules, VM auto-shutodown
The Azure portal used to accept times in the format like 1200 or 1700, etc. After a recent change, the format is very rigid and must now be like "5:00:00 PM". Any deviation from that erase user input and reverts. Very annoying, and caused errors for us.
Example locations for time entry are VM auto-shutdown and Automation schedules.
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
-
Windows Virtual Desktop - User Assigned Personnel Desktop
In WVD enable the feature to assign a user to a personnel Session Host in PowerShell and the WVD Web UX
This will allow users to pre-assign users to their own VDI host in Azure that can be pre-staged with the apps that user will need, giving more flexibility to the WVD Service.
6 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
-
Allocation failed. We do not have sufficient capacity for the requested VM size in this region
When is this problem going to be fixed? This article https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/allocation-failure was written in early 18 so it's clearly been forgot about.
We were told to move to ARM from Classic as this problem was mitigated but if anything it's worse. In the entire West Europe region, we can only provision 19 d14_v2s at any given time!
1 vote -
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.
6 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
- Don't see your idea?