Microsoft Azure Stack Development Kit – new Region Name in parallel operation with several ASDKs


In various customer discussions, it emerged that a single Azure Stack Development Kit (ASDK) did not correspond to the desired test scenarios. Especially since new ASDK versions should be deployed at regular intervals due to updates (monthly).
This customer scenario is exclusively an ASDK system, which is located in the customer’s internal network. However, there is certainly also a possibility to set up the system in such a way that it can be used by Managed Service Providers.

This gave us the idea to get more involved with the network configuration of the ASDK and, if possible, to make changes to it. Because if one speaks of a parallel operation of ASDKs, then one also talks about Tenant VPN access. The review of various blog posts on the net did not lead to the desired customer request.

Customer wishes

are defined in the following form:
– several ASDKs in the same network
– Different configurations of the ASDKs
– Connected and Disconnected Mode
– with and without App Services
– with Kubernetes
– with and without AD FS and AAD
– Access from the customer’s local network with various Clients

asdk - Customer Requirements

asdk - Customer wishes


Change network configuration

With Powershell, we were able to adapt the Config XML of the ASDK to the desired customer scenarios. It is important to know that an ASDK has 62 IP addresses available, from which 31 IP addresses are already subtracted by the pure installation. Each additional resource provider installation requires IP addresses from this pool. There’s not much left in the end. With the well known subnetting you can get the desired result here.

asdk - internal network configuration


New Region Name

In the next step, additional parameter values are added to the InstallPOC. ps1 script in the front section of the parameters. These serve to adapt the region names of the respective ASDKs. E. g. from “local”; to “hamburg”; or “RZ1”. The decision lies in the customer configuration in which the ASDks are added.

asdk - New Region Name

Since the ASDK has now adapted the RegionName, the custom DomainSuffix must also be specified if a Post Deploymennt is used for the installation of App Services (Script Matt McSpirit). It is the same name as the RegionName of the ASDK.


Post deployment

asdk - Post deployment

DNS Delegation

Since the network IP address range of the ASDK has been adapted, it must also be adapted either in the firewall, or the router where the various ASDKs are located. Just like setting up or configuring a DNS delegation.

asdk - DNS Delegation

Let´s check the customer request

The last hurdle is importing the ASDK certificates to all clients interacting with the systems.

asdk - customer request


The way to this overall configuration was not an easy one, but the time invested was worth it. This makes it possible to provide customers with differently configured systems for a Proof-of-Concept (PoC). The total running time of the PoC may also be reduced in the positive decision towards the Azure Stack Integrated System.

Questions, suggestions and wishes are very welcome.

Use the Azure DevOps Demo Generator for your own task planning – creation of a template – #AzureStackHub


In this post I would like to go into more detail about the Azure DevOps Demo (Project) Generator, because in my current activities as an Operator in an Azure Stack Hub project I am dealing with recurring tasks from the operation. That’s why I created my to do’s in Azure DevOps with stories and tasks and entered all information about websites and help in the stories.

These stories and tasks refer to the Azure Stack Hub Operator tasks associated with updates from Microsoft and the manufacturer. In my case, it is a Dell Technologies Azure Stack Hub 14G Integrated System.

One advantage of this Azure DevOps project is that individual people can be assigned different stories and tasks and thus get an overview of who is working on which tasks. In addition, it can be traced in retrospect, where there are problems with the tasks approaching. It is important that every employee maintains all the necessary information in his stories and tasks.


Azure DevOps Generator


Example for a Story

The stories can easily be expanded or changed to personal needs.

Azure DevOps Story


Example for a Task

The task can also be adapted according to personal needs.

Azure DevOps Task



Azure DevOps Demo Generator is available here.

A how-toto create a template and use it in a project can be found here.


If you are interested in the template, please feel free to contact me. I would then make it available.