Create the customer offering after preparing its Azure connection. The saved region, VM size, image and disk settings determine what the module will request when the service is intentionally provisioned.

Create the package

1. Open Packages → Packages → Add Package.
2. Choose PD Azure VM as the module and select the intended saved Azure account.
3. Review the module fields for region, VM size, operating-system image and OS disk size. Select valid offered choices and confirm the intended subscription and region can deploy the size.
4. Review the client controls the package will expose and set the package’s terms and your own pricing.
5. Save the package and place it in the intended package group. Add that group to the appropriate order form under Packages → Order Forms when the offering is ready.

Start with the package’s fixed settings

The reviewed release uses the package’s own module settings for its defaults. Its older configurable-option generation path does not provide the newer native Blesta generation workflow described in some module documentation. Do not follow a Generate options procedure merely because a newer guide mentions it.

A fixed offering can use a separate package for each intended combination. If you want customer-selectable dimensions, obtain guidance for your installed build before creating manual options or copying another platform’s option names. A generic No customer options status describes the absence of attached checkout options; it is not a test of whether the fixed package can provision.

Review activation and client controls

Check the order form and package settings that govern activation. Blesta’s Provision Paid Pending Services automation handles eligible paid pending services; a package configured for manual activation needs the intended staff action instead. Saving the package or taking an order is not itself proof that a VM exists.

Review the client-area controls before exposing the package. Additional data disks create separately chargeable provider resources. The in-browser console needs both its package feature setting and the module-wide console switch. Do not assume every displayed feature is included in the price you set.

Use your normal authorised provisioning test when ready. A real service creates Azure resources and can incur provider charges. Inspect the module’s service state and Activity, returned connection details and provider outcome, then keep the normal cron running for subsequent operations. Resolve an uncertain create result before another activation attempt.

Do not send credentials, private SSH keys or a full customer record.

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