none
Azure Virtual Machine creation wizard is broken? RRS feed

  • Question

  • Hi guys,

    I have gone through the Azure VM creation wizard and noticed it always completely ignores the settings I select if I run it normally through the Azure Portal.  I basically go in to Create a virtual machine, enter a name, select a OS, select disk type, select networking with no public ip and no nsg, etc and then at the very end hit create.  I then go back and look and the VM did create a nsg and assign it a public IP(even though I told it not to do either), it does use a premium SSD, even though I chose standard SSD, etc.  It has the correct name and OS and does have the correct shutdown policy(but I noticed that does not always work correctly the first night), but everything else is not correct.  Each time I create a VM, I have to go back through it again and delete the public IP and reassign the nsg and delete then delete the one I told it not to create.  I have gone through the wizard severl times and do not think I am making the wrong selections, but if I download the json template at the end of the process I notice it has completely different settings than I selected.  Does anyone else have any ideas on this?  What am I missing?

    Thanks,


    Dave




    • Edited by DaveBryan37 Friday, December 27, 2019 5:42 PM
    Friday, December 27, 2019 5:39 PM

All replies

  • Hi Dave,

    this does not match my experience.

    Can you make a recording of the steps you are going through and the outcome - and post it for us to review?

    hth
    Marcin

    Friday, December 27, 2019 5:55 PM
  • I just did it again and cannot reproduce the problem.  If anyone has ever seen that before or can even think of a way I might have screwed up the wizard process, etc. let me know 

    Dave


    • Edited by DaveBryan37 Friday, December 27, 2019 9:39 PM
    • Proposed as answer by Spam filter Saturday, December 28, 2019 12:21 AM
    Friday, December 27, 2019 9:39 PM
  • Hi Dave,

    good to see this is resolved - I gather it's possible that you might have missed a step somewhere in the process - but without opening a support case with the Azure support team, that's not likely to be determined

    rgds
    Marcin

    Saturday, December 28, 2019 12:04 AM