Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Virtual Machines

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Rubenzandbergen025@Outlook.com

    Wisselen van persoonlijk naar bedrijf

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow raising DSv4 quota via the portal

    Since at least the 11th, I have been unable to raise DSv4 quotas the normal way in the portal, because they're missing from the list. Each time I have to try my luck via various support channels to get a staff member to raise my core quota. It takes a long time, and burns a lot of time at Microsoft and with me. I have an open production incident right now, in fact, open for a number of hours, because I am unable to raise the DSv4 quota in the semi-automated manner.

    Cross referencing case numbers:

    120102221002436
    120102221002010
    120101121000118
    https://twitter.com/danfarina/status/1319410593598615552

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  3. The New-AzVM cmdlet no longer works

    The page is: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/quick-create-powershell

    This command, copied directly from the toturial and run in the Azure Cloud Shell: New-AzVm `

    -ResourceGroupName "myResourceGroup" `
    
    -Name "myVM" `
    -Location "East US" `
    -VirtualNetworkName "myVnet" `
    -SubnetName "mySubnet" `
    -SecurityGroupName "myNetworkSecurityGroup" `
    -PublicIpAddressName "myPublicIpAddress" `
    -OpenPorts 80,3389

    Generates the following error:

    New-AzVM: The property 'securityProfile.encryptionAtHost' is not valid because the 'Microsoft.Compute/EncryptionAtHost' feature is not enabled for this subscription

    Please help!

    I've run this same command before, and never got this error. It is happening on all of my subscriptions.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  4. Source image for adding images to shared image gallery must be uniquely identified across different resource groups

    Source image for adding images to shared image gallery must be uniquely identified across different resource groups

    There are two images with same name in different resource groups and therefore I am unable to identify the source image that I want to be included in shared image gallery. See screen shot. One way out of this mess was trial and error. Customer was not appreciative of this mechanism.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  5. Password Reset also working as new user creations

    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

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  6. Standard NV4as_v4 instance: AMD driver is not running after installing 20.Q1.1 driver

    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 AMD
    issue.zip file

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  7. Daylight Savings not considered in VM

    I live in UK.
    I created a VM, deployed in West US (of course because Azure UK/Europe is facing overloading), so when I logged into VM the time is showing 1 hour behind. I believe the Daylight saving after March 29th is not considered.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  8. Update-AzVmss throws error : Azure PowerShell deployment To deploy the extension on a virtual machine scale set

    while i ran this command in windows powershell admin mode
    $vmss = Get-AzVmss -ResourceGroupName <ResourceGroupName> -VMScaleSetName <VmssName>

    Update-AzVmss -ResourceGroupName <ResourceGroupName> -VMScaleSetName <VmssName> -VirtualMachineScaleSet $vmss

    By passing <VmssName> and <ResourceGroupName> got below exception PS C:\windows\system32> Update-AzVmss -ResourceGroupName "gave my fabric clusters resource group name" -VMScaleSetName "ExpInt" -VirtualMachineScaleSet $vmss
    Update-AzVmss : Long running operation failed with status 'Failed'. Additional Info:'VM has reported a failure when processing extension 'KeyVaultForWindows'. Error message: "Failed to parse
    the configuration settings with: 'not an object'"
    More information on troubleshooting is available at https://aka.ms/vmextensionwindowstroubleshoot '
    ErrorCode: VMExtensionProvisioningError
    ErrorMessage: VM has reported a failure when processing extension 'KeyVaultForWindows'. ErrorMessage:…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  9. CSE executed before cloud-init

    Hello,

    I have an ARM template with VM + CSE script to be executed.
    I've provided a cloud-init config through customData parameter.

    My cloud-init looks as follows:
    $ cloud-config
    package_upgrade: true
    package_update: true
    packages:
    - libssl-dev
    - libffi-dev
    - python-dev
    runcmd:
    - curl -sL <a rel="nofollow noreferrer" href="https://aka.ms/InstallAzureCLIDeb">https://aka.ms/InstallAzureCLIDeb</a> | sudo bash
    - az aks install-cli

    Within the CSE script, I'm trying to run az login command, but I keep getting an error az: command not found.

    When I ssh into VM, I can see az working just fine.

    Actual behavior

    I've looked through logs, and this is what I…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  10. Inconsistent case conversions

    There is a lot of case conversion inconsistency and it appears to be growing. For example:

    Resource group names are converted to uppercase when creating disk resources.

    When creating DNS and RSV resources, the resource names and resource groups names are converted and stored in lowercase.

    Consistency throughout should be maintained. We are wasting significant hours in development and testing implementing workarounds due to case inconsistency in the Azure back-end.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    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 backlog and also gives us insight into the potential impact of implementing the suggested feature.

  11. Add word "Local" to the reserved words list for username when creating Windows VMs in Azure

    When creating VMs, if you use the username "local" and choose a password the user account 'local' does not get created on the OS. Instead, the Administrator account gets enabled and the password you attempted to set for a user called "local" is set on the Administrator account.

    This caused confusion during RDP to the OS, as the expected username to use was "local" - however, the account does not exist on the OS.

    A potential fix would be to block the use of "local" as a username, similarly to how the username "Administrator" is reserved from use.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    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

  12. "Windows Server 2016 Datacenter - with Containers" Hangs on Extracting "microsoft/windowsservercore" layer

    I run docker images from azure pipeline on virtual machine remotely. I have image that usese "microsoft/windowsservercore" image as base.
    I am using "Windows Server 2016 Datacenter - with Containers" on "StandardA2v2"/"StandardA4v2" size machines with "Standard SSD". Last two weeks everything was working fine. But starting from 18.02.2019 virtual machine docker run command hangs on extracting "microsoft/windowsservercore" second layer and instead of like previously run for 7-11 minutes it runs for 35, when i run command manually over RDP or from azure pipeline. I have recreated virtual machines 3 times and process still hangs. On local…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  13. Close the security hole allowing outbound traffic to any server on the internet on TCP port 1688 from any Azure IaaS VM

    NSG 'deny' rules ignore TCP port 1688.

    It is possible to exflitrate [i.e. steal] confidential data from any Azure IaaS VM (via the internet) to a server running an arbitrary service on TCP port 1688.

    Example:
    1. Deploy an SSH/SFTP server running on port 1688 in your home or another cloud service
    2. As a legitimate user of an Azure IaaS deployment, logon to an Azure VM (RDP or Citrix servers commonly allow user-logons)
    3. Transfer confidential data from the Azure IaaS VM to your private server on port 1688

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  14. The final step gives an error.

    When I try to access http://publicIPAdress/wordpress it shows "Error establishing a database connection".

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  15. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  16. Request to add PhysicalDisk counters in enable guest-level monitoring, Metric Auto collection improvement required

    I will request you to please add below like PhysicalDisk counters in MS service improvement because these are basic and important performance counters to differentiate PhysicalDisks Performance.

    As well as it can set automatically when we enable guest-level monitoring like logical disk counters and Network, Memory Counters.

    \PhysicalDisk(0 C:)\Disk Transfers/sec => IOPS
    \PhysicalDisk(0 C:)\Avg. Disk sec/Transfer => Disk Latency
    \PhysicalDisk(0 C:)\Disk Bytes/sec => Throughput

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  17. EnableRemotePS Run Command Fails on Windows 10 VMs

    The script of EnableRemotePS Run Command:
    Enable-PSRemoting -Force
    New-NetFirewallRule -Name "Allow WinRM HTTPS" -DisplayName "WinRM HTTPS" -Enabled True -Profile Any -Action Allow -Direction Inbound -LocalPort 5986 -Protocol TCP
    $thumbprint = (New-SelfSignedCertificate -DnsName $env:COMPUTERNAME -CertStoreLocation Cert:\LocalMachine\My).Thumbprint
    $command = "winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname=""$env:computername""; CertificateThumbprint=""$thumbprint""}"
    cmd.exe /C $command

    It on Windows 10 VMs with the following error from RunCommandExtensionn.Log file :

    [3504+00000001] [12/05/2018 08:52:29.69] [ERROR] Command execution finished. Command exited with code: 1

    When executing the first command (Enable-PSRemoting -Force) manually on the VM, we get the following error:

    Set-WSManQuickConfig : <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault&quot; Code="2150859113" Machine="localhost"><f:Message><f:ProviderFault provider="Config provider"
    path="%systemroot%\system32\WsmSvc.dll"><f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault&quot;…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  18. Azure CustomScriptExtensions for SKU Win7-SP1-Ent-N-x64 stopped working

    All I see in the logs is "Current sequence number, 0, is not greater than the sequence number of the most recently executed configuration. Exiting...". Basically we use a setup very similar to https://github.com/Azure/azure-quickstart-templates/blob/master/201-vm-custom-script-windows/azuredeploy.json but with a custom script url and the win7 sku. And it worked fine for a long time. But now things have stopped working without any obvious change from our end (we even reverted everything and it still doesn't work anymore).

    I tried to workaround by using different CustomScriptExtension versions, but nothing helped. The deployment succeeds when connecting via RDP and running disable, reset and …

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  19. Azure CustomScriptExtensions for SKU Win7-SP1-Ent-N-x64 stopped working

    All I see in the logs is "Current sequence number, 0, is not greater than the sequence number of the most recently executed configuration. Exiting...". Basically we use a setup very similar to https://github.com/Azure/azure-quickstart-templates/blob/master/201-vm-custom-script-windows/azuredeploy.json but with a custom script url and the win7 sku. And it worked fine for a long time. But now things have stopped working without any obvious change from our end (we even reverted everything and it still doesn't work anymore).

    I tried to workaround by using different CustomScriptExtension versions, but nothing helped. The deployment succeeds when connecting via RDP and running disable, reset and …

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  20. Unable to remove the base image in Microsoft Azure

    Sometimes when we are trying to remove base image of VMSS, it will prompt out this error, while there is no any further information to guide us on how to properly delete the image. It would be great if azure can provide more information regarding to this problem

    Virtual Machine ScaleSet '/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups//providers/Microsoft.Compute/virtualMachineScaleSets/

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Virtual Machines

Categories

Feedback and Knowledge Base