Virtual Machines

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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
    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 →
  2. KeyVaultForWindows does not install the full certificate chain

    Azure Key Vault Extension, KeyVaultForWindows installs only the leaf certificate and not the full chain. Is this the expected behavior?

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

    18 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

  10. 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
    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. 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": {

            &quot;value&quot;: &quot;5&quot;
    

    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': {

    &#39;code&#39;: &#39;InvalidParameter&#39;,
    
    &#39;message&#39;: &#39;The value of parameter platformFaultDomainCount is invalid.&#39;,
    &#39;target&#39;: &#39;platformFaultDomainCount&#39;

    }
    }

    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

  12. az vm create (windows server) - parameter linuxConfiguration is invalid

    $ az --version
    azure-cli 2.0.77

    command-modules-nspkg 2.0.3
    core 2.0.77
    nspkg 3.0.4
    telemetry 1.0.4

    Python location '/opt/az/bin/python3'
    Extensions directory '/home/xxxxxxxx/.azure/cliextensions'

    Python (Linux) 3.6.5 (default, Nov 22 2019, 05:32:09)
    [GCC 7.4.0]

    Legal docs and information: aka.ms/AzureCliLegal
    Your CLI is up-to-date.

    >>> azcli script <<<
    az group create ...
    az storage account create ...
    az disk create ...
    az network nic create ...

    az vm create --name ${RESOURCENAME} \
    --admin-password VerySecret \
    --admin-username AdminAccount \
    --attach-data-disks ${DATADISK01} \
    --authentication-type password \
    --boot-diagnostics-storage ${STORAGEACCOUNT} \
    --enable-agent true \
    --image MicrosoftSQLServer:sql2019-ws2019:sqldev:latest \
    --location westeurope
    --nics ${NETWORKCARD} \
    --os-disk-caching ReadWrite \
    --os-disk-name ${OSDISKNAME} \
    --size Standard…

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

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

  15. 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 StandardD13v2

    az vm show -g SAP -n clitest1 -d

    "hardwareProfile": {

    &quot;vmSize&quot;: &quot;Standard_D13_v2&quot;
    

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

    az vm show -g SAP -n clitest2 -d

    "hardwareProfile": {

    &quot;vmSize&quot;: &quot;Standard_D13_V2&quot;
    

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

  18. 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 →
  19. "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
    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 →
  20. 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
    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 5
  • Don't see your idea?

Virtual Machines

Categories

Feedback and Knowledge Base