Connect the host’s Azure app credentials before creating a PD Azure Blob Storage plan. These credentials manage provisioning; they are separate from the container-scoped credential a customer receives for a provisioned service.

Prepare the four values

Have the Azure subscription administrator prepare the intended app registration and access for this module. Obtain tenant ID, client ID, client secret and subscription ID through your secure credential process.

The app registration supplies the tenant and client IDs. Copy a newly created secret’s Value, not its secret ID. See Microsoft’s app credential instructions.

The module’s documented provisioning setup uses Contributor on the intended subscription. That is broad resource-management access; confirm the intended subscription and identity with its administrator. Microsoft describes the role here. Do not substitute a similarly named app or assume a read-only role can provision storage.

Enter the connection in Blesta

Install and enable PD Azure Blob Storage through PD Modules, then allow the administrator or staff group that needs it to open the panel. Connect your PD account first when activating PD Modules; a licence key is the alternative activation route.

Open Settings → Company → Modules, find PD Azure Blob Storage under Installed, then choose Manage. Add an Account name and paste the JSON into Service principal credentials (JSON). Leave Azure endpoint (optional) blank. Save the account. When editing an existing account, a blank credential box keeps its saved value.

Enter the credential as one JSON object containing tenant_id, client_id, client_secret and subscription_id, with each value in double quotes. Keep the object in the credential field; do not paste it into a hostname, a support conversation or a public example.

Check what the connection test proves

In PD Modules → PD Azure Blob Storage → Settings, use Test Connection and read its result. It checks sign-in, whether Microsoft.Storage is registered, and whether storage accounts can be listed. It does not create a storage account or prove permission for every provisioning operation.

With several configured accounts, verify the intended one rather than treating a panel-wide success as proof they all work. The released panel test selects the first active connection; check the connection assigned to the actual plan and use its supported account-specific test where offered.

If the test fails

Check for a secret Value/ID mix-up, expiry, a mismatched tenant or client ID, and the intended subscription. Ask the Azure administrator to review the named registration or permission error. Do not repeatedly replace a valid secret or broaden unrelated access as a guess.

Retain the original connection label, attempt time and redacted error while your hosting team and Azure administrator establish which check failed. Keep the JSON credential, subscription identifiers and customer storage links out of shared screenshots.

See the PD Azure Blob Storage Blesta guide for related tasks, or explore PD Azure Blob Storage.