In your previous generations of D class VMs you had the DS3_v2, With 4vCPUs, 14GB of RAM and 4 NICs. In all subsequent generations the 4vCPU VMs only support 2 NICs. Why? I have vendor appliances that require 3 NICs. They don't require massive amounts of compute and memory so why is it that on the current generation we are forced to buy huge machines just to get the same NIC count as older generations. The equivalent AWS m4.xlarge supports 4 NICs and for Google Cloud any instance can support up to 8vNICs

NEW INNOVATION FOR NEW LOOK PROGRAM

"az cli" (and the backing service) should be able to display the pricePerHour of a vm size.
e.g.

$ az vm list-sizes --location northeurope --query "[?contains(name,'StandardNC6Promo') == `true`].{name: name, osDiskSizeInMb: osDiskSizeInMb, pricePerHour: pricePerHour}"
[
{

"name": "Standard_NC6_Promo",

"osDiskSizeInMb": 1047552,

"pricePerHour": null       <----

}
]

With the Single Placement Group enabled, there will be a decrease in capacity within the cluster and an Allocation Failure will occur sometimes.
To avoid this, please add a configuration that only considers deploying from another cluster when the cluster is out of capacity.

From PowerShell GitHub repo: https://github.com/Azure/azure-powershell/issues/11989.

It will be nice that New-AzVM supports creating VM basing on an existing VM within on cmdlet.

Support create VM from unattached disk in Portal

Why it's only supported with script?
https://docs.microsoft.com/en-us/azure/virtual-machines/scripts/virtual-machines-windows-powershell-sample-create-vm-from-managed-os-disks

We encountered a driver mismatch issue with the preinstalled CUDA drivers on N-series VMs (cuDNN 7.0 vs. CUDA 9.0). And upgrading to newer versions took some time due to confusing N-series driver setup documentation that led us down the wrong path.

Drivers in VM image should be updated (to cuDNN 7.4 and CUDA 10.0) and docs should be updated to provide better guidance for setting up drivers.

Documentation: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/n-series-driver-setup

Only one custom script can be attached to Ubuntu VMSS Agent Pool, need the ability to add more than one custom script to Ubuntu VMSS.

www.myhelmetsguide.com

Please provide easy way to change virtual disk name.
The current alternative is deattache the disk, clone the disk with name name, then attach new disk by PowerShell. But the performance is very low. 4GB disk took more than 6 minutes.

i have windows 10 running on VM with username - XX2020Az

I forgot the password of it, then when i want to change password through reset password on virtual machine resources...

i type username-XX2020A and reset the password.. once login found there are two users are there with admin privelieges XX2020Az & XX2020A

then i realize that there is issues on VM Password reset.. Password reset is working in both the ways 1-Reset the password, 2- Creating new users.. I think there is some coding issues... kindly check it

i have windows 10 running on VM with username - XX2020Az

I forgot the password of it, then when i want to change password through reset password on virtual machine resources...

i type username-XX2020A and reset the password.. once login found there are two users are there with admin privelieges XX2020Az & XX2020A

then i realize that there is issues on VM Password reset.. Password reset is working in both the ways 1-Reset the password, 2- Creating new users.. I think there is some coding issues... kindly check it

We have our solution to deploy as Linux VM in Azure with our customized virtual disk. It has user name 'admin'. As this 'admin' string is reserved, I'm not able to provide ssh-key during vm creation. So good to allow user choiced names. Also let me know currently if there is a way to provide string like 'admin' , 'root' as user names.

This is with a newly created Win10 VM. I tried to use the Run command to enable the user account and troubleshoot with PowerShell, but Run does not appear to be responding either. Can't SSH into it. Thanks.

Redeployment is painful. Customers have a tendency to deploy PAYG during POC phase and then want to switch to a BYOS model to take advantage of cost savings later. Switching Linux VMs from PAYG to BYOS in Azure requires a disruptive VM redeployment to a different image. AHB for Linux would remove the need for the redeployment.

Reproduce steps:
1. Deploy a fresh NV4asv4 instance
2. Download 20.Q1.1 driver from Azure documentation page.
3. RDP to the instance.
4. Run AMD driver installer.
5. Reboot machine.
6. RDP to the instance
Result: AMD driver is not running. Logs and screenshot are attached in AMDissue.zip file

Make the .net 3.5 binaries available on Server 2019 by default.

It's a real pain spinning up a virtual machine in Azure and then having get hold of a 2019 ISO just to get .NET 3.5 installed.
There are still a lot of Microsoft things that require .NET 3.5 so just include it and save us all a lot of hassle in our configurations.

MSIT Windows 10 imaged machine with locked down permission/group policy is unable to install Docker and switch to Linux containers. It throws Hyper-V unable to connect to the computer error.

Is this on the upcoming road map for Azure Government? I have a customer where this would help with requirements.