An order, paid invoice or active billing record does not by itself prove that Azure storage is ready. Check the billing trigger, assigned connection and module operation before repeating provisioning.

Check whether provisioning was requested

Customer orders begin as pending services. Check invoice payment, Blesta’s Provision Paid Pending Services automation task, the relevant client-group provisioning setting and the normal cron. Staff activation uses Use module when an actual provider operation is intended. An unpaid pending service is not evidence of an Azure failure.

Do not activate several copies of the same request to see which one succeeds. If the service is intended to represent storage already managed elsewhere, confirm that intention before enabling a provider operation.

Check the storage operation

Open PD Modules → PD Azure Blob Storage → Clients & Storage and find the intended service. Review its storage state, account/container details and Activity messages.

A billing-platform Active status and the module’s storage state answer different questions. Storage creation and verification may still be incomplete, or the module may hold a failure that needs attention. Read the actual result rather than interpreting an empty usage figure as proof that no account exists.

Check the assigned Azure connection

Confirm the account assigned to the product or package, not merely that some Azure account is saved. Test Connection checks read access and registration; it does not prove the permission to create resource groups, storage accounts, containers or credentials.

For a permission error, ask the Azure administrator to review the named operation and intended subscription. For authentication errors, check the prepared tenant/client values and secret status without sending the credential to support. The panel’s released connection test selects its first active account, so a success can refer to a different account from the one assigned to this service.

Check location and provider restrictions

Review the selected region, saved plan defaults and any customer option. Ask the Azure administrator to investigate a named policy, provider-registration, naming or capacity refusal. A different storage service’s setup is not evidence that this subscription can perform the requested operation.

Reconcile before retrying

An interrupted operation can leave a tracked service or provider resources. Inspect the current service and error before pressing Create or activating again. Do not delete a billing record, storage account or resource group as a repair shortcut.

Retain the original service reference, selected connection/plan, intended region, attempt time and redacted operation result while your hosting team checks the actual creation stage. Keep customer files, app secrets and live access links out of shared evidence.

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