Set Azure DNS client zone and record allowances in WHMCS
Use the module’s Packages area to connect a DNS allowance to the WHMCS products you offer. These limits control client DNS management, while Azure’s subscription and provider quotas remain separate.
Define the intended allowance
- Open Azure DNS → Packages and choose Add package.
- Set a recognisable name and zone allowance.
- Review records-per-zone and per-type rules offered by the form.
- Save and link the intended WHMCS products using the package’s picker.
- Enable the allowance and check an applicable active service and zone owner.
Link the actual products/packages, rather than assuming a whole product group inherits the allowance automatically. Read zero/unlimited settings carefully. A default record TTL pre-fills the editor; it is not an instruction to rewrite existing Azure record sets.
Check the effective entitlement
The released logic considers applicable enabled packages behind active services. Finite allowances use the largest relevant allowance, not a sum of every service’s quota. An applicable unlimited allowance removes that finite cap.
Check that the service is active, the configured package is linked, and the zone belongs to the intended client. An unowned zone is not a reliable test that customer enforcement works.
Diagnose the actual refusal
Compare module record counts and allowance with Azure’s separate quota. Import checks the planned missing records against the owning customer’s allowance before writing; a later provider refusal is a separate failure. A zone lock, content rule, resource scope or Azure permission can refuse a change even where a customer still has count allowance.
Do not delete working records simply to clear a cap warning. Review whether the saved DNS tier matches the service being supplied, then make the intended setting correction. Disabling an allowance is not a request to delete provider DNS.
For visibility problems, use the binding/access guide. For zones missing at the provider connection, use the resource-group checks. Keep the relevant settings and exact redacted error for support without exporting unrelated client data.
See the PD Azure DNS WHMCS guide for related tasks, or explore the module.