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. Virtual Resource Deletion process

    I have suggestion wrt to deleting a resources,I think we need to create a process while creating a VM,That this resource will follow a deleteion approval process to make sure its not delted without MFA andhas to be retained for 24 to 48 hours for saftey puprose

    Virtual Deletion is a simple process but it has to be equal to physical security not from data perspective but also from physical deletion perspective ,

    so when someone deletes a resource it cannot just go away like that which may increase the customer fear of cloud computing when compare to Physical computing,

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  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

  2. 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
    Sign in
    (thinking…)
    Sign in with: oidc
    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

  3. Request add a FirstCreationTime field for Azure VM

    Considering the requirement for auditing, could you please add a FirstCreationTime field for Azure VM?

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

    We’ll send you updates on this idea

    0 comments  ·  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

  4. Detect Azure VM on BIOS

    A way using systeminfo or dmidecode to detect if a machine is running on azure, amazon has his enabled on bios.

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  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

  5. Clone VM without sacrificing the original to the "sysprep" gods

    I often set up Linux VMs with attached disks, and need to 1-click clone the VM to make new ones for parallel work.

    For some reason Azure requires us to prepare the VM for a ritual sacrifice with "sysprep" or something, and destroying the original magically makes a clone-able VM. If I need to make modifications I have to re-deploy and then re-sacrifice again. This seems way too complicated.

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Linux  ·  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

  6. "accelerated networking"

    Allow us to enable or disable Accelerated Networking via the Portal, in addition to the command line methods.

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

    We’ll send you updates on this idea

    1 comment  ·  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

  7. 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 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Windows  ·  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

  8. VMSS rolling updates on custom images

    Allow rolling updates on custom images.

    Currently if you build a custom image and create a VMSS with it you have to manually "roll it out" via upgrade. Seems silly when the image is housed and built just like any other. were just talking about watching the upgrade process by way of the VM's "upgrade status"

    seems doable not sure why its held back, especially when the VMSS set knows its "not current"

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  VMSS  ·  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

  9. 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 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Windows  ·  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

  10. After configuration is complete, add new nodes to the product rotation.

    An update occurs when a new Node enters product rotation.
    If a VM is deployed in the Node during updating, the VM is not started until the updating is complete.
    Therefore, we put Node in rotation after setting is completed.

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  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

  11. Provide an API to tell whether a promo VM size is expired

    There doesn't seem to be any way to tell via the VM APIs that a promo size is expired in a region.

    Eg, in West US, the "list sizes" API includes promo sizes like Standard_DS3_v2_Promo in the result, and the usages API says I have quota for standardDSv2PromoFamily, so it looks like I should be able to create a Standard_DS3_v2_Promo VM, but I can't.

    There needs to be a way to tell this programatically. "Look in the portal, it's grayed out" is NOT an API. "Read this blog post" is NOT an API.

    Maybe this should be included as a…

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  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. Support put metrics from multiple nodes from a VMSS into a single chart in metric explorer

    Currently, from metric explorer I can view some metrics from a single node from a VMSS. For example, I can view CPU percentage for node-0 in a chart. However, it will be more useful if I can put CPU percentage metrics for other nodes in the same chart so that I can view all CPU usage in a single chart. Then I can do a second chart for network for all nodes.

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  VMSS  ·  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

  13. The monitoring of blob-fuse mounted on Linux server through azure OMS

    How to alert on unmounted blob fuse drive on linux VM though OMS monitoring solution.

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Linux  ·  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

  14. 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.

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

    We’ll send you updates on this idea

    0 comments  ·  Windows  ·  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

  15. 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 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Windows  ·  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

  16. You really gotta fix those machines.. If Paperspace has AIR machine with graphics card, 4 GB RAM, 2cores processor, hardware

    Thanks, dear.. You really gotta fix those machines.. If Paperspace has AIR machine with graphics card, 4 GB RAM, 2cores processor, hardware encoding, for 18$ flat price.. AZURE should have 4 high performance processors for 3$, + 4 GB RAM + 3$, + Storage usage + 0.10 cent per GB :)

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Windows  ·  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

  17. Azure don't give any warning and providing size which will not work for the image we select

    Azure don't give any warning and providing size which will not work for the image we select:

    You can provision a windows Server 2016 with Basic_A0. But the size is below requirement and you won't be able to login and make that server work.

    Most of the time server will go in the failed state.

    I recommend, if azure can give some kind of warning of totally don't provide the size. when the selected size don't meet the minimum requirement for the selected server.

    Regarding the Case - 119052422002805

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Windows  ·  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

  18. Notification for the capacity for requested VM size

    It is quite critical that we could receive the notification for running out of the requested VM size.
    In our customer, the allocation failure was happened in the following critical scenarios:
    • Restoring VM in Azure Backup
    • Failover in ASR
    • Starting VM
    Getting that notification earlier, they can avoid the error by considering another size.

    7 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  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

  19. Custom VM Sizing

    Allow for custom sizing of CPU and RAM (and possibly other schedulable resources like GPUs) in VM provisioning. This provides greater flexibility in workload scheduling than standard SKUs, and enables higher level tooling to take advantage of this for more sophisticated purposes.

    See https://cloud.google.com/custom-machine-types/

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  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

  20. The virtual machines of the B series do not inform about the bandwidth. All series report about bandwidth except type B machines. Accordin

    The virtual machines of the B series do not inform about the bandwidth.

    All series report about bandwidth except type B machines.

    According to Microsoft they do not inform because it is a variant connection, but at least they should indicate the minimum and maximum.

    As in all series in the NIC part, the bandwidth must also appear.

    1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    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

← Previous 1 3 4 5 70 71
  • Don't see your idea?

Virtual Machines

Feedback and Knowledge Base