A diversified components manufacturer with a large Microsoft estate spread across office staff, task workers, shop-floor devices, and acquired entities did not have a simple licensing problem. It had a scale problem. At baseline, the environment covered 1,952 qualified users, 2,269 qualified desktops, and 547 thin clients, with different work profiles pulling against the same renewal and compliance deadlines.
The immediate pressure point was Microsoft licensing visibility. Renewal decisions, true-up preparation, and user segmentation all depended on having a defensible view of what was owned, what was deployed, and which workers actually needed which rights. UMS helped the manufacturer move from point-in-time spreadsheet exercises to an ongoing Microsoft optimization and governance program built around recurring data reconciliation, effective license positions, and annual contract readiness.
That operating model scaled. By February 2019, the managed program covered 3,977 devices, and in January 2020 the client approved a three-year extension that carried the engagement through February 14, 2023.
The Challenge
The manufacturer’s Microsoft estate had grown into the kind of environment where small visibility gaps become expensive. The company was balancing traditional information workers, lighter-use task workers, and kiosk-style shop-floor access, all while supporting on-premises infrastructure, Office workloads, SQL usage, and a growing estate shaped by acquisitions.
A 2017 renewal review made the problem plain. Finance had a stated working budget of $650K for the desktop and user licensing plan under consideration. IT wanted room to modernize. Operations wanted systems to keep running without disruption. And leadership needed a licensing position they could defend before key contract milestones.
The initial effective license position work also surfaced specific areas that required attention before true-up and renewal events:
- User segmentation was not aligned to licensing policy — The company had 1,363 productivity users, 589 business task workers, and 547 shop-floor kiosk devices, but those groups did not all need the same Microsoft stack.
- Deployment and entitlement data lived in different places — Without a repeatable reconciliation process, annual true-up work risked turning into a manual scramble.
- The estate included real exposure points — Early reconciliation highlighted gaps requiring validation, including 163 Windows desktop OS licenses, 163 Office Professional Plus positions, 465 SQL User CALs, and 5 Visual Studio Professional with MSDN subscriptions in the true-up view.
- Acquisitions increased complexity — The environment included acquired entities in the United States and abroad, making it harder to maintain one clean, current licensing fact base.
This could not be solved with a one-time recommendation deck. The client needed a system and cadence that would survive growth, contract cycles, and operational change.
How UMS Solved It
UMS structured the engagement as an ongoing governance program rather than a one-off audit. The kickoff on June 16, 2017 established the core scope: implement License Management as a Service, administer the dashboard environment, cleanse and normalize deployment and entitlement data, deliver a Microsoft effective license position, train stakeholders on self-service reporting, and facilitate regular working sessions.
Step 1: Build a defensible baseline UMS started by turning a mixed environment into a licensing model leadership could actually use. That meant establishing qualified user and device counts, mapping different worker profiles to different licensing needs, and documenting where existing spend was not delivering corresponding value. The renewal review explicitly called out that the client was not getting meaningful value from several cloud-adjacent components at the time, including Azure and Dynamics Online, and had only limited Office 365 ProPlus usage in testing.
Step 2: Reconcile entitlements against actual deployment The heart of the work was the effective license position. UMS used deployment data, entitlement records, and Microsoft contract logic to show what was really in use and where the important gaps sat.
| Category | What UMS Clarified | Why It Mattered |
|---|---|---|
| User populations | 1,363 productivity users, 589 task workers, 547 kiosk devices | Enabled role-based licensing instead of one-size-fits-all purchasing |
| Qualified estate | 1,952 users and 2,269 desktops at baseline | Gave finance and IT a common planning denominator |
| True-up exposures | 163 Windows positions, 163 Office positions, 465 SQL CALs, 5 Visual Studio subscriptions requiring validation | Turned vague renewal risk into a concrete action list |
| Managed scope growth | 3,977 devices in the 2019 program order | Proved the governance model could scale with the business |
Step 3: Turn analysis into an operating rhythm UMS did not stop at the spreadsheet. The program included dashboard administration, recurring data imports, and regular meetings so the licensing position stayed current between annual milestones. That matters in manufacturing environments, where worker populations, shared devices, and infrastructure footprints do not stand still.
The recurring model also made contract negotiations more practical. Instead of rebuilding the story from scratch before every anniversary or renewal, the client had a living fact base that could be used for annual true-up preparation and longer-range planning.
Step 4: Keep the model in place as the company changed Executed program records show the engagement maturing beyond the initial rollout. A February 2019 order tied the service to 3,977 devices, and a January 14, 2020 change order extended the existing SOW for three additional years, preserving the same per-device commercial structure through February 2023. That is the clearest evidence that the program had become part of how the manufacturer managed Microsoft licensing, not just a short-term project.
Results
| Metric | Before | After | Impact |
|---|---|---|---|
| License governance model | Renewal and true-up work driven by point-in-time analysis | Recurring LMaaS operating model with regular meetings and data updates | Moved licensing into a managed process |
| Estate visibility | Separate deployment, contract, and entitlement views | Centralized dashboard plus Microsoft ELP | One defensible source of truth |
| Managed scope | Baseline of 1,952 qualified users and 2,269 desktops | Program order covering 3,977 devices by 2019 | Scaled governance with the environment |
| Program continuity | Initial kickoff in 2017 | Extended through February 14, 2023 | ~6 years of sustained coverage |
The most important result was not a single negotiated discount or one dramatic audit escape. It was control. The client gained a repeatable operating model for understanding its Microsoft position, preparing for annual true-ups, and aligning licensing choices to how different parts of the business actually worked.
That matters because a manufacturer like this does not stay still. Worker populations shift. Devices proliferate. Acquired entities add new contracts, infrastructures, and exceptions. A governance model that can absorb that change is materially more valuable than a one-time cleanup that is out of date six months later.
Key insight: In complex Microsoft environments, the highest-value win is often not a one-time price concession. It is replacing licensing guesswork with a durable governance system that keeps renewal, compliance, and worker segmentation decisions grounded in current data.
Additional Outcomes
- Created a role-based licensing framework — The program gave the client a practical way to distinguish productivity users, task workers, and kiosk access instead of paying for the same stack everywhere.
- Made annual contract events more manageable — Effective license positions and recurring data updates reduced the amount of discovery work required each time true-up planning came around.
- Built a foundation that survived growth — The managed scope expanded to 3,977 devices and the engagement was extended for three more years, showing that the process held up as the estate evolved.
For organizations that have grown through operational complexity rather than greenfield planning, that is the real lesson. Microsoft licensing control is not a document. It is a discipline. This client invested in making it continuous.