A regional insurance carrier was approaching Microsoft renewal decisions in mid-2022 with the usual problem: too many contracts, too many moving parts, and too little confidence that the next purchase would actually match the estate. The client had an on-prem Microsoft footprint spanning 40 servers, plus Microsoft 365 subscriptions being billed through CSP. A June 22, 2022 CDW quote proposed $154,660.34 of Microsoft software assurance across Visual Studio, Windows Server, and System Center before the client had a reconciled view of what truly needed to be renewed.
UMS was engaged through CDW on a fixed-fee Microsoft licensing consultation to review current licensing, provide true-up and renewal guidance, and replace renewal momentum with evidence. By the September 12, 2022 closeout, UMS had reconciled a mixed EA, MPSA, and CSP position covering 30 qualified users, 30 qualified desktops, and 40 servers. The final recommendation was clear: the client’s on-prem SQL Server, Windows Server, and System Center estate could continue on perpetual rights without new renewal purchases as long as no upgrades were planned, while the Microsoft 365 subscriptions should be transferred to CDW first and then downsized after the transition.
That shifted the decision from “renew what the quote says” to “buy only what the deployed versions and contract rights actually require.”
The Challenge
The client’s Microsoft stack had grown across several licensing motions at once:
- Mixed agreement layers — Core on-prem products were spread across EA, MPSA, Microsoft License Statement history, and older perpetual records, while Microsoft 365 was already being billed through CSP.
- Commercial pressure before reconciliation — A six-figure quote for software assurance arrived before the client had one defensible view of what versions were deployed and what rights were already in place.
- Hybrid estate complexity — The environment included physical servers, VMware hosts, virtual machines, SQL workloads, desktop systems, and Microsoft 365 subscriptions that could not be evaluated as one flat user count.
- License carry-forward risk in Microsoft 365 — The closeout workflow specifically called out the need to archive mailboxes for retired employees, a sign that some user licenses were likely being preserved for retention rather than active use.
This is a common Microsoft renewal trap. Procurement has a quote. IT has partial inventory. No one is fully comfortable signing the renewal, but the deadline keeps moving faster than the evidence. The client needed a partner who could combine Microsoft optimization and contract negotiation support into one working fact base.
How UMS Solved It
UMS approached the engagement as a true reconciliation, not just a quote review.
Step 1: Establish the actual scope UMS first anchored the environment count and agreement stack. The final workbook summarized a footprint of 30 qualified users, 30 qualified desktops, and 40 total servers across EA, MPSA, and CSP sources. The successful scan set covered 36 inventoried Windows systems, split between 6 physical systems and 30 virtual machines, with failed devices broken out separately for follow-up rather than buried inside the totals.
That mattered because renewal quality depends on separating verified devices from assumptions. UMS also had VMware host data, SQL workload detail, and product-level deployment views instead of treating the estate as a single opaque server count.
Step 2: Rebuild the entitlement position product by product Next, UMS matched deployment evidence against the entitlement record:
| Product Area | What UMS Reconciled | What the Finding Changed |
|---|---|---|
| Microsoft 365 CSP | 119 Office 365 E1, 57 Office 365 E3, 176 EMS E3, 176 Defender for Office 365 Plan 1, 3 Visio Plan 2 | Established the “transfer as-is, then right-size” path instead of changing everything during the reseller transition |
| Windows Server | Datacenter and Standard core positions across physical and virtual estate | Confirmed the client could stay on perpetual rights if no upgrades were planned |
| SQL Server | Enterprise Core and Standard Core workloads across clustered physical systems and VMs | Removed pressure to renew or move licenses just because the EA had expired |
| System Center | Datacenter and Standard core coverage across server estate | Confirmed renewal was not required for the current-version operating model |
The point was not to prove that every Microsoft cost should be cut immediately. It was to prove which costs were still justified and which were being carried forward by habit.
Step 3: Separate perpetual-use decisions from upgrade-rights decisions This was the turning point in the project. The final ELP and closeout deck both documented that the client’s on-prem environment was already covered by perpetual rights for SQL Server, Windows Server, and System Center, provided the client did not upgrade to newer versions.
That distinction matters. A renewal quote can be commercially real and still be operationally unnecessary. In this case, the June 2022 CDW quote was largely framed around software assurance, while the September 2022 UMS closeout established that the client’s current-version posture did not require rolling those products into new renewal purchases.
Step 4: Create the post-transition cleanup plan UMS did not stop with the server-side finding. For Microsoft 365, the recommendation was to move the CSP estate to CDW first, then downsize the user counts after the first 30 days. The closeout also documented a mailbox-retention workflow for retired employees:
- Assign the right Exchange Online hold capability.
- Remove the broader paid license.
- Place the mailbox on hold.
- Mark the mailbox inactive.
- Remove the old license.
That is important because Microsoft 365 waste is often less about the active workforce than about legacy users, retained mailboxes, and old assignment patterns that survive every renewal cycle.
Results
| Metric | Before | After | Impact |
|---|---|---|---|
| On-prem Microsoft renewal posture | $154,660.34 software-assurance quote dated June 22, 2022 | Final September 2022 ELP showed no renewal need for current SQL Server, Windows Server, and System Center versions if no upgrades occurred | Quote pressure replaced by version-aware buying discipline |
| Environment visibility | Mixed EA, MPSA, CSP, and inventory views | One reconciled position across 40 servers, 30 desktops, and 30 users | IT and procurement worked from the same fact base |
| Microsoft 365 contract path | Existing CSP footprint spread across 119 E1, 57 E3, 176 EMS E3, 176 Defender P1, and 3 Visio P2 subscriptions | Transfer-to-CDW-first plan, then quantity reductions after transition | Operationally safe route to right-sizing |
| Retired-user licensing process | Mailbox-retention needs risked carrying full licenses forward | Documented inactive-mailbox workflow for archived users | Better retention hygiene without paying for the full user stack forever |
The biggest win was not a dramatic product migration. It was commercial clarity. UMS showed the client where it truly had to spend, where it did not, and how to transition Microsoft 365 without turning the reseller move into a licensing fire drill.
Key insight: In Microsoft renewals, the most expensive licenses are often the ones a company buys because the quote arrived before the reconciliation did.
Additional Outcomes
- Renewal urgency stopped driving the answer — The client could evaluate software assurance from the roadmap and version plan instead of treating the renewal calendar as the decision maker.
- The VMware-backed server estate was treated as a licensing system, not just an infrastructure map — Physical nodes, VMs, SQL clusters, and System Center dependencies were reviewed in the same model.
- Mailbox retention became part of license governance — UMS translated an operational records requirement into a lower-cost Microsoft 365 handling pattern rather than letting old accounts silently inflate the subscription footprint.
For enterprise teams facing Microsoft renewal pressure, this engagement shows where the real leverage often sits. Before negotiating price, make sure the quantity, version, and entitlement story is actually right. If perpetual rights already cover the deployed environment, the most valuable work may be preventing a purchase instead of trying to optimize it after the order is placed.
See also: How a Regional Consumer Finance Lender Built a Repeatable Microsoft True-Up Process Across 2,300 Devices for another example of UMS turning Microsoft renewal pressure into an evidence-based operating model.