With the Azure Stack Development Kit (ASDK) having a limited lifespan per deployment I need a way to be able to spin up the ASDK fairly fast for internal use and for clients who want to take Azure Stack for a spin. There are more and more great resources coming online on how to deploy and manage the ASDK as well as Azure Stack in general. However, most of these examples are manual setup and not very automated. I do know that guys like Thomas Maurer and Mark Scholman are working on automated solutions so I will keep watching their Twitter feeds and blogs as well.
I also have a requirement of being able to spin the ASDK up on an Azure VM as well. This just makes it easier for our external clients to access the ASDK management server. However, this can become a pricey solution so just be aware that the VM’s I will be using is not cheap and we will control when they can be powered on and off for now. If one of our clients wants to host this VM on their own subscription then we will work with that as well.
I did find two blogs that were very good. One is a manual deployment of the VM within Azure and also a manual deployment of the ASDK.
The one that I am going to follow and give my experience using is more automated and uses an ARM template to build out the Azure VM.
This was pretty much self-explanatory. From Yagmur Sahin’s blog you just need to click on Deploy to Azure button. You can also find this on his Github project as well.
When the template opens in Azure make sure you select an active Subscription. For the resource group, I created a new resource group. Each new ASDK I will deploy into Azure I will have a separate resource group for.
Now here are notes on my deployment of this template:
- We are going to be using a Standard_E32s_v3 VM for this project.
- This is a big VM with a lot of cores and memory. However, just a heads up, these VM’s are not available in every Azure region at this time. I do know that they are available at the Centra US location so I went with Central US.
- I add 8 256 disk instead of the 4 that is default in this template.
- I gave it a public name and made sure the password met the requirements.
- I disabled the Auto Shutdown Status
Make sure you put a check the I agree to terms and conditions then click purchase checkbox.
This should take a few minutes to build and be ready for the next step of deploying the ASDK. If you are bored you can monitor the deployment.
Once the deployment of the VM has finished you can RDP to the server using the public name. Log on as the local Administrator with the password you specified.
Once logged on:
- Click the Install-ASDK shortcut on the desktop. Make sure it runs the PowerShell command as Administrator.Note: At the time of writing this blog the newest release of the ASDK was 1802. However, the script that runs doesn’t seem to be able to locate 1802 or 1801. There was no release for 1801 so don’t worry about that. The only 2 releases the script seems to find is 1712 and 1711.
- When prompted enter your Administrator Password and confirm the password.This will validate you are using the correct local Administrator password on the host server.
- Next, enter your Tenant Admin.This script configures the ASDK to use AAD. If you plan to use ADFS then this process won’t work for you.
- Next, enter your Tenant Admin password and confirm it.
- Next, select the ASDK version you will want to deploy.
- At the confirmation prompt, verify your information is correct and click any key to continue with the installation.
The deployment of the ASDK will take at least 4 hours. During the installation, the VM will be rebooted. Once rebooted you can log on using the AzureStack\AzureStackAdmin account to monitor the deployment. The password will be the same as the local Administrator password you used.
At this time you have deployed the ASDK. There are shortcuts on the desktop for the Tenant Portal and the Admin Portal. At this point, you still have a few more task to follow.
Please follow the above Microsoft documentation to finish your deployment:
- Activate the administrator and tenant portals
- Reset the password expiration policy
- Install PowerShell for Azure Stack
- Download the Azure Stack Tools from Github
- Register Azure Stack with your Azure Subscription
- Add a default Image
From here you can add other services like the SQL and/or MySQL as PaaS and the App Service as PaaS. Populate your marketplace and create your plans, offers, and quotas.
I have a blog on how to deploy App Services on the ASDK and will blog about the others items as well one day.
I hope this helped. Have fun exploring the ASDK.