Connect PD Azure MySQL to the Azure subscription that will host your managed database offerings. Keep the provider connection separate from the product or package that describes what a customer receives.

Prepare the connection values

Ask the administrator responsible for Azure to prepare an approved app registration and access to the intended subscription. The module’s documented credential format uses Directory (tenant) ID, Application (client) ID, client secret Value and Subscription ID. Use the secret’s Value, not its ID. Microsoft explains where these values appear in its app credential guide.

The module documents Contributor on the intended subscription. It creates a separate resource group for each service, so access confined to one existing resource group does not match that provisioning design. Have the Azure administrator review the role and scope for the intended app rather than broadening unrelated identities.

Prepare one valid JSON object with all four keys: tenant_id, client_id, client_secret and subscription_id. Keep the completed object private. Optionally include secret_expires in YYYY-MM-DD form to record the secret’s expiry date for the module’s countdown notice. This date does not renew the credential.

Save the provider account

1. Open Settings → Company → Modules.
2. Find PD Azure MySQL under the installed modules and choose Manage.
3. Add a recognisable account name and paste the prepared credential JSON into the credential field. Save the account.
4. Open PD Modules → AZ MySQL and use Test Connection after checking the account-selection limitation below.

Blesta calls the saved account a module row. Choose that account on the intended package. When editing the account later, leaving the credential field blank keeps the stored value.

Check which account was tested

The module-level connection check uses the first available account for this module. With several saved accounts, do not assume it checks the account selected by the last product, package or service you viewed. Confirm the intended association through your normal administration process. Do not disable a working connection simply to force the selection.

Test Connection checks sign-in, the Microsoft.DBforMySQL registration and a subscription read. It does not create a database or prove the write permissions needed for provisioning. Review the actual role assignment separately before accepting orders.

If the credential format is refused, recheck all four keys and valid JSON. If authentication fails, check the tenant/client pair and secret Value. Do not send the credential JSON, client secret or unredacted subscription details.

See the PD Azure MySQL Blesta guide for related setup, or explore PD Azure MySQL.