Fix it now
A licence inventory is two lists rather than one: what you are entitled to run, and what is actually installed. Build them separately, because compliance is only the statement that the second is covered by the first, and a renewal is only negotiable if you can show both. The work is unglamorous and it is what turns an audit into a reconciliation.
- Start in the Microsoft 365 admin center. Billing then Licenses shows totals per product across subscriptions and names any groups used for assignment.
- Look for volume licensing in the same place. The Volume Licensing Service Center retired in April 2024; agreements, licence keys and downloads moved to Billing, then Your products, then the Volume Licensing tab, with the old VLSC roles carried across.
- Sort the roles before the data. On a new contract the Notices and Online Admin Contact becomes the first Online Administrator, who then assigns volume licensing roles to everybody else.
- Record proof of purchase rather than product keys. Microsoft’s terms make product keys Confidential Information and a key proves only that software can activate, never that you were entitled to it.
- Add a last-reassignment date column. The 90-day reassignment rule is only defensible if you can show when each licence last moved.
- Skip discovery tooling on a small estate. Microsoft Graph PowerShell and the licensing WMI class will give you an accurate enough deployment picture to reconcile against.
If you can already produce both lists and the evidence behind them, stop here. Below are the fields that earn their place, where each channel keeps the truth, and how to count deployment without buying anything.
Why it happens
Entitlement is what you are allowed to run: the licences you bought, from whom, under which agreement, with what rights attached. Deployment is what is actually installed and switched on. Compliance is simply the statement that the second list is covered by the first. Almost every audit finding comes from an organisation that maintained one of these lists carefully and never built the other, then discovered at the worst possible moment that the two had drifted apart across four hardware refreshes and a merger.
Keeping them separate also makes the numbers usable for buying. When your entitlement sheet says you hold forty Windows Server User CALs and your deployment sheet says thirty-four named users touch a file server, you have a defensible position and six CALs of headroom. When you hold one number that mixes the two, you have an opinion.
Where the truth lives has changed, and it is worth knowing before you start hunting for an old URL. Cloud subscriptions are the easiest: the Microsoft 365 admin center shows totals per product across subscriptions, and where licences are assigned through groups it shows the group name rather than each user. Volume licensing now lives in the same admin center – the Volume Licensing Service Center retired in April 2024 and agreements, keys and downloads moved to Billing, Your products, Volume Licensing, with VLSC roles enabled there under the same permissions. If nobody in the business can see that tab, the blocker is a role rather than a missing record: on a new contract the Notices and Online Admin Contact must become the first Online Administrator, and that person then assigns the rest.
OEM licences have no portal at all. The evidence is the device, its firmware-embedded key and the invoice for the hardware, which is why hardware purchase records belong in the same folder as licensing ones. Retail keys are the weakest link because they are usually held by whoever bought them. Chase those into the sheet first, with the invoice or order confirmation attached. Microsoft’s terms are explicit that product keys are Confidential Information of Microsoft and may not be disclosed to third parties, and a key on its own has never been evidence of entitlement.
One field earns its place more than people expect: the date a licence was last reassigned. Microsoft’s terms allow reassignment no sooner than 90 days after the last reassignment, with published exceptions for permanent hardware failure or loss, termination of the user’s employment or contract, and temporary reallocation to cover an absence. Every one of those exceptions depends on being able to show when the move happened and why. A sheet without that column cannot answer the question at all.
Full reference
The fields that earn their place
| Field | Why it matters | Where to get it |
|---|---|---|
| Product, edition and version | Downgrade and coverage questions turn on edition | Portal record and the installed build |
| Licence type | OEM, retail, volume and subscription carry different rights | Purchase record; OEM is tied to the device |
| Quantity | The number being reconciled | Agreement or subscription record |
| Assignment basis | Per user, per device, per core or per server | Product Terms for that SKU |
| Agreement or order number | The evidence an auditor asks for first | Microsoft 365 admin center, Volume Licensing tab, or the reseller invoice |
| Channel and reseller | Determines who can change or renew it | Your own purchase records |
| Purchase or start date | Establishes the term and any support window | Invoice |
| Renewal or expiry date | Drives the calendar and the budget | Subscription record |
| Software Assurance status | Decides upgrade, disaster recovery and reassignment rights | Volume licensing records |
| Date last reassigned | The 90-day rule and its exceptions depend on it | Your own change log; nothing else records it |
| Where the proof lives | So it can be produced in minutes rather than weeks | Your document store, linked from the sheet |
Where each channel keeps the record
| Channel | Where entitlement is recorded | What to export |
|---|---|---|
| Microsoft 365 subscriptions | Microsoft 365 admin center, Billing then Licenses | Purchased and assigned counts per product, plus any assignment groups |
| Volume licensing agreements | Microsoft 365 admin center, Billing then Your products then Volume Licensing | Agreement numbers, licence summary, keys and downloads |
| OEM | No portal | Hardware invoice, device serial, firmware-embedded edition |
| Retail | No portal | Invoice or order confirmation, held with the key |
| Antivirus and other vendors | The vendor console | Device list and licence usage page |
Counting deployment without buying a tool
For a small estate you do not need discovery software. Microsoft Graph PowerShell reports subscription counts and consumption tenant-wide, and the licensing WMI class on each Windows machine reports what is installed and how it is activated. Your antivirus console already holds a device list and your directory already holds a computer list. Export all four, deduplicate on machine name and user principal name, and you have a deployment picture good enough to reconcile against.
# Subscription entitlement and consumption, tenant-wide
Connect-MgGraph -Scopes "Organization.Read.All"
Get-MgSubscribedSku |
Select-Object SkuPartNumber, ConsumedUnits,
@{n='Purchased';e={$_.PrepaidUnits.Enabled}}
# What is installed and how it is activated on a Windows machine
Get-CimInstance -ClassName SoftwareLicensingProduct |
Where-Object { $_.PartialProductKey } |
Select-Object Name, Description, LicenseStatus
The Description field is the useful one on the second query: it distinguishes a retail licence from a volume KMS client or a MAK activation, which is exactly the distinction an auditor asks about and the one your invoices need to match. LicenseStatus is a number rather than a word, and it is worth having the meanings to hand: 0 is Unlicensed, 1 Licensed, 2 out-of-box grace, 3 out-of-tolerance grace, 4 non-genuine grace, 5 notification and 6 extended grace. Anything that is not 1 belongs on a follow-up list.
True-ups, and whether you actually have one
A true-up is the annual reconciliation under an Enterprise Agreement, where you order licences for the users and devices added since the last anniversary. Two published facts decide whether it applies to you. Microsoft sets the qualifying size for an Enterprise Agreement at 500 users and devices for commercial customers, and 250 for public sector; the agreement runs three years. And if you do hold one, the annual true-up order must reach Microsoft in the period between 60 and 30 days before the agreement anniversary, which makes the counting exercise due roughly a quarter earlier than most people plan for. If you buy through a reseller on subscription, none of this applies and the equivalent exercise is the seat count you take into the renewal.
How much inventory you need, by situation
- Under about twenty devices, all bought with the hardware: a single sheet with invoices attached is genuinely enough.
- Mixed cloud and on-premises: build the sheet by channel first, then reconcile, because the channels do not talk to each other.
- Facing a true-up under an Enterprise Agreement: count added users and devices since the last anniversary and diarise the 60-to-30-day ordering window.
- Post-merger or post-acquisition: inventory both estates separately before consolidating anything, because only fully-paid perpetual licences transfer at all, and only under Microsoft’s published divestiture and merger conditions.
- Preparing for an audit letter: prioritise proof of purchase over counting. Numbers can be recounted; evidence cannot be recreated.
- Approaching a renewal: bring the deployment count to the conversation. It is the only thing that makes a reduction negotiable.
When a licence is the actual fix
Once the inventory exists it usually shows two things: lines you are paying for and not using, and lines you are using and cannot evidence. The second group is where volume licensing normally becomes the answer, because it consolidates scattered retail and OEM purchases into one agreement with one set of records – now in the Microsoft 365 admin center rather than a separate portal. Arco can review your inventory sheet, tell you which existing licences carry forward, and quote only the genuine shortfall rather than a fresh count of every machine. Building the inventory itself costs nothing but time, and it is worth doing before you ask anyone, us included, for a price.
Questions people ask about this
Is a product key proof that I own a licence?
No. A key is a technical enabler; the licence is the right to run the software, and the evidence is the purchase record and the agreement it sits under. Microsoft’s terms go further and make product keys Confidential Information that may not be disclosed to third parties. Auditors ask for invoices, agreement numbers and, for OEM, the device the licence came with.
Where do I find our volume licensing agreements now?
In the Microsoft 365 admin center. The Volume Licensing Service Center retired in April 2024 and agreements, licence keys and software downloads moved to Billing, then Your products, then the Volume Licensing tab. VLSC roles were enabled there with the same permissions. If you cannot see the tab, the problem is a missing role: on a new contract the Notices and Online Admin Contact becomes the first Online Administrator and assigns the rest.
How often should the inventory be updated?
At every purchase, every leaver and every hardware change, then reviewed as a whole once a year before your main renewal. A sheet updated continuously takes minutes; a sheet rebuilt annually from scratch takes days and is wrong by the time it is finished. Update the last-reassignment date at the moment you move a licence, because nothing else records it.
Do I need a discovery tool?
Not for a small or medium estate. Get-MgSubscribedSku for subscription consumption, the SoftwareLicensingProduct WMI class for installed and activated products, plus your antivirus console and directory listings will get you an accurate enough picture. Discovery tooling earns its cost at hundreds of devices, multiple sites, or server products licensed by core where manual counting stops being reliable.
What is a true-up and does it apply to me?
It is the annual reconciliation under an Enterprise Agreement, and it probably does not apply to you. Microsoft sets the qualifying size at 500 users and devices for commercial customers, 250 for public sector, on a three-year agreement. If you do hold one, the true-up order must reach Microsoft between 60 and 30 days before the anniversary. If you buy through a reseller on subscription, your equivalent is the seat count you take into the renewal.
