Onboarding Azure DNS

Overview

Before you configure the Azure DNS integration in AppViewX, ensure that a service principal is registered in Microsoft Entra ID (formerly Azure Active Directory) with the correct role assignments. AppViewX uses OAuth 2.0 client credentials to authenticate against the Azure Resource Manager API and perform DNS record management including TXT and CNAME records for Domain Control Validation (DCV) or ACME DNS-01 challenge validation, across both public and private DNS zones.
Azure DNS is a managed DNS hosting service in Microsoft Azure. In AppViewX, onboarding Azure DNS enables controlled access to DNS zones and records through Azure APIs.
  • 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

Before you configure the Azure DNS integration in AppViewX, ensure the following prerequisites are met in your Azure subscription.
  • 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

Gather the following information before you begin configuring Azure DNS in AppViewX.
Table 1. Information required for Azure DNS 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

AppViewX uses a service principal to authenticate against the Azure Resource Manager API. Complete the following steps to register the application and generate client credentials.
  1. Sign in to the Azure portal.
  2. Go to Microsoft Entra ID > App registrations > New registration.
  3. Enter a name for the application, such as AppViewX-DNS, and select the appropriate supported account type for your organization.
  4. Select Register.
  5. 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.
  6. Go to Certificates & secrets > Client secrets > New client secret.
  7. Enter a description, set an expiry period, and select Add.
  8. Copy the secret Value immediately and store it securely.
Important: The client secret value is displayed only once after creation. Ensure you copy and store it before leaving the page.

Construct the Access Token URL

The Access Token URL is the OAuth 2.0 token endpoint for your Microsoft Entra tenant. Use the following pattern, substituting your Directory (tenant) ID:
https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token
Example:
https://login.microsoftonline.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/oauth2/v2.0/token

Assign the Required Role to the Service Principal

The registered application must have the DNS Zone Contributor role (or an equivalent custom role) assigned on the Azure DNS zone or the resource group that contains it. This role allows AppViewX to:
  • Discover and list DNS zones.
  • Retrieve DNS record sets.
  • Create, update, and delete CNAME and TXT records for DCV.

To assign the role:

  1. In the Azure portal, go to the DNS zone or resource group that AppViewX will manage.
  2. Select Access control (IAM) > Add > Add role assignment.
  3. Under Role, search for and select DNS Zone Contributor.
  4. Under Members, select the registered application (service principal).
  5. Select Review + assign.
Note: During DNS automation, AppViewX retrieves the DNS zones list and validates that the required zones exist before it creates DNS records.
Important: For production deployments, use a dedicated service principal instead of a shared administrator account. Scope access to only the zones or resource groups required by AppViewX.

Minimum Required Azure RBAC Permissions

The permissions required depend on whether AppViewX manages public DNS zones, private DNS zones, or both. AppViewX supports both CNAME and TXT record types for DCV validation grant the permissions for the record type your certificate authority requires. If your deployment uses private DNS zones, grant the private zone permissions as well.
Important: Avoid assigning broad subscription-wide privileges unless there is a justified operational requirement. Least-privilege access reduces security risk and configuration drift. Assign the role at the DNS zone or resource group scope, not the subscription scope.

Public hosted zones

Grant the following permissions when AppViewX manages public Azure DNS zones (Microsoft.Network/dnsZones).

Table 2. Required permissions for public hosted zones
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.

Table 3. Required permissions for private hosted zones (if applicable)
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
Note: The Private DNS Zone Contributor built-in role grants the required permissions for private zones. Assign it on the private DNS zone or its resource group scope, in addition to the DNS Zone Contributor role for public zones, if both zone types are in use.

Network Connectivity

Ensure that AppViewX can reach the following Azure endpoints over HTTPS (port 443):
  • https://management.azure.com Azure Resource Manager API for DNS management.
  • https://login.microsoftonline.com Microsoft 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

The Subscription ID identifies the Azure subscription that contains the DNS zones AppViewX will manage. To find the Subscription ID:
  1. Sign in to the Azure portal.
  2. Go to Subscriptions.
  3. Copy the Subscription ID for the subscription that contains your DNS zones.

Configuring Azure DNS

  1. Go to Menu > CERT+ > ADMINISTRATION > DCV Management > Manage DDI services > Add new vendor.
    The Select Vendor page appears.
  2. On the Select Vendor page, select Azure.
  3. 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
  4. 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
  5. Turn on Use Proxy for the vendor.
  6. Turn on Config sync to enable vendor parsing.
  7. Under Configurations, turn off the Enable Advanced Config toggle.
  8. Select Finish.
    A Vendor configuration saved successfully confirmation message appears.

Validating the Vendor Configuration

  1. On the Integration Hub page, locate the configured vendor tile.
  2. Confirm that a green check mark (✔) appears on the tile. This indicates the vendor is active and reachable.
  3. Select the View status icon on the tile to open the Vendor Status Log dialog for the vendor.
  4. Verify that the Authentication entry shows a Success status with a recent timestamp.