Sell managed MySQL databases on Microsoft Azure under your own brand — provisioned, billed and managed in WHMCS
Sell cloud servers on Microsoft Azure under your own brand — provisioned, billed and managed in WHMCS
Made and supported by Projektif Digital Ltd. Runs inside PD Modules, the panel every module installs into.
PD Azure VM lets a hosting company sell Microsoft Azure virtual machines as its own cloud server product. Your customer orders in your WHMCS cart, a dedicated server is built in your Azure subscription within a few minutes, and your customer manages it from your client area: a control panel in your brand that never names Azure in its own words. You set the price, Microsoft bills you the cost, and the difference is your margin.
It is built for hosts who want to offer cloud servers on Azure without building a control panel, without giving customers access to the Azure portal, and without a support ticket every time a customer needs a reboot or a firewall rule.
Sell cloud servers under your own brand. Your customers see your company, your prices and your client area. They never need an Azure login, and there are no per-server fees to us: you pay a flat module subscription and Microsoft bills your own subscription.
Every order sets itself up. The server is created while WHMCS processes the order, with the region, server plan and operating system the customer picked at checkout. Provisioning resumes from the step it reached if anything needs retrying, and an order Azure cannot fulfil fails with the reason instead of sitting half-built.
Each customer is isolated. Every service gets its own Azure resource group holding its server, disks, private network, firewall, public IP and snapshots. The module leaves the rest of your subscription alone.
Customers help themselves. Power controls, connection details, snapshots, extra disks, a firewall, SSH keys, boot diagnostics, usage graphs and an optional in-browser terminal are all on the customer's own service page. That is most of the tickets a server product normally generates.
Problems caught before they cost you. An order whose size does not fit the region's vCPU quota is refused with the exact steps to raise it, before anything is created. The cart only lets a customer combine a region and a size that Azure actually offers there, so a refusal never becomes a paid order that then fails.
Nothing left billing. Terminating a service deletes its whole resource group in one ordered operation, then verifies at Azure that nothing is left. No forgotten disks or addresses on your Azure bill.

ssh command


Every one of these is a switch on the product. Turn one off and it disappears from the customer's page, and the server refuses it too. The pages render natively on WHMCS's Six, Twenty-One and Nexus themes and are fully translatable, with wording overrides that survive updates.

PD Azure VM is one paid module with everything included: provisioning, power, snapshots, disks, firewall, boot diagnostics, metrics, upgrades and the browser console. There are no add-ons or tiers to compare. It installs into PD Modules in one click, updates itself, and uninstalls cleanly without modifying any WHMCS files.
If your subscription ever lapses, your customers are not cut off. Their servers keep running in your Azure subscription throughout, and customers can keep managing them until the subscription is suspended. New provisioning and admin configuration lock when it expires, and the browser console stops at that point. Terminations still complete, so nothing is left billing you.
Yes. You connect an Azure service-principal credential once, and every client's VM is provisioned into your Azure subscription — Microsoft bills you, you bill your client through WHMCS, and the difference is your margin.
Yes. VM sizes are read live from Azure for each region (refreshed every 12 hours, and whenever you rebuild the options); OS images come from a curated list of Microsoft's own images. A size a region does not offer is refused before anything is built.
Yes — the client area shows boot diagnostics (the boot screen and a read-only serial log), and the customer can then reboot, reinstall or restore a snapshot, without any access to your Azure subscription.
The VM is deallocated, not destroyed — a lapse never deletes data. Everything is restored once the account is brought back into good standing. Data is only ever removed on an explicit termination.
No. Size and disk upgrades apply in place with the data preserved, through WHMCS's normal Upgrade/Downgrade flow.
One paid product unlocks every feature — no add-ons or tiers to juggle. You set your own price for each VM size.
WHMCS 9 or later, on PHP 8.2 or later. It installs alongside whatever else you run — it adds its own tables and templates rather than modifying WHMCS files, so it does not collide with other vendors' modules or with a customised theme. Uninstalling removes its own tables and settings. Terminate its services and let their cleanup finish first — uninstalling also removes the record of any cleanup still in progress.
Open a ticket from your client area, or use Get help inside the PD Modules panel, which attaches a diagnostic report — you see a preview of exactly what it contains, and can exclude any part of it, before anything is sent. Support is included with an active subscription; bug reports are welcome whatever your licence state.