Set the storage region before the service is provisioned. PD Azure Blob Storage uses the selected region when creating the service’s Azure storage account; changing a plan default later does not relocate existing data.

Set the plan default

Open the package under Packages → Packages and review its Module settings. Confirm that PD Azure Blob Storage and the intended Azure connection are selected.

Find Default Region and choose the intended location. Save the plan, reopen it and verify the selected value. The module’s initial default is uksouth, but review it explicitly rather than relying on an untouched form.

The region list is a choice of locations, not proof that your Azure subscription can provision every listed location. If an operation is refused, ask the Azure administrator to check the selected region, subscription policies and the named provider error.

Understand which choice takes precedence

At provisioning, a supplied customer Region option takes precedence over the plan’s Default Region. If no customer choice supplies a value, the plan default is used. The module also has a fallback, but a fallback is not a substitute for deliberately saving the intended region.

For a fixed-location package, use its saved Default Region. Customer-selectable region options require a separately confirmed supported workflow; use only a confirmed Blesta option workflow.

Verify the provisioned location

On an authorised controlled provision, compare the intended choice with the storage service details in Clients & Storage and the relevant Activity result. Distinguish a configured plan from a completed storage account: a pending or failed operation has not established a ready service in the intended region.

Handle a later change

Changing Default Region affects future provisioning. It does not move a storage account that has already been created, copy its blobs, or rewrite the customer’s connection details. A plan change is not a storage migration procedure.

If the wrong region was used, your hosting team should stop further provisioning for that plan and compare the accepted choices with the actual account location through your Azure administrator. Do not terminate an existing account or repeat Create as an experiment, especially when it contains data.

Retain the original service reference, intended region, saved default or order selection and redacted error while checking placement. Do not include credentials, private files or live storage access URLs.

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