Deploy Azure Stack On An Azure VM (Part 1)

Share This Post

Share on facebook
Share on linkedin
Share on twitter
Share on email


  • Request extra CPU quota from Microsoft support for the region that you are looking to use
    • You must have a minimum of unused 16 vCPU quota at a minimum for the DSv3 or ESv3 VM series
    • Default quota limit is 10 vCPUs
  • Create a new Azure AD user with Global admin rights
  • Advisable to use a single complex password to avoid confusion
    • Obviously, this is only recommended as we are merely using this for testing and the environment will be destroyed afterwards

Basic Information

Deploy Azure Stack Hyper-V Host as an Azure VM (Approx 20 minutes)

Log into Azure Stack Host

  • Connect to the newly deployed Azure VM using RDP to its public IP address
  • Username in the template is administrator” 
  • Password is whatever you set
    • You may need to use the Azure password reset tool to reset the password

Run Install-ASDK.ps1 script on the desktop (Approx 6 hours)

  • Open PowerShell (ensure you run as administrator) and run the following:

    Set-Location "C:\AzureStackOnAzureVM"
  • Enter the password for the local “Administrator” user (same password used to log into the computer)
    • Re-enter the password
  • Enter the username of the Azure AD user with Global Admin permission that you created earlier
  • Enter the Azure AD user password
    • Re-enter the password
  • Enter 1” to select Azure Latest 1807” and enter “C” to confirm
  • The deployment will start. After about one hour, the system will auto-shutdown. This happens after the Azure VM is joined to the domain.
    • Wait about 6 hours for the rest of the deployment to complete
    • If you sign in as a local admin after the machine is joined to the domain, you won’t see the deployment progress.
    • Do not rerun deployment, instead sign out and sign back in as “AzureStack\AzureStackAdmin” to validate that the deployment process is still running.

Post-Installation Configuration (Approx 1.5 hours)

Subscribe To Our Newsletter

Get updates and learn from the best

More To Explore


New Azure Container Instance Vulnerability — What to do?

Just yesterday, Microsoft disclosed a new (and yet to be clarified) Azure Container Instance vulnerability — From the information shared in the disclosure, it seems

Protecting against #ChaosDB

Cloud security researchers @sagitz and @nirohfeld who both work at Wiz recently discovered what I think is a major vulnerability that exploits the recent CosmosDB Jupyter notebook feature to

Do You Want To Boost Your Business?

drop us a line and keep in touch