A Market Briefing Is Not an NHS License Position
NHS England awarded IDC UK Limited £46,000 for “benchmarking and advisory services relating to software licensing and pricing as part of preparation for large scale software licensing procurement.” The Contracts Finder notice, published 30 March 2026, is titled MS Benchmarking Services. It was a G-Cloud 14 call-off after a search and shortlisting exercise. No SKU list is in the award. The implied file is the national Microsoft estate NHS England already runs.
That’s the problem.
This is not a procurement-notice story. It is a license-position story. A £46k briefing can tell you what the market looks like. It cannot tell you what you are using. You cannot negotiate NHS Microsoft licensing at this scale with a market note unless you already have a live license position.
What the notices actually say
The 2026 award is short. Buyer: NHS England. Supplier: IDC UK Limited. Value: £46,000. Route: G-Cloud 14. Purpose: benchmarking and advisory services on software licensing and pricing, as preparation for a large-scale software licensing procurement. The buyer’s own title is MS Benchmarking Services. That is as close as the notice gets to naming the vendor.
The estate sitting behind that title is not a mystery. On 29 June 2023, NHS England published a Contracts Finder award to Bytes Software Services for “Procurement of Core Licensing for NHS England and wider-NHS under NHSmail,” with scope to bring in alternative technology products over the term. The published value is £774,531,681.36. The initial term was 34 months from 1 June 2023, extendable by up to two years. Contemporaneous NHS and Microsoft statements described the deal as covering Microsoft 365, Teams, and related security tools for about 1.5 million staff. Small percentage moves on a file that size are tens of millions over the term.
One more distinction, because the UK public sector has more than one Microsoft file. This is not the 2025 SPA24 memorandum. That was a Crown Commercial Service arrangement for eligible public bodies. This is NHS England preparing its own next national Microsoft round. Different buyer. Different contract. Different numbers you have to defend. A named UK public-sector Microsoft cleanup is West Northamptonshire Council’s £1 million consolidation.
A £46k briefing will not negotiate a £774 million estate
Benchmarking answers a useful question. What are others paying. What has moved in the catalog. Is there room to push. That is IDC’s job on a short G-Cloud call-off.
The question you have to answer is narrower. What are you actually consuming across email, Teams, and the security tools that ride with them. What are you entitled to. What sits unused. What would you still need if the next deal is smaller, larger, or bundled differently.
Those are not the same file.
Picture the room. The IDC work is landing. Your CIO wants to know whether the last national deal was a good one, and what you should walk into the next Microsoft conversation with. Procurement wants a number. Finance wants a range. Microsoft, or the reseller who will deliver the next term, will walk in with a seat count close to the workforce headline and a bundle that treats “security” as one line.
If SAM takes three weeks to recast assigned seats, active use, and entitlement against that bundle, the briefing becomes the file. The market note will be current. The estate will not.
This is not a criticism of the teams who commissioned the work. A national health estate is exactly the profile traditional SAM tools were built for: comprehensive collection, slow answers, a specialist in the middle. Those tools prove what is deployed. They do not, on their own, turn more than a million identities into a decision the CIO can take into a nine-figure conversation. The gap is interpretation work. An analysis that arrives after the vendor has framed the meeting is a document. One that arrives during the meeting is a decision input.
If that feels familiar, the problem is not your team’s maturity. A commercial question is being answered with a market briefing.
Public sector makes this harder, not easier. The deal spans organizations. Day-to-day operations sit on the suite. Lead times are long on purpose. That is why a £46k exercise is rational. It is also why it is not enough. The leverage in a deal this size is not the benchmark slide. It is the unused SKU, the local buy that leaked off the national contract, and the security product that was paid for and never turned on. None of that is in a pricing comparables pack.
The vendor will walk in with a number. The only question is whether you have yours first.
What to count before the next NHS Microsoft licensing conversation
Do this in the same window as the IDC work, as a decision pack, not a project.
| What to count | Why it has to be live before you talk |
|---|---|
| Assigned seats vs active use, by product | 1.5 million staff is a workforce number. It is not automatically 1.5 million of email, Teams, and every security SKU. |
| Security tools actually enabled | “Related security tools” is not one line. Unused security is the easiest silent uplift at renewal. |
| National-deal entitlement vs local or trust-level buy | Fragmented purchase is how a national number leaks. You cannot defend the next Bytes conversation if a slice of the estate is still buying around it. |
| Identity count vs license count | A joiners-and-leavers problem at this scale is not a rounding error. It is the difference between the headline and the position. |
| What you would still need if the bundle changes | The briefing will describe the 2026 market. You need the estate those products would land on (including SKUs that did not exist when the 2023 deal was signed). |
Then say, in one page, whether the next conversation is a like-for-like renewal, a cleanup, or a smaller buy. A benchmark that arrives without that page is a document. A live position that can be briefed in fifteen minutes is a decision input.
Can a non-specialist walk the CIO through that pack today? If the answer is no, you do not have an NHS Microsoft licensing position. You have a library and a £46k reading list.
The decision layer, not another inventory
You already have discovery data, a national contract, and now a benchmarking engagement. The gap is not another inventory. The gap is turning that estate into a decision: what you use, what you are entitled to, what should happen before anyone picks up the phone. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next. A live Microsoft 365 position from the Graph data you already have is the point. Another report that needs a specialist to decode it is not. Microsoft Deployment Manager and Microsoft Entitlement Manager sit on that Graph feed so assignment, active use, and entitlement can be briefed in the same pack.
If you are heading into a Microsoft conversation this year and your current tools still need three weeks to turn “1.5 million staff” into assigned, active, and entitled, book a Software Intelligence Review. You can also start on the free plan and run the analysis on your own data.
The question to walk in with
Do not let the next meeting open as “did we get a good deal last time.” The briefing can help with that. The right question is: what are we actually using, what are we entitled to under the current national deal, and what would we still buy if the bundle moved. That is a data question, not a sales question.
£46,000 buys you a market view. It does not buy you a license position. The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.
