Fix it now
A licence review compares two lists: what you are entitled to, and what you have actually deployed. Almost every finding is a gap between records rather than deliberate copying, and almost every expensive finding is on the server side. The work that makes a review survivable is clerical and is done before anybody asks.
- Build the entitlement register now: product, SKU, quantity, channel, purchase date, invoice reference and agreement number, one row per purchase.
- Pull your volume licensing records from the right place. The Volume Licensing Service Center was retired in April 2024 and the functionality moved to the Microsoft 365 admin center, at Billing then Your products then the Volume licensing tab.
- Export purchased against assigned seats from the Microsoft 365 admin center at Billing then Licenses, and export a dated deployment inventory from Intune, Configuration Manager or your management tool rather than typing one.
- Check the four areas that produce the largest findings first: server core counts against physical cores, virtualisation density against entitlement, CAL counts against users and devices, and remote desktop against RDS CALs.
- Check that every device running a volume Windows build has a qualifying operating system licence underneath it. Microsoft states plainly that upgrade licences require a Qualifying Operating System licence and the device must already have one installed.
- Read your own agreement before you send anybody data. The right to verify comes from the agreement you signed, so involve whoever signs contracts and agree scope and format first.
Do not send raw estate data before you know what is required and who sees it. Producing your own inventory first changes the tone of the entire conversation, and nothing obliges you to publish a count you did internally.
If you can produce an entitlement register, a dated deployment inventory and a reconciliation between them, a review is paperwork. Below is what gets compared area by area, the evidence pack to assemble, and the order in which to close gaps.
Why it happens
Every review, whatever it is called, does the same thing: it collects discovery data from your estate, reconciles it against the entitlement records the vendor holds and the records you produce, and lists the differences. What varies is the shape of the request. A partner-led software asset management engagement is the gentlest, usually offered free with a sales motion attached. A self-assessment questionnaire asks you to declare deployment against entitlement. A formal letter names an accounting firm and cites the clause in your agreement that permits verification.
That last point is the one to internalise, because it decides everything about how you respond. The right to check sits in the agreement you signed rather than in general law, and the terms differ by programme. Microsoft does not publish a single universal notice period or threshold, so anyone who tells you the standard notice is thirty days is quoting somebody else’s contract. Read yours, and involve whoever signs contracts before any data leaves the building.
The findings cluster in predictable places, and they are not where small businesses expect. Desktop Office is usually the smaller number. Server core counts are the larger one, because a core licence covers hardware rather than people and a shortfall multiplies across every host. CALs come next, because they accumulate silently with headcount and are enforced by nothing. Remote desktop is third, because the two built-in administrative connections get used as general capacity.
Server cores and virtualisation density
You have this one if Hosts bought at different times, virtual machines added by whoever needed one, and no single document that says how many cores are licensed.
- Count physical cores per host and compare against core licences held, applying the minimums: 8 core licences per physical processor and 16 per server.
- Count Windows operating system environments per host against entitlement. Standard grants two per fully licensed server; Datacenter grants any number.
- Where Standard is stacked, confirm every set was actually purchased. Density creeps up quietly and each further pair of OSEs needs the whole server relicensed.
CALs nobody has counted since the server was installed
You have this one if Headcount has grown, contractors come and go, and the CAL quantity on the invoice is from three years ago.
- Recount users and devices per product, including unattended devices, and check the CAL version: a 2025 CAL reaches 2025 and prior versions, never the reverse.
- Check RDS separately. Per-user RDS CALs can be over-allocated by the licence server, so the console showing green proves nothing.
- Cover external users with an External Connector licence per accessed physical server rather than trying to enumerate them.
Volume Windows with nothing underneath it
You have this one if Enterprise or Pro deployed from an image across machines whose original edition nobody recorded.
- Confirm each device holds a qualifying operating system licence. Microsoft’s guidance is explicit that a device must already have a qualifying operating system installed to be eligible for a Windows 11 upgrade licence.
- The qualifying systems are Windows 10/11 Enterprise, IoT Enterprise, Pro and Pro for Workstations. Anything else needs a new PC with Windows preinstalled or a retail Full Packaged Product licence as the base.
- Read the channel per machine with
slmgr /dli, which displays licence information for the installed active Windows edition and needs no elevation.
Non-production licences running production workloads
You have this one if A developer subscription key on a server that real users depend on.
- Check it against the terms rather than intent. Visual Studio subscription software may be used for evaluation and to develop, test and demonstrate the customer’s programs, and Microsoft states plainly that the software is not licensed for use in a Production Environment.
- Any online service made available with a Visual Studio subscription carries the same restriction.
- Re-licence the workload properly before a review finds it. This is a finding with no defence and it is easy to spot in discovery data.
Full reference
What gets compared, area by area
| Area | What is compared | Why it commonly goes wrong |
|---|---|---|
| Windows Server | Physical cores per host against core licences held | The 8-per-processor and 16-per-server minimums; counting virtual machines instead of hardware |
| Virtualisation | Operating system environments running against entitlement | Standard grants two per fully licensed server, and density creeps up quietly |
| Windows Server CALs | Users and devices with access against CALs held | Headcount growth, contractors, and unattended devices nobody counted |
| Remote Desktop Services | RDS users and devices against RDS CALs | The two administrative connections used as general capacity; per-user RDS CALs over-allocated |
| SQL Server | Edition, core counts and Server plus CAL choices | Development instances serving production; Server plus CAL is Standard edition only |
| Windows desktop | Editions deployed against qualifying base licences | Volume Windows is an upgrade licence and the device still needs a qualifying OS underneath |
| Office, perpetual | Installations against licences purchased | An image containing Office deployed to more machines than were bought |
| Microsoft 365 | Assigned seats against purchased seats | Usually clean, because the platform enforces it |
| Non-production subscriptions | Developer subscription keys | Visual Studio software is not licensed for use in a production environment |
| Reassignment | How often a licence has moved | Not less than 90 days since the last reassignment of the same licence, exceptions aside |
The evidence pack to build now
Everything below can be assembled in an ordinary week and updated in an hour a quarter. It is the difference between a review that is paperwork and one that is a project.
- An entitlement register: product, SKU, quantity, channel, purchase date, invoice reference and agreement number, one row per purchase.
- Invoices from every reseller, naming your legal entity. Scan them and store them somewhere that survives a laptop refresh.
- Volume licensing agreement numbers and a licence summary exported from the Microsoft 365 admin center, under Billing then Your products then Volume licensing – VLSC was retired in April 2024 and the roles carried over with the same permissions.
- A seat report from the Microsoft 365 admin center at Billing then Licenses, showing purchased against assigned.
- OEM proof for every machine: the hardware invoice, which is the evidence, and the edition and channel read from the machine with
slmgr /dli. - A dated deployment inventory exported from Intune, Configuration Manager or your remote management tool, not typed by hand.
- A reconciliation sheet: entitlement minus deployment, per product, with a written note explaining every variance you already know about.
Microsoft’s published class reference for the SoftwareLicensingService WMI class does not list an OA3xOriginalProductKey property, and WMIC – the tool people usually reach for to read a firmware key – is being removed from Windows in favour of PowerShell. Do not build an evidence process on either. The hardware invoice is the evidence; slmgr /dli tells you what the machine believes it is.
Closing gaps in the right order
Work from the largest numbers down. Server core shortfalls are the biggest single line in most findings, because a core licence covers hardware rather than people and a shortfall multiplies across every host. CAL shortfalls come next, because they accumulate silently with headcount and nothing enforces them. Desktop software is usually last, both because the unit cost is lower and because subscriptions enforce themselves.
Buying to close a gap before a review is normally cheaper than settling one during it, and it is always cheaper than settling one afterwards. Buy through a channel that produces documentation in your company’s name, and file the invoice into the register on the day it arrives rather than at the next quarterly update.
Which approach to take, by situation
- A formal letter has arrived: read the agreement first, involve whoever signs contracts, and agree the scope and the data format before sending anything.
- A partner has offered a free assessment: usually worth accepting, but establish in writing what is reported back to the vendor and what stays with you.
- You have never counted anything: count now, quietly and internally. Nothing obliges you to publish the result of your own exercise.
- You are mid-merger or in diligence: two estates and two sets of records, and the buyer will ask for exactly this pack anyway.
- You are confident you are compliant: build the register regardless. Being compliant and being able to prove it are different states, and only one of them survives a request.
Records, and how long they matter
Keep licensing records for as long as the licence is in use, plus whatever your normal retention period is afterwards. Perpetual licences can be deployed for a decade, which means a decade-old invoice can be the only evidence for something running today. Portals do not solve this for you: the volume licensing portal changed once already in April 2024, so a PDF export you hold is worth more than a link you assume will still resolve.
When a licence is the actual fix
If a count turns up a genuine shortfall, the fix is to buy the missing licences through a channel that leaves a paper trail. Arco supplies Microsoft volume licensing along with the CALs, server core licences and desktop licences that most findings involve, and documents the purchase in your company’s name with the SKU and quantity stated plainly, which is the form the evidence needs to take. If your reconciliation shows you are already covered, you should buy nothing – building the register that proves it costs only time, and it is the cheaper half of this article by a wide margin.
Questions people ask about this
Can Microsoft audit us without warning?
Verification rights come from the agreement you signed rather than appearing from nowhere. Microsoft does not publish a single notice period, threshold or process that applies to every programme, so read your own agreement rather than relying on what somebody says is standard. That reading is the first step, before any data is collected or sent.
Is a product key acceptable as proof of licence?
No. A key demonstrates that software can be activated, not that you were entitled to it. Proof is the transaction: an invoice or agreement naming your legal entity, the SKU and the quantity, backed by the entitlement appearing in the correct place for that channel – which for volume licensing is now the Microsoft 365 admin center under Billing, Your products, Volume licensing.
Where did the Volume Licensing Service Center go?
It was retired in April 2024 and the functionality moved to the Microsoft 365 admin center. Agreements are found under Billing then Your products then the Volume licensing tab, and administrators who previously accessed VLSC with a Microsoft Entra ID have the equivalent roles there with the same permissions. Export what you need rather than relying on the portal being where you left it.
Does volume Windows cover a machine on its own?
No. Microsoft states that upgrade licences require a Qualifying Operating System licence and that the device must already have a qualifying operating system installed. The qualifying editions are Windows 10/11 Enterprise, IoT Enterprise, Pro and Pro for Workstations. A machine with no qualifying base needs a new PC with Windows preinstalled or a retail Full Packaged Product licence underneath the upgrade.
Can we use a developer subscription to run a small production service?
No. Visual Studio subscription software may be used for evaluation and to develop, test and demonstrate your programs, and the Product Terms state directly that the software is not licensed for use in a Production Environment. Any online service made available with the subscription carries the same restriction. It is one of the easiest findings to make and has no defence.
What does preparing actually cost?
Mostly time, and much less than people expect. The inventory comes from tooling you already own, the entitlement side comes from invoices and the admin centre, and the reconciliation is a spreadsheet. Money only enters the picture if the reconciliation finds a genuine gap, and finding it yourself is always the cheaper way to find it.
