Use the module’s Products page to build customer-selectable region, server-plan and operating-system choices for an existing PD Azure VM product. Review the generated group before making it available to customers.

Prepare the product

Save the product with PD Azure VM, the intended server group and its default region, size, image and disk settings. Confirm that the Azure connection belongs to the subscription you intend to use. Keep the offering out of sale while checking a new option group.

The catalogue can use cached or shipped choices when the live lookup is unavailable or supplies no usable choices. With several Azure connections, its lookup can use the first available account rather than the product’s intended server group. Listed choices therefore are not a deployment guarantee. Confirm region, family eligibility and quota for the intended subscription before offering them.

Generate and price the choices

1. Open PD Modules → Azure VM → Products and find the intended product.
2. Choose Generate options if it has no generated group. If the action says Rebuild from catalog, read the replacement warning before proceeding.
3. Review the generated dimensions. The released generator includes Region, Server plan, Operating system, Disk size and Snapshots you can keep; not every dimension is necessarily shown at checkout.
4. Use Open Options or the product’s Configurable Options tab to review the group linked to this product and set your own prices. Inspect the billing cycles and currencies you offer rather than assuming the defaults are commercially ready.
5. Preview the intended order form and check the selected values, displayed choices and resulting price before publishing the offering.

Generating choices does not import your Azure costs, choose your margins or enable automatic product setup. Review those decisions separately.

Change visibility without rebuilding

Expand the product’s available Customer-selectable dimensions controls and use Save visibility for the visibility changes you intend. This path changes visibility rather than rebuilding prices. Check the actual option group afterwards: a success message alone is not proof that the expected group was found and changed.

Read every generated option, including snapshot allowance, before offering it. Do not assume the dimension picker exposes a control for every option in the group. Hidden choices and product defaults also need checking against the values a service will receive.

Treat a rebuild as a replacement

Rebuild from catalog replaces the generated option set and its pricing with the generator’s defaults. Record and review your customised choices and prices before doing this to an existing offering. It is not a routine refresh that preserves every edit.

If options appear missing, check which group is linked to the product and whether the last operation completed before generating another group. For an uncertain result, inspect the saved group and the last operation result before making another change. Do not repeatedly rebuild while that outcome remains unclear. This task does not require an order or a live Azure VM.

Do not send provider credentials or customer billing data.

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