Bind the intended Azure DNS zone to its customer so routine record management can happen in the Blesta portal. Customers receive access to their own zone, not your Azure app credential or subscription administration.

Check ownership before binding

1. Open Azure DNS → Zones and identify the provider/domain.
2. Review the existing records and the intended customer’s domain or service.
3. Open the zone menu and choose Assign to client.
4. Select the correct account and optional related domain/service.
5. Save and verify the resulting client and binding information.

Check the zone’s Azure subscription/group and public delegation separately. A same-named zone belonging to a different connection should not be assigned just to make a portal link appear.

Direct the customer to DNS

The customer can use My Tools in the client portal, then the DNS manager. Where the module’s navigation link is enabled, it can also appear directly in the client menu using the label configured by your hosting team. Check that saved choice rather than assuming every portal uses identical menu wording. The record editor adapts to the selected type, with import/export, backups or signing controls available according to provider capability and saved access settings.

The customer’s view should contain only the zones assigned to that account. Do not distribute provider credentials as a workaround for a missing client link.

Control editing deliberately

Use Lock when customer edits need to pause and Unlock when they should resume; administrators retain their own controls. The domain-only editing setting separately chooses full editing, view-only access or hidden record pages for domains without a hosting service here.

Signing and other write controls can be restricted by the zone’s editing state. A customer being able to view records does not mean every save is authorised: quotas, content policy and provider permissions also matter.

If a zone is missing, review ownership, binding, active service and navigation before changing provider settings. Removing a binding withdraws portal management without deleting Azure DNS data. Keep destructive Delete zone separate and check it carefully before using it. See the allowance guide for count-related refusals.

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