Create a PD Azure Blob Storage plan after connecting the Azure account. Review the fixed plan defaults before accepting orders; saving a billing plan does not itself provision storage.

Create the billing plan

Open Packages → Packages → Add Package and choose PD Azure Blob Storage as the module. Select the intended Azure account or module row, then review the module fields on the package.

Review the package name, pricing and package group. Add the group to the intended order form under Packages → Order Forms when the plan is ready. Paid pending services rely on Blesta’s provisioning automation and cron; a saved package alone creates no Azure storage.

Describe what the customer receives

Review Quota mode, Default quota (GB), Default Region and Default versioning. The default quota is used when no customer-selected Storage Quota option supplies a value. Blank or zero means unlimited, so enter a deliberate quota when the plan should have one.

Soft quota mode records usage without pausing uploads at the quota. Hard mode can pause new uploads when collected usage reaches the quota. This is based on usage collection, not an instantaneous byte counter at the moment a customer uploads a file.

Each service is provisioned with a dedicated storage account and one container. Keep Containers per service at its supported fixed value of one. The generic Client: Container management label is not a promise that this provider supports extra containers.

Set Default Region for new storage and review Default versioning. A customer-selected option can override a default at provisioning time when that option is supported and linked to the plan. Changing the default region later does not move an existing account.

Review optional choices and controls

Begin with reviewed fixed package defaults. Do not assume that a Generate options control shown elsewhere has created working Blesta package options. Confirm the supported option workflow for the installed module before offering customer-selected dimensions; retain the package, attempted action and observed result if that workflow is unclear.

Review the optional sharing and storage-setting controls against the actual service. Confirm customer self-service separately before including it in the plan; this package setup procedure does not establish that each customer action is available.

Check the first service

Review the connection and the complete plan, then use your normal controlled first-provisioning process. Azure resources can incur charges; do not place a real order solely to inspect a form.

Check both the billing service status and PD Azure Blob Storage → Clients & Storage. Inspect Activity for a failed or incomplete operation before retrying. If the result is unclear, your hosting team and Azure administrator should compare the original service reference, selected plan/account and redacted error with the actual Azure resources before another attempt.

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