Virtual Machines

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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.

    21 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 →

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

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

    We’ll send you updates on this idea

    5 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. Creating a Low Priority VMSS using Portal has FD count bug

    When creating a VMSS with Low Priority, FaultDomain Count is set to 5 by default.

    "spreadingAlgorithmPlatformFaultDomainCount": {

            "value": "5"
    

    Obviously this is a bug, because Low Priority VMSS only supports Single Fault Domain
    https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-use-low-priority

    If we go with the default value, we got FD count error.

    Deployment failed. Correlation ID:
    {
    'error': {

    'code': 'InvalidParameter',
    
    'message': 'The value of parameter platformFaultDomainCount is invalid.',
    'target': 'platformFaultDomainCount'

    }
    }

    I think this needs to be fixed in Portal Front-end side.

    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 →

    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. 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 →
  5. Getting Duplicate search results for "Windows Virtual Desktop - Provision a host pool"

    Getting Duplicate results coming for the following keyword in azure portal

    Azure portal -> Create Resource -> type "Windows Virtual" in "Search the Marketplace" search box

    "Windows Virtual Desktop - Provision a host pool"

    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 →

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

    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.

  7. 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: Microsoft
    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

  • Don't see your idea?

Virtual Machines

Categories

Feedback and Knowledge Base