Rotate an Azure DNS client secret without changing zones in WHMCS
Replace the app secret used by PD Azure DNS before it expires or when a replacement is required. Creating a new secret does not itself update the module’s saved connection, and changing DNS records is not part of credential rotation.
Identify the existing connection
Open Azure DNS → Providers and review the intended provider name, subscription, tenant and application. Confirm that the Azure app you plan to change is the one this connection uses.
Check the secret’s actual expiry in Microsoft Entra. The optional expiry date stored in the module supports information shown by Test connection; do not rely on it as proof that an automatic reminder was sent or that the saved secret can never expire.
Replace in a controlled order
- In the app registration, open Certificates & secrets → New client secret.
- Set an appropriate expiry and copy the new secret’s Value privately.
- Edit the corresponding provider in Azure DNS → Providers.
- Replace the client-secret value and update the optional expiry information.
- Run Test connection, then save the provider.
- Verify the intended connection and DNS-zone reads with the replacement before retiring the old secret.
Where the old secret still works, keep the overlap until the replacement is confirmed. Do not delete another integration’s secret simply because it belongs to the same app registration; check who uses each credential.
Diagnose an expired or wrong secret
A wrong-secret response can mean the secret ID was entered instead of its Value. An application-not-found response can indicate a mismatched tenant and client ID. An authorisation refusal after sign-in can concern role scope rather than the secret itself.
If the old secret has already expired, create the replacement and update the saved provider; repeatedly retrying the expired value will not restore access. Keep keys and secret values out of support attachments. Retain the provider name, action time and redacted error if the connection checks do not resolve it.
See the PD Azure DNS WHMCS guide for related tasks, or explore the module.