Publish a TXT record requested by a service to verify control of your domain. PD Azure DNS writes the value to the zone; the requesting service decides when verification succeeds.

Check the current request

Keep the service’s requested type, full hostname and latest value. A root-domain record differs from one under a verification label. Avoid accidentally repeating the zone name in the record name field.

Open the zone’s Records page through Azure DNS → Zones, or use the enabled DNS Manager navigation link or Manage DNS on a linked domain/service. Check the resource group and authoritative nameservers so you publish to the zone that visitors and verification services actually query.

Enter the TXT value

1. Search for existing TXT values at the intended name.
2. Select TXT in the editor.
3. Enter the requested name, TTL and complete content.
4. Save without removing unrelated SPF or verification values.
5. Reload and compare the saved name/value with the latest request.
6. Verify authoritative DNS, then run the requesting service’s check.

Azure can hold several TXT values in the same name/type record set; they share a TTL. Adding one requested value is not a reason to replace every other value. Preserve the full content of a long verification string rather than truncating it to fit a visual row.

Separate save and visibility failures

A save refusal can concern policy, quota, a zone lock or Azure authorisation. A saved value that the service cannot find can concern the wrong zone, a repeated hostname, cached answers or a newer request issued by that service.

Do not recreate the zone or remove working mail records to clear one verification warning. Keep account-specific strings out of public diagnostic screenshots where they are not needed. Follow the requesting service’s retention instructions after verification instead of automatically deleting the record. See the zone-placement guide if the expected zone is missing.

See the PD Azure DNS WHMCS guide for related tasks, or explore the module.