Editorial photograph of a database team reviewing SQL Server license deployment records
Spoke / Microsoft Audit

SQL Server audit defense the buyer side guide.

SQL Server audits hit DBA teams unprepared more often than any other Microsoft audit. Core licensing math, virtualization, and mobility rules drive most of the exposure. This guide gives the buyer side baseline.

Contact Us Microsoft Practice
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

SQL Server audit exposure comes from per core licensing, virtualization rules, and license mobility. Most exposure is preventable with a clean inventory baseline.

Key takeaways

  • SQL Server is licensed per physical core with a four core minimum per processor.
  • Standard and Enterprise editions price differently. Enterprise is required for advanced HA and analytics features.
  • Virtualization changes the math. Without Software Assurance, every VM must be individually licensed.
  • Software Assurance unlocks license mobility, including Azure Hybrid Benefit.
  • Audit exposure is mostly a baseline problem. Estates with weak inventory pay the most.
  • Cloud migration of SQL workloads creates both opportunity and audit risk. Plan the migration with licensing in mind.

SQL Server is one of the most frequently audited Microsoft products in 2026.

The licensing model has not changed structurally in years, but the deployment patterns have shifted to virtualized and cloud workloads.

Most audit exposure traces back to the same gaps. Per core math errors, unlicensed VMs, and missing Software Assurance.

License metric mechanics

SQL Server uses a per physical core metric with edition and feature gating.

Per core licensing

Each physical core on the host requires a SQL Server core license.

  • Four core minimum per physical processor.
  • Core licenses sold in two core packs.
  • Hyper threading does not change the count.
  • Total cores on the host must be licensed if a SQL VM is hosted, unless VM level licensing is used with SA.

Standard vs Enterprise edition

Edition selection is the first audit lever.

  • Standard: most general purpose workloads.
  • Enterprise: required for Always On AG with secondary readable replicas, AlwaysOn Failover Cluster on more than two nodes, in memory OLTP at scale, partitioning, transparent data encryption (was Enterprise only, now in Standard from 2022), and other advanced features.
  • Down editioning where features are unused saves significant cost.

Server plus CAL legacy

Server plus CAL still exists in older licensing but applies only to Standard edition for new agreements.

Virtualization rules

Virtualization is the largest single source of audit exposure.

Host based licensing

Host based licensing covers unlimited SQL VMs on the licensed host.

  • Enterprise edition with Software Assurance unlocks unlimited VMs on the licensed host.
  • Standard edition without SA requires VM level licensing.
  • Licensing the entire host is often cheaper than licensing many VMs.

VM level licensing

VM level licensing covers a specific VM, not the host.

  • Minimum four core licenses per VM.
  • VM movement without SA requires re licensing.
  • Hyper threaded cores in the VM count as one core each.

SQL Server licensing scenarios, indicative 2026

Scenario License model Minimum cores SA recommended
Standalone physical serverPer core4 per socketYes for mobility
Virtualized, less than four VMs per hostPer VM4 per VMYes for movement
Virtualized, dense hostHost licensingAll host coresRequired for unlimited VMs
Azure SQL via Hybrid BenefitPer core with SAPer Azure SKURequired
Failover only secondaryPassive rightsCovered by SARequired

Software Assurance and mobility

Software Assurance is the single most important commercial decision in SQL Server licensing.

License mobility

SA unlocks license mobility, including movement to authorized hosting providers.

Azure Hybrid Benefit

Azure Hybrid Benefit lets on premises SQL Server licenses with SA cover Azure SQL Managed Instance and Virtual Machines at reduced rates.

Passive failover rights

SA includes free passive failover rights, often missed in inventory and lost at SA lapse.

Microsoft does not need to win the audit. Microsoft only needs the buyer to be unable to prove the licensing position. A clean inventory makes that impossible.

Inventory baseline

Audit defense lives or dies on the quality of the inventory baseline.

Host inventory

List every host running SQL Server with core count, edition, processor model, and virtualization platform.

VM inventory

List every SQL VM with vCore count, edition, host assignment, and movement history.

License evidence

Match every host and VM to a license entitlement with proof of purchase and SA status.

Audit response playbook

The audit response runs in three phases, regardless of how the audit was triggered.

Engagement

Engage independent advisory and legal before responding to Microsoft.

Scope

Narrow scope to specific products and time windows in writing.

Close out

Negotiate close out as part of the next renewal, not as a separate emergency purchase.

Suggested reading

What to do next

  1. Inventory every SQL Server host and VM with core count and edition.
  2. Match each instance to license entitlement and SA status in writing.
  3. Identify VMs that should be on host licensing rather than VM licensing.
  4. Review edition mix. Down edition where Enterprise features are unused.
  5. Document Azure Hybrid Benefit usage and passive failover rights.
  6. Build an audit response runbook with named legal and advisory contacts.
  7. Review SQL Server in the EA scope before renewal, not after.
  8. Engage independent advisory if a Microsoft audit notice is in hand.

Frequently asked questions

How is SQL Server licensed in 2026?

Per physical core with a four core minimum per processor. Two core packs are the unit of purchase. Editions are Standard and Enterprise. Server plus CAL legacy applies only to Standard for some older agreements.

Do I need to license every core on the host?

Only if you use host based licensing with Software Assurance or run more VMs than is economic to license individually. For dense SQL hosts, licensing all host cores with SA unlocks unlimited VM rights.

Is Software Assurance required for SQL Server?

Not strictly, but SA unlocks license mobility, Azure Hybrid Benefit, passive failover rights, version upgrades, and several other rights. Most enterprise SQL estates run with SA for these reasons.

What is Azure Hybrid Benefit for SQL Server?

Azure Hybrid Benefit lets on premises SQL Server licenses with active Software Assurance cover Azure SQL Managed Instance and Azure SQL Database compute at reduced rates. It is a major Azure cost lever for SQL workloads.

What triggers a SQL Server audit?

Common triggers include large download spikes, license expiry without renewal, contract anomalies during renewal negotiation, and rapid Azure adoption that creates apparent on premises shrinkage.

How do I prepare for a SQL Server audit?

Build a clean inventory baseline across hosts and VMs. Match each instance to a license entitlement and SA status in writing. Identify and close obvious gaps before any audit notice arrives.

Microsoft EA Renewal Playbook

The full microsoft ea renewal playbook framework from the Microsoft Practice.

Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.

Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.

No spam. We will only email you about this download. Privacy.
Run the Microsoft 365 license optimizer against your estate in under five minutes.
Open the Tool →
Per Core
License Metric
4 Min
Core Minimum
2
Virtualization Rights
90 Days
Audit Window
100%
Buyer Side

SQL Server audits are won and lost on the inventory baseline. Without a clean baseline, every Microsoft claim looks defensible. With one, most do not.

Morten Andersen
Co Founder, Redress Compliance
Deep Library

More on this topic.

Microsoft Practice →
Microsoft EA renewal playbook on a boardroom table
Microsoft
Microsoft EA renewal playbook.
Renewal moves, M365 SKU framework, Azure commitment, and the buyer side levers.
15 min read
Microsoft knowledge hub overview screen
Microsoft
Microsoft Knowledge Hub.
Every Microsoft framework, benchmark, and playbook in one library.
8 min read
Microsoft 365 license optimization dashboard
Microsoft
Microsoft 365 license optimization.
Right size E3, E5, F1, F3, and standalone add ons across the estate.
12 min read
Microsoft Azure Enterprise Agreement 2026
Microsoft
Microsoft Azure Enterprise Agreement 2026.
How the Azure EA works in 2026 and where to push for buyer leverage.
16 min read
Editorial boardroom interior

The advisor your vendors do not want.

500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.

The Microsoft Brief.

Monthly briefings on Microsoft audit defense, EA renewals, and the buyer side benchmarks across the Microsoft estate.