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. Prevent the 'failed' state when VMSS autoscaled to subnet namespace size

    VMSS easily turn 'failed' status with following step and cannot recover without delete and re-create the VMSS.

    Repro step is:
    1. Create Vnet and subnets. The address space of subnet for VMSS is /27 (for example)
    2. Create AppGW(Small/1instance, no publicIP) in Vnet
    3. Create VMSS under AppGW
    ... set the Autoscale rule as Min/Max/default : 2/25/2
    ... In my case, I created Standard_DS1_v2 size VMSS
    4. change Autoscale parameter to 16/25/16
    5. change Autoscale parameter to 25/25/25
    =>reproduces

    want to prevent the state. thanks,

    11 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  VMSS  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow update of gallery image for VMSS

    When referencing a custom image in a VMSS from a Shared Image Gallery (Preview), it cannot be updated to refer to a new image. This results in an error code "PropertyChangeNotAllowed".

    Today, a VMSS can be updated to a new image reference when it references a managed image that does not reside in a Shared Image Gallery.

    7 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  VMSS  ·  Flag idea as inappropriate…  ·  Admin →
  3. Enable Powershell Cmdlet for migrating VMSS to use Managed Disk

    Similar to the cmdlet ConvertTo-AzVMManagedDisk - have an option to trigger a VMSS migration to use Managed Disk

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  VMSS  ·  Flag idea as inappropriate…  ·  Admin →
  4. N-Series VMs with AMD CPUs

    Please offer N-Series units with AMD Epyc CPUs.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  VMSS  ·  Flag idea as inappropriate…  ·  Admin →
  5. where do i put a password for the oracle vm?

    in the step Automate database startup and shutdown needs a password? the password is: OraPasswd1 ? it does not work!

    https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/oracle/oracle-database-quick-create?view=sql-server-2016

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  VMSS  ·  Flag idea as inappropriate…  ·  Admin →
  6. Azure Virtual Machine Scale Set

    The ability to select and register the Azure Virtual Machine Scale Set to Azure Automation DSC. Currently you are only able to select Virtual Machines. This becomes a problem when you need to refresh the key after a year has expired.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  VMSS  ·  Flag idea as inappropriate…  ·  Admin →
  7. it does not allow size in a virtual machine

    I have created a virtual machine with a free 30 day trial of Azure (with credit 161.90), following the instructions of Microsoft but at the time of selecting the size in select size

    It shows me the following image ...

    https://docs.microsoft.com/en-us/azure/virtual-machines/windows/quick-create-portal?WT.mc_id=UI_empg

    I do not understand why the size of the vm can not be created.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  VMSS  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow me to dictate CPU and Memory in calculator to choose machines vs trying to understand your A-Z machine criteria... 4 core, 16gb, XX s

    Calculator flexibility - Allow me to dictate CPU and Memory in your calculator to choose machines vs trying to understand your A-Z machine criteria... 4 core, 16gb, then storage, then location... then give me options. I could care less about. Use my requirements to drive machine selection vs trying to understand you machine classes... When I have 20K workloads and 300+ various machine sizing's. Various variables have less impact in pricing - prioritize those that have $$$ impact. Machine class and region should be less prioritized and better defined (South Central US???) really? Net Net is I should not have…

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  VMSS  ·  Flag idea as inappropriate…  ·  Admin →
  9. vmss python sample

    provide a sample for python vmss manamgement.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  VMSS  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow customization of eviction logic of scale sets

    One should be able to select which VM will be evicted from the scale set when the ScaleIn rule triggers. Or, at least reject the choice made by the existing logic.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  VMSS  ·  Flag idea as inappropriate…  ·  Admin →
  11. scheduled event is missing the delete/scale-in event for scale sets

    to properly demote cluster members during a scale-in or delete operation on a scale set node, the schedule event endpoint should provide the event-type delete or similar.

    then it would be possible, to take proper local actions before the node is gone.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  VMSS  ·  Flag idea as inappropriate…  ·  Admin →
  12. Automatic scaling up/down virtual machines very limited

    Automatic scale up of virtual machines seems to be very limited in Azure:
    a) it does only work for certain types of virtual machines
    b) you can only scale up/down to a single other point, which is predefined by Azure
    c) you cannot control details e.g. amount of vcpu or ram

    Also, getting automatic vertical scaling to work needs one to get pretty involved. You have documentation about this topic, but somehow documentation is confusing and you don't find easily where to start / what to do in what order.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

Virtual Machines

Feedback and Knowledge Base