Why BizTalk is a separate licensing budget
Moving from VMware to Proxmox cuts virtualization cost — but BizTalk Server doesn't leave the bill. It's EDI/B2B/ESB integration middleware that runs only on Windows Server and needs SQL Server for configuration, MessageBox queues and tracking data. Each component has its own per-core licensing — and on Proxmox VE you count physical host cores, not just the BizTalk VM's vCPU.
+ SQL Server
physical cores
lower license TCO
IT decision-makers often see "one BizTalk app" in inventory and budget from a single Microsoft price line. In practice a license audit covers the entire stack — and on a shared, dense Proxmox node the cost can be many times what vCPU-based intuition suggests.
BizTalk Server — per-core model and editions
BizTalk Server 2020 (the latest on-premises edition) is licensed only under a per-core model — there are no per-user or per-device licenses. Licenses are sold in 2-core packs, with a minimum of 4 cores per physical processor or per virtual machine (depending on the licensing option chosen).
| Edition | Use profile | Key differences |
|---|---|---|
| Standard | moderate volume, smaller deployment scale | one BizTalk instance on the licensed OSE (physical or VM) |
| Enterprise | high volume, HA, multiple instances | multiple instances on the host; with SA — unlimited virtualization |
| Branch | hub-and-spoke, branch offices | topology restrictions; cheaper, narrow use case |
Two main ways to license BizTalk on Proxmox:
| Model | What you license | When it makes sense |
|---|---|---|
| Per physical core (host) | all physical server cores | Enterprise + SA: unlimited BizTalk VMs on the host; Standard: one instance |
| Per virtual OSE (VM) | the VM's vCPU (min. 4 cores per VM) | several BizTalk VMs on a dense node — requires SA (same rule from SQL Server 2022 onward) |
No "cheaper" per-user license: BizTalk has no integration CALs in the Windows sense. All cost sits in cores — similar to SQL Server Enterprise, but without Azure PAYG as a simple alternative.
Enterprise is roughly 4–4.5× more expensive than Standard per core — worth it for BizTalk clusters, multiple instances and HA requirements. Standard is enough for a single, moderate installation on a dedicated node.
Windows Server and SQL Server in the BizTalk stack
BizTalk Server is a Windows application — every instance needs Windows Server as the guest OS. MessageBox, Management, Tracking Store and other SQL catalogs are a separate layer: usually SQL Server Standard or Enterprise (often on a separate VM or Always On cluster).
- Windows Server — per-core license from physical host cores (Standard: 2 VMs; Datacenter: unlimited) or per-VM with Software Assurance. Details: Windows Server licensing.
- SQL Server — separate per-core licenses for the instance serving MessageBox; with several databases on one host you license the whole SQL server. Details: Oracle & SQL Server licensing.
- Host Integration Server — included in BizTalk 2020 license (not a separate line item in a typical deployment).
TCO example — dedicated 16-core node (EPYC 9175F), per-host model. BizTalk Standard alone (16 cores): 8 packs × $5,070 ≈ $40,560. Plus Windows Server Datacenter (16 cores): ~$6,771 + SQL Server Standard (16 cores): ~$3,717. Roughly ~$51,000 (~204,000 zł) in perpetual licenses alone — without SA. Small BizTalk VM (4–8 vCPU)? Usually cheaper with per-VM + SA — see HA and Software Assurance.
BizTalk licensing architecture on Proxmox should be planned together with Windows and SQL — optimizing one layer without the others rarely delivers real savings.
The dense-host trap on Proxmox
If the BizTalk VM (or SQL for MessageBox) sits on a shared node with hundreds of other machines, under the classic per-core model you must cover all physical host cores — just like Windows Server and SQL Server Enterprise.
Density trap: BizTalk on 4 vCPU running on a host with EPYC 9755 (128 cores) under the per-host model requires BizTalk licenses for 128 cores — not 4. Same mechanism as SQL Server and Windows.
| Scenario | Cores to license (BizTalk Standard) | Approx. BizTalk license cost |
|---|---|---|
| Dedicated EPYC 9175F node (16 cores), per-host model | 16 | ~$40,560 (~162,000 zł) |
| Small VM (8 vCPU) on any host, per-VM + SA | 8 (VM only) | ~$20,280 (~81,000 zł) + SA — cheaper than a full 16-core host |
| Small VM (4 vCPU, min. 4 cores), per-VM + SA | 4 | ~$10,140 (~40,500 zł) + SA |
| Shared EPYC 9755 host (128 cores), per-host | 128 | ~$324,480 (~1.3M zł) |
If BizTalk is a small virtual machine (typically 4–8 vCPU), Software Assurance and per-VM licensing is usually the best fit — you pay for the VM's cores (minimum 4), not all physical host cores. On a 16-core host that's up to half the BizTalk license cost; on a dense node the savings are many times larger. We recommend a dedicated EPYC 9175F node when you need per-core performance, isolation or multiple instances/SQL on one server under the per-host model — not as the only way to cut license cost.
HA, Software Assurance and license mobility
A Proxmox cluster with live migration and automatic failover means the BizTalk VM can start on another node. Without the right licensing rights, each such node must be fully licensed — doubled (or multiplied) like Windows and SQL.
Software Assurance (SA) for BizTalk provides among other things:
- License Mobility Across Server Farms — move licenses between servers in a farm without the 90-day limit (critical for HA).
- Per-VM model — license the VM's vCPU (min. 4 cores) instead of all cores on a dense host.
- Unlimited Virtualization (Enterprise + SA) — after fully licensing the host's physical cores with Enterprise you can run any number of BizTalk instances in VMs on that server.
- Upgrade rights — newer versions while SA is active (BizTalk 2020 is the last on-prem edition; SA maintains compliance for coexisting Windows/SQL components).
HA without SA: assigning core licenses to a host can legally be changed only once every 90 days — that conflicts with everyday Proxmox HA failover. Options: SA + License Mobility, strict node-affinity (BizTalk only on fully licensed nodes) or full licensing of every HA node.
Recommendation for a small BizTalk VM: if the machine typically has 4–8 vCPU (even on a dedicated 16-core host), choose per-VM licensing with Software Assurance — it's cheaper than covering all 16 physical host cores.
Example — BizTalk Standard, 16-core host vs small VM:
- Whole host (16 cores): 8 × $5,070 = $40,560 (perpetual)
- 8 vCPU VM + SA: 4 × $5,070 = $20,280 + ~$5,070/year SA — even after ~4 years of SA still cheaper or comparable, plus license mobility
- 4 vCPU VM (min. 4 cores) + SA: 2 × $5,070 = $10,140 + ~$2,535/year SA — 4× less than licensing the whole host
Apply the same logic to Windows Server (per-VM with SA, min. 8 cores per VM) and SQL Server for MessageBox — with a small VM the SQL layer is also counted from the VM's vCPU, not the whole host. Details: Windows Server, SQL Server.
SA for Microsoft server products costs roughly ~25% of license price per year. With a small VM and licensing below 16 cores the annual SA fee is proportionally low — and you avoid the one-time "tax" on all server cores. With BizTalk Enterprise on a full 16-core host SA is tens of thousands of USD per year — then compare the per-VM model too. In TCO budget for license + 3–5 years of SA together with Windows and SQL.
BizTalk Server 2020 catalog prices
Below are indicative Microsoft catalog prices (Open / ERP channel, net, without SA) for 2-core packs. BizTalk 2020 is the current on-premises edition; Microsoft has not announced a successor — plan long-term with Windows Server and SQL Server in the same support lifecycle.
| Item (2-core pack) | Catalog price (USD) | Approx. (PLN) |
|---|---|---|
| BizTalk Server 2020 Standard | $5,070 | ~20,300 zł |
| BizTalk Server 2020 Enterprise | $22,114 | ~88,500 zł |
| BizTalk Server 2020 Branch | ~$1,264 | ~5,050 zł |
Example — 16-core host, BizTalk Enterprise. Minimum 4 cores per CPU met; you need 8 two-core packs: 8 × $22,114 = $176,912 (~707,000 zł) in BizTalk licenses alone. Standard on the same host: $40,560 (~162,000 zł). Add Windows, SQL and possibly SA (~25%/year per layer).
Prices are indicative, converted at ~4 zł/USD. Actual price depends on EA/MPSA/Open agreement, discounts and exchange rate. B2B adapters, mapping development and maintenance are separate project costs — not included in BizTalk Server list price.
AMD EPYC 9175F recommendation and VMware migration
Proxmox Migracje recommendation — small BizTalk VM: for a typical 4–8 vCPU machine choose Software Assurance + per-VM licensing (BizTalk, Windows and SQL each per VM). Below 16 cores this is cheaper than licensing the whole host — including on a dedicated 16-core node.
Recommendation — performance and isolation: when BizTalk needs high per-core power, multiple instances under the per-host model or dedicated SQL on the same server, we recommend AMD EPYC 9175F — 16 high-frequency cores (up to 5.4 GHz boost) instead of a dense 128-core host shared with hundreds of VMs.
- Small BizTalk VM (4–8 vCPU) → SA + per-VM on the machine's cores (min. 4 for BizTalk, min. 8 for Windows) — usually cheaper than licensing a full 16-core host; essential on a shared Proxmox node.
- Dedicated integration node — EPYC 9175F when you license per-host (many instances, SQL on the same server) or need isolation; rest of cluster on dense EPYC 9755.
- 16 cores instead of 128 — under the per-host model, savings on BizTalk Standard of roughly ~$284,000 vs a mega-host (indicative, excluding Windows/SQL).
- BizTalk HA — SA + License Mobility or strict node-affinity to fully licensed nodes.
- Migration from VMware — BizTalk, Windows and SQL licenses are independent of the hypervisor; on the same hardware they carry over to Proxmox. Moving to new, denser CPUs requires recalculating cores from scratch.
Related articles: Windows Server licensing, Oracle & SQL Server licensing, AMD EPYC 9175F for databases, HA affinity rules.
Microsoft licensing can be complex — confirm your specific BizTalk scenario (number of host instances, SQL cluster, HA requirements) with a licensing partner. The above are general rules and indicative prices, not legal advice or an offer.
We'll plan BizTalk licensing on Proxmox
We'll calculate the BizTalk + Windows + SQL stack, design dedicated AMD EPYC 9175F nodes and migrate from VMware while staying compliant.
⚡ Free consultation → AMD EPYC 9175F