Virtual Machines

How can we improve Azure Virtual Machines?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Improve Portal Message for Availability Set allocation errors

    If there is an allocation error when restarting a deallocated VM, the following error message is logged:
    “Failed to start virtual machine 'xyc'. Error: Allocation failed. Please try reducing the VM size or number of VMs, retry later, or try deploying to a different Availability Set or different Azure location.”

    If there is an allocation issue when creating a new machine the following message is displayed:
    “New-AzureRmVM : Unable to create the VM because the requested size Standard_F4 is not available in the cluster where the availability set is currently allocated. The available sizes are: Standard_DS1_v2,Standard_DS2_v2 …”

    Would be nice…

    11 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  2. Low On Memory Error: Server 2016, B series

    I just spun up a brand new Standard B1ms (1 vcpu, 2 GB memory), all I did was login to the VM and am getting out of memory errors (which would tell me windows server 2016 doesn't really support this level of VM size). Also it fails to retrieve updates - this is just a plain vanilla OOB/first run experience. Additionally you can't login and click the start button - you have to click it about 10 times to get the menu to pop up - this is probably more of a windows issue but I'd expect it to at…

    10 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  3. Report VM Status and PowerState More Accurately

    VM Status and PowerState are not always reported correctly. Often a VM which has been running for hours or days will report Status=RoleStateUnkown or PowerState=Starting (even though it is clearly Started).

    Please work to make this reporting more accurate. Thank you!

    9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  4. storing vmSize with the exactly the same capitalization independently how VM was created

    VmSize is stored with the capitalization how it was called during creation (v2 <> V2).

    VM with v2
    az vm create -n clitest1 -g SAP --image UbuntuLTS --size Standard_D13_v2

    az vm show -g SAP -n clitest1 -d

    "hardwareProfile": {
    "vmSize": "Standard_D13_v2"

    VM with V2
    az vm create -n clitest2 -g SAP --image UbuntuLTS --size Standard_D13_V2

    az vm show -g SAP -n clitest2 -d

    "hardwareProfile": {
    "vmSize": "Standard_D13_V2"

    It causes additional data cleaning necessary during azure data analyzes.
    Please correct
    thanks
    István

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  5. Modify Set-AzureRmVMDiagnosticsExtension cmdlet to improve the ability to automate the install/config of diagnostics exten

    Remove the dependency to have the virtual machine unique ID inside XML configuration file. To automate the install/config of a hundred VMs you would need to customize a hundred XML files. See attached document fo further explanation

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  6. I can not set up automatic backup of SQL Server 2016 on a portal with a language setting other than English

    When deploying the image of SQL Server 2016 with the portal in Japanese language setting and setting automatic backup, the deployment parameter is set to Japanese and an error occurs at the time of expansion.

    If you set the portal language setting to English, the correct parameters are set and you can deploy.

    backupScheduleType : 手動 → Manual
    fullBackupFrequency: 週単位 → Weekly

    Even in languages other than English, I would like you to pass the correct parameters at deployment time.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  7. Improve image gallery replication to other region

    image replication to other region fail or limited to 1

    Code="ReplicationJobsNotCompleted" Message="The replication job has not completed at region: 'eastasia'. You can try to reduce the number of the target regions when you first create the gallery image version, then update the gallery image version by adding more target regions.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  9. Posible Bug when create a new VM with powershell

    When I create a Linux VM with PS, whith a migrated vhd between suscriptions, the machine is created correctly but:
    1) Name of the Machine don't appear in 'General Information'
    2) Connect button is in grey (inactive)
    Machine is working ok, and we can connect to it with putty, but these two elements are not ok.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  10. SharePoint 2013 Non-HA Template Doesn't work

    Twice today I have tried to use the SharePoint 2013 Non-HA Template and it has failed both times. Once when it was trying to create the domain controller and the second time when it was trying to create the SQL Server.

    Can this template be fixed ?

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  11. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  12. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  13. New SQL Server Resource Provider not idempotent?

    It seems that the new Microsoft.SqlVirtualMachine/SqlVirtualMachines resource provider is not idempotent when deployed from an ARM template. Every first deployment succeeds and yields the expected results, but subsequent deployments time out on the Microsoft.SqlVirtualMachine/SqlVirtualMachines resource after > 2 hours.

    Currently, the workaround is to move this resource to a separate template which is kicked off only once, but obviously that's not ideal. Am I missing something, or is this a bug and should the Microsoft.SqlVirtualMachine/SqlVirtualMachines be idempotent?

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  14. Usernames longer than 14 are not valid, but allowed to be created in new VM wizard.

    When creating a new VM from the portal, an admin user name greater than 14 characters can be created, but it is not valid. The result was I could not remote into the VM as the user credentials were rejected. It wasn't until I went and tried to reset the password did I receive the validation error that the username I had selected was too long. I had to delete the VM and recreate it with a shorter username before I could RDP into the new Virtual Machine.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow machines without a public IP to go outbound to the internet when in the same group as one machine with a Standard Public IP SKU

    When you have the following configuration:

    1 HA Group
    1 Machine with Standard public Sku
    N number of machines with no public IP assigned.

    The machines with no public IP cannot go to the internet. MS support tell me this is a feature.

    This works differently to the following:

    1 HA Group
    1 Machine with BASIC public Sku
    N number of machines with no public IP assigned.

    All of the machines in this group can go outbound to the internet.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  16. Set-AzureRmVMBootDiagnostics has no effect

    The Set-AzureRmVMBootDiagnostics PowerShell cmdlet returns without an error, however, the boot diagnostics for a VM does not appear to change.

    Also, the documentation for the Set-AzureRmVMBootDiagnostics cmdlet specifies the ResourceGroupName is the resource group of the VM, however, the cmdlet only works when the resource group of the storage account is used.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  17. management portal is not showing the updated state

    management portal is not showing the updated state

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  18. If more than 8 disks are connected at image deployment of SQL Server, the number of columns is not properly set

    When deploying the image of SQL Server, the number of disks is set to the parameter of sqlStorageDisksCount, but when IaaS agent is running New-VirtualDisk, it is not used as the number of columns, so 16 disks Even if you set up, the number of columns is 8, and Virtual Disk is created.

    When IaaS Agent runs New-VirtualDisk and creates a disk, it uses [NumberOfColumns <sqlStorageDisksCount parameter>] instead of [AutoNumberOfColumns] and uses the number of connected disks as the number of columns and 8 If you are connecting more disks than you want, let me set the appropriate number of…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  19. Make the Classic Portal work .

    I created new Azure account and went to the the new portal and created a storage account. I then went to the classic portal and did not see it ??? So I deleted the storage account in the new portal and created one in the classic -- BUT I could not get the Region to be US East in the classic portal only in the new Portal ?????? Go figure ???? How ridiculous is this ! I can not stand the new portal -- its as complex and stupid as AWS . So if you want to loose more customers…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  20. Azure VM Agent support for Forced Tunneling / User Defined Routes

    To meet legal requirements, like many, we employ "forced tunneling", to push traffic through our proxy server. Many of your services, including agents are "Proxy Unaware" (like your developers!)

    One possible way to overcome this, is to add a UDR to the special VM Agent IP of 168.63.129.16, however, when I try to create a route of 168.63.129.16/32, I get the below error, essentially saying it is in a restricted address space.

    Please remove this restriction, post hast.

    This is an incredibly quick and easy way to overcome your lack of proxy support with the VM agent.

    Full error message: …

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4
  • Don't see your idea?

Virtual Machines

Feedback and Knowledge Base