Per core licensing turns hardware into a license count, and the counting rules are where audit exposure hides. Get the core math wrong and the gap shows up in the Effective License Position with a 125 percent price attached.
Why per core matters in an audit
Several of Microsoft's most audited products, including Windows Server and SQL Server, are licensed by the physical core. That means your license requirement is driven by the hardware underneath, not by the number of installs you remember deploying. In an audit, the auditor counts cores from the actual configuration and from telemetry, then compares that count to your entitlement. If your records were built on an assumption about cores rather than the real figure, the gap appears in the Effective License Position, the reconciliation of deployment against entitlement.
How core counting works
The core model has a few rules that drive most of the exposure. Licensing is per physical core on the server, subject to a minimum per processor and a minimum per server. Cores are usually licensed in packs, and partial packs round up. The practical effect is that a single dense server can require far more licenses than an intuitive headcount suggests, and a fleet of them multiplies the effect.
- Count every physical core on each licensed processor, not the sockets
- Apply the minimum cores per processor and the minimum cores per server
- License in core packs and round partial packs up to the next pack
- Reconcile to the real hardware configuration, not to a procurement assumption
A worked example
Consider two servers, each with two processors of sixteen cores, so thirty two cores per server and sixty four across the pair. Suppose the estate was licensed on an older assumption of two licenses per server, treating the unit as the box rather than the cores. The real requirement is the full core count. The figures below are indicative, but the shape is what an audit exposes.
| Item | Assumed | Actual under per core |
|---|---|---|
| Servers | 2 | 2 |
| Cores counted | Not counted | 64 physical cores |
| License basis | Per server | Per core, packs rounded up |
| Audit result | Apparent compliance | Shortfall priced at 125 percent |
Where the costly mistakes hide
The expensive errors are rarely dramatic. They are quiet assumptions that never got revisited: licensing the socket instead of the core, forgetting the per processor minimum, missing a hardware refresh that added cores, or carrying a count from a previous environment into a denser one. Because the product runs fine regardless of the license math, nothing surfaces the gap until the auditor counts. By then it is exposure, not a planning question.
The next step
Per core licensing rewards the organization that counts honestly before Microsoft does. Start with our pillar, the Effective License Position Guide, then read virtualization rights and license counting and bring your own license rules. Build your core count from the real hardware, and the per core trap closes before it can open.
When the exposure is real, we take over the process through our Microsoft audit defense engagement.
Know your core count first
We sit between you and Microsoft and its appointed auditor. Fixed Fee from $18,000 or Gainshare, both backed by our guarantee that we reduce your exposure or we reimburse our service fee.
Download guide