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 product

1. In System Settings → Products/Services, create the intended product in its product group.
2. Choose Other Products/Services as the product type, then select PD Azure VM in Module Settings.
3. Select the server group containing the intended Azure connection. Confirm the subscription behind that group rather than relying on the group’s name alone.
4. Set the intended region, VM size, operating-system image and OS disk size. Review the choices together: a size being listed does not prove availability or quota in every subscription and region.
5. Review Automatically setup the product and choose the trigger that matches your order process. If the product should provision after payment, ensure that is the option you select; do not assume the creation link configured it for you.
6. Save the product before generating customer checkout options.

Review the customer offering

Use PD Modules → Azure VM → Products to find the saved product. Generated checkout dimensions are separate from the Module Settings defaults. Review their values, visibility and your own pricing before making the offering available.

Review the client-area feature switches as part of the product design. Additional data disks create separately chargeable Azure resources, so do not enable Volumes without deciding how you will offer them. The in-browser console also has a module-wide switch; turning on only a product’s console control is not sufficient.

Verify before accepting orders

Preview the intended order form and confirm the values customers can select, the product defaults and pricing. A saved product, Ready label or successful connection check is not proof that a VM has been provisioned.

Use your normal authorised provisioning test when the offering is ready. Creating a real service creates Azure resources and can incur provider charges. Check the module’s service state and Activity, the returned connection details and the provider outcome. Keep the normal automation cron running for subsequent operations. If a service appears active without a VM, investigate the selected module, account and setup trigger before repeating a create action.

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

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