One-Click Deployment for Azure NetApp Files (ANF)


Azure NetApp Files (ANF for short) is no longer so new and has already proven in various projects where the advantages of this enterprise storage is.

In this blog entry, I want to talk less about the Use Cases. But give the proof-of-concept (PoC in short) the ability to simplify the ANF deployment,
or via Powershell. Of course, you can do everything as usual via the Azure Portal (

I have become accustomed to deploying ANF into the customer’s environment via Powershell for various PoC’s. For this reason, I would like to use my Powershellscript here for and explain in part.

Basic requirements

  1. The first requirement to use ANF is to register the subscription for ANF. You can find the information in this article:
  2. Next, you should familiarize yourself with the documentation of ANF. Information can be found here:
  3. The next step is to download my Powershell Script from Github. You can find the script here:

The Script

Before we start the deployment a few words to the script.

The script expects various paramters for the deployment, which are requested after start. Things like Location, ResourceGroup Name, VNet & Subnet are queried.
With this script, an ANF account, pool & volume with all associated resources is deployed in the West Europe & North Europe region. You can also use
Snapshots for an existing volume. If you want to deploy ANF only in one region, you can deactivate the lines in the script for the 2nd region.

More Parameters

There are various parameters which I have entered firmly, but which can also be changed or adjusted as required.

more parameters anf azure netapp files

Install Modules

Later, the script checks whether all necessary Az Powershell modules are available and are up to date. If not, they will be downloaded and installed.

install module anf azure netapp files

Connect to Azure

The next step is to connect to Azure and the subscription.

connect to azure anf azure netapp files

ANF Deployment

The next block deploys the ANF and dependent resources, even in the 2nd location.

first location anf azure netapp files

second location anf azure netapp files

If desired, a snapshot of a volume can still be performed.

snapshot anf azure netapp files

Delete Resources

Once all the resources have been deployed, there will be costs.
So if this is not desired, simply delete the voluem. or the entire Resource Group.

delete resources anf azure netapp files

Either you start the script block by block, or alternatively you can start one line of Powershell and specify the individual parameter values after the script.

For the deployment in one region

.\ANF-PoC-Deployment.ps1 -location westeurope -resourcegroup anfwe – anfaccountname anfwe -creationtoken anfwetest -subnetaddressprefix -networkaddressprefix

Other Deployment method

For the deployment in two regions

.\ANF-PoC-Deployment.ps1 -location westeurope -resourcegroup anfwe – anfaccountname anfwe -creationtoken anfwetest -subnetaddressprefix -networkaddressprefix -secondlocation northeurope -secondresourcegroup anfne – secondanfaccountname anfne -secondcreationtoken anfnetest -secondsubnetaddressprefix -secondnetworkaddressprefix

The End

There is certainly a lot to improve on the script, but I’m constantly working on it.
Next I would try a deployment via ARM Templates.

For more infromation about the Use Cases use this Link:

Hashtags: #AzureNetAppFiles #Azure #cloudmigration #datacenters #storage #data #cloudstorage #hybridcloud #NetApp #Microsoft #workloads #applications

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.

Azure NetApp Files – Enterprise file storage, powered by NetApp


I have consciously chosen this title. Azure NetApp Files (ANF) is becoming increasingly important and therefore I wolud like to go into a little more detail with this article.
ANF is an enterprise-class, high-performance and metered file storange service.

Today, 80% of enterprise data is stored in files – and even so-called native cloud applications often use files to structure the information that is stored in the cloud. So whether you’re moving enterprise applications and workloads to the cloud, or you want to accelerate many cloud applications, a high-performance, fully managed file service in the cloud is critical. Azure NetApp Files offer a fully managed service, built on NetApp technology, running in the cloud. These services support SMB, NFSv3, and NFSv4 protocols, and they allow full data mobility between any endpoint for hybrid and multi-cloud flexibility. Experience NetApp’s data management capabilities and the cloud’s unlimited availability and scalability, without any of the administrative tasks and overhead.


Azure NetApp Files

Key Features

  • Azure NetApp Files supports multiple protocol and enables lift and shift migration from On-prem to Azure
  • Multiple performance tiers for your workload requirements
  • Simple integration with other Azure Services
  • Manage with Azure Portal, CLI, Powershel or REST API
  • Three performance tiers (Standard, Premium and Ultra)
  • Integrate with Azure Active Directory for Role-Based-Access
  • Complies with leading industry certifications, with 99,99 % availabiility



Before starting with Azure NetApp Files you have to register for Azure NetApp Files. You can do it with this Link (

Newest Announcement

The newest announcement is that ANF is also available in the Azure Region Germany and UAE.


Use Cases

Since Microsoft announced general availability of Azure NetApp Files a year ago, some of the key use cases that have emerged include:

  • Windows Virtual Desktop (WVD) (and in the future in combinition with Microsoft Azure Stack Hub – Announcement on Build 2020)
  • SAP
  • High-performance computing (HPC)

But in my opinion there are also Use Cases like this:

  • Azure NetApp Files with Oracle
  • Azure NetApp Files with Azure Kubernetes Service (also in combinition with Microsoft Azure Stack Hub)

and many more on the Microsoft´s Website (


An all-round successfull service, I think, to run the usual workloads in the cloud.


More on this in the future.

Hashtags: #AzureNetAppFiles #Azure #cloudmigration #datacenters #storage #data #cloudstorage #hybridcloud #NetApp #Microsoft #workloads #applications