Onboarding Azure DNS
Overview
- Primary use case: Automated creation, update, and deletion of DNS records.
- Typical integrations: DNS-based validation for certificate issuance, delegated record management, and lifecycle automation.
- Recommended model: Use a dedicated service principal with least-privilege access scoped only to the required zones or resource groups.
Prerequisites
- An active Azure subscription containing the DNS zones to be managed.
- One or more Azure DNS zones already created.
- A dedicated application identity for AppViewX typically an Azure Entra ID application with client secret authentication.
- Network connectivity from AppViewX to Azure management endpoints.
- Administrative approval to assign Azure roles on the target resource scope.
Information to Collect Before Configuration
| Parameter | Description | Example / Notes |
|---|---|---|
| Tenant ID | Azure Entra tenant identifier used for authentication. | Directory-level ID associated with the Azure tenant. |
| Client ID | Application ID of the registered service principal. | Used together with the client secret. |
| Client Secret | Secret associated with the Azure application. | Store securely and rotate per your organizational policy. |
| Subscription ID | Azure subscription containing the DNS zones. | Required for locating the resource scope. |
| Resource Group | Resource group containing the DNS zone. | May be specific to DNS infrastructure. |
| DNS Zone Name | Zone to be managed by AppViewX. | For example, example.com. |
| Azure API Endpoint | Management endpoint used by Azure DNS APIs. | Standard Azure management URL:
https://management.azure.com |
Register an Application in Microsoft Entra ID
- Sign in to the Azure portal.
- Go to Microsoft Entra ID > App registrations > New registration.
- Enter a name for the application, such as AppViewX-DNS, and select the appropriate supported account type for your organization.
- Select Register.
- On the application overview page, copy and save the following values:
- Application (client) ID used as the Client ID in AppViewX.
- Directory (tenant) ID required to construct the Access Token URL.
- Go to Certificates & secrets > Client secrets > New client secret.
- Enter a description, set an expiry period, and select Add.
- Copy the secret Value immediately and store it securely.
Construct the Access Token URL
https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/tokenhttps://login.microsoftonline.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/oauth2/v2.0/tokenAssign the Required Role to the Service Principal
- Discover and list DNS zones.
- Retrieve DNS record sets.
- Create, update, and delete CNAME and TXT records for DCV.
To assign the role:
- In the Azure portal, go to the DNS zone or resource group that AppViewX will manage.
- Select Access control (IAM) > Add > Add role assignment.
- Under Role, search for and select DNS Zone Contributor.
- Under Members, select the registered application (service principal).
- Select Review + assign.
Minimum Required Azure RBAC Permissions
Public hosted zones
Grant the following permissions when
AppViewX manages public Azure DNS zones (Microsoft.Network/dnsZones).
| Azure resource action | Purpose | Required |
|---|---|---|
Microsoft.Network/dnsZones/read |
Discover and list public DNS zones in the subscription. | Yes |
Microsoft.Network/dnsZones/recordsets/read |
Enumerate all record sets within a public DNS zone. | Yes |
Microsoft.Network/dnsZones/CNAME/read |
Read existing CNAME record sets in a public DNS zone. | Yes |
Microsoft.Network/dnsZones/CNAME/write |
Create or update CNAME records for DCV validation. | Yes |
Microsoft.Network/dnsZones/CNAME/delete |
Remove CNAME records after DCV is complete. | Yes |
Microsoft.Network/dnsZones/TXT/read |
Read existing TXT record sets in a public DNS zone. | Yes |
Microsoft.Network/dnsZones/TXT/write |
Create or update TXT records for DCV validation. | Yes |
Microsoft.Network/dnsZones/TXT/delete |
Remove TXT records after DCV is complete. | Yes |
Private hosted zones
Grant the following additional permissions
when AppViewX manages private Azure DNS zones
(Microsoft.Network/privateDnsZones). These are required only if your
deployment uses private DNS zones.
| Azure resource action | Purpose | Required |
|---|---|---|
Microsoft.Network/privateDnsZones/read |
Discover and list private DNS zones. | If applicable |
Microsoft.Network/privateDnsZones/recordsets/read |
Enumerate all record sets within a private DNS zone. | If applicable |
Microsoft.Network/privateDnsZones/CNAME/read |
Read existing CNAME record sets in a private DNS zone. | If applicable |
Microsoft.Network/privateDnsZones/CNAME/write |
Create or update CNAME records for DCV in private zones. | If applicable |
Microsoft.Network/privateDnsZones/CNAME/delete |
Remove CNAME records after DCV is complete in private zones. | If applicable |
Microsoft.Network/privateDnsZones/TXT/read |
Read existing TXT record sets in a private DNS zone. | If applicable |
Microsoft.Network/privateDnsZones/TXT/write |
Create or update TXT records for DCV in private zones. | If applicable |
Microsoft.Network/privateDnsZones/TXT/delete |
Remove TXT records after DCV is complete in private zones. | If applicable |
Network Connectivity
https://management.azure.comAzure Resource Manager API for DNS management.https://login.microsoftonline.comMicrosoft identity platform for OAuth 2.0 token acquisition.
If your AppViewX deployment is behind a firewall or proxy, ensure that outbound HTTPS access to both endpoints is permitted.
Locate the Azure Subscription ID
- Sign in to the Azure portal.
- Go to Subscriptions.
- Copy the Subscription ID for the subscription that contains your DNS zones.
Configuring Azure DNS
- On the Select Vendor page, select Azure.
-
On the Vendor Configuration page, under
General, enter or select the required information.
The following table describes the fields in this section:
Field Description *Name Enter a unique name to identify the vendor account that you are configuring. Description Enter a description for this vendor configuration. This field is optional. Data center Select a data center from the dropdown list. *: Mandatory fields -
Under Credentials, enter or select the required information.
The following table describes the fields in this section:
Field Description Auth Type Displays OAuth 2.0 as the authentication method selected by default for Azure DNS. *URL Enter the Azure Resource Manager API endpoint. This field is pre-populated with the default value. Default:
https://management.azure.com*Client ID Enter the Application (client) ID of the service principal registered in Microsoft Entra ID for AppViewX integration. *Client Secret Enter the client secret value generated for the service principal in Microsoft Entra ID. Store this value securely and rotate it per your organizational policy. *Access Token URL Enter the OAuth 2.0 token endpoint for your Microsoft Entra tenant. Format:
https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token*Grant Type Specifies the OAuth 2.0 authorization flow. Client Credentials is selected by default and is required for Azure DNS integration. Scope Defines the access scope for the OAuth 2.0 token request. This field is pre-populated with the default Azure Resource Manager scope. Default:
https://management.azure.com/.default*Subscription ID Enter the Azure Subscription ID that contains the DNS zones AppViewX will manage. *: Mandatory fields - Turn on Use Proxy for the vendor.
- Turn on Config sync to enable vendor parsing.
- Under Configurations, turn off the Enable Advanced Config toggle.
-
Select Finish.
A Vendor configuration saved successfully confirmation message appears.
Validating the Vendor Configuration
- On the Integration Hub page, locate the configured vendor tile.
- Confirm that a green check mark (✔) appears on the tile. This indicates the vendor is active and reachable.
- Select the View status icon on the tile to open the Vendor Status Log dialog for the vendor.
- Verify that the Authentication entry shows a Success status with a recent timestamp.
