Prerequisites for Deploying DNS Proxy into your Resource Group
The following are prerequisites you should consider before deploying DNS proxy into your Resource Group. For further information, you can read Manage Azure resource groups by using the Azure portal 
.
DNS Proxy must be launched into an existing resource group with an existing Azure Virtual Network (VNet) and Network Security Group (NSG).
The subnet that DNS Proxy is launched into must have an NSG associated with it.
To access the UI, HTTPS or HTTP ports must be open on the VNet.
By default, ports 80, 443 and 7780 are open on the NSG. Ports 80 and 443 are required to access the DNS Proxy UI. Port 7780 Is needed to communicate with other DNS Proxies in your Azure estate.
Azure Command-Line Interface (CLI) must be installed on the machine that runs the DNS Proxy installer. See https://docs.microsoft.com/en-us/cli/azure/install-azure-cli
.You must have a default ssh key in your ~/.ssh folder (C:\Users[username].ssh). If you do not have one, it can be generated in PowerShell with the following command:
"ssh-keygen -m PEM -t rsa -b 4096".