Deploying Azure Stack Development Kit – Part II

Great, thanks for hanging in there, in part 1 we covered how you can deploy the Azure Stack Development Kit instance on a single node. In the second part, we will talk about how you can complete the post-installation steps and deploy your first test VM on the ASDK instance.

Activate the Admin and Tenant Portals:

This step is only required if you are using Azure AD for authentication. Go to the admin and tenant portal links below and then accept the EULA:

Reset the Password expiration policy:

Run the following command from an elevated PowerShell prompt:

Set-ADDefaultDomainPasswordPolicy -MaxPasswordAge 180.00:00:00 -Identity azurestack.local

Install the Azure Stack PowerShell modules

To install the Azure StackPowerShell modules, execute the following PowerShell commands:

Set-PSRepository -Name "PSGallery" -InstallationPolicy Trusted
# Install the AzureRM.Bootstrapper module. Select Yes when prompted to install NuGet 
Install-Module -Name AzureRm.BootStrapper

# Install and import the API Version Profile required by Azure Stack into the current PowerShell session.
Use-AzureRmProfile -Profile 2017-03-09-profile -Force

Install-Module -Name AzureStack -RequiredVersion 1.2.11

And to confirm the installation, you can use the following command:

Get-Module -ListAvailable | where-Object {$_.Name -like “Azure*”}

Register Azure Stack

This step is usually required just for Azure Marketplace Syndication and Usage reporting for Azure Stack, but I was not able to upload a test VM iso to the ASDK instance using PowerShell without registering because my AzureStackAdmin user did not have a default subscription. So, I will say that this is kind of mandatory.

You will need an Azure account to register the Azure Stack instance, so if you don’t already have one, go ahead and sign up for one for free. You won’t be charged for anything that you deploy on the ASDK instance.

To register the ASDK instance, use the following PowerShell commands

Add-AzureRmAccount -EnvironmentName "AzureCloud"

Get-AzureRmSubscription -SubscriptionID '<Your Azure Subscription GUID>' | Select-AzureRmSubscription

Register-AzureRmResourceProvider -ProviderNamespace Microsoft.AzureStack

Import-Module .\RegisterWithAzure.psm1

$AzureContext = Get-AzureRmContext
$CloudAdminCred = Get-Credential -UserName AZURESTACK\CloudAdmin -Message "Enter the cloud domain credentials to access the privileged endpoint"
Set-AzsRegistration -CloudAdminCredential $CloudAdminCred `
 -PrivilegedEndpoint AzS-ERCS01 -BillingModel Development

Awesome, now that you have registered the ASDK instance with your Azure Account, you will be able to download any images from the Azure Marketplace onto your local instance and then start deploying VMs.

Add Default Image

Since you have the Azure Stack instance registered with Azure Cloud, you can go ahead and download images onto the Azure Stack instance. To do that log into the Azure Stack Administrator Portal

  1. In the left blade, click on more services > Marketplace Management > Add from Azure
  2. Find or search for the image that you want and click download.
  3. This process will take some time depending on your network bandwidth. Once the image is downloaded, you will see it show up in the Compute section.
  4. Now that you have a local image, in the next section, we will go ahead and deploy a Test VM instance using this image.

Create a Test VM

In my case, the image that I downloaded was a Windows Server 2016 Datacenter image. So to create a test VM, I logged in to the admin portal and:

  1. Under Compute, Select the Windows Server 2016 image and click Create.
  2. In the basics blade, enter a name, Username, Password, Resource Group etc and click Next.
  3. Select a size for the VM instance, click Next.
  4. Accept the defaults, or customize the settings as you want and then click Next.
  5. In the summary page, make sure that everything looks good and click Ok to create the virtual machine.
  6. You can see that the VM deployment has started under the Notifications pane.
  7. Once the VM is deployed, you can Remote Desktop into it using the IP address that was assigned and the Username/Password that you entered in step 2.

This is it. I hope this series helps you to deploy an Azure Stack Development Kit Instance. And please reach out to me or comment below if you have any questions regarding the deployment.

For additional things that you can do with the Azure Stack Instance, look at the Operator Documentation here:


One thought on “Deploying Azure Stack Development Kit – Part II

  1. Log in as CloudAdmin, and you’ll be able to run the Canary.Test script.

    You should also log in to a privileged endpoint and Test-Health. It also provides access to a Stop-AzureStack (and Start-AzureStack) command


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s