You can use a normal DNS Server Controller, including one that is already connected to a DNS server, and configure it to work as an Azure DNS connector.
Currently, the Controller must be able to connect to:
Connection via a web proxy is not yet supported.
In order to be able to connect to a Microsoft Azure DNS instance, you want to have the following Microsoft Azure DNS details ready:
- tenant ID
Open the "Resource Groups" (e.g. from "More Services" if the icon is not displayed). Then click on the resource group you want to include in M&M. Under Essentials (right-most entry there is the subscript ID displayed - another way to get it is also described under "subscriber ID" in this bullet list.
In the next sub-menu click on "Access Control (IAM)", then on the user account and then on the role that is assigned it to. The tenant ID is displayed as "Object ID". The client ID is also displayed as "App ID". Another way to get the client ID is described further down.
- subscriber ID
The Subscription ID can be retrieved by the Azure Portal. After login to the Portal click on the "More Services" icon ">" or press the "B" key. In the search field enter "Subscriptions" or select it from the list of services.
The Subscription IDs are displayed.
- client ID
The client ID is basically the Application ID of your registered application in Azure. To get the ID just open the "More Services" and search for "App registrations". Then click on the appropriate app that is used with your Azure DNS.
The APPLICATION ID is the client ID.
- client password
- list of Azure resource groups that you plan to manage in M&M
First install the DNS Server Controller on a Windows Server. Then open the preferences.cfg file (c:\ProgramData\Men and Mice\DNS Server Controller) and
add the following XML-tags to the file:
After the change, restart the DNS Server Controller. Use the Add DNS Server dialog, select the server type "Azure DNS", and add the Azure DNS Server Controller to the M&M Management Console.
For more information about the Microsoft Azure cloud-based DNS service, see: