Case Study: How Vertex Solutions Mastered Microsoft 365 Per User Licensing Explained to Cut Costs by 15%

Background: The Shift to Identity-Based Productivity 👤

In the evolving landscape of cloud productivity, understanding Microsoft 365 per user licensing explained in a practical context is essential for any IT leader. For many years, IT procurement focused on "counting boxes" or "counting machines." If a company had 100 computers, they bought 100 licenses. However, the shift to Microsoft 365 changed the fundamental unit of value from the hardware to the identity.

This case study examines "Vertex Solutions," a fictional mid-size engineering firm with 450 employees spread across three regional offices. Vertex had recently transitioned from Office 2019 Perpetual licenses to a Microsoft 365 subscription. While the transition seemed straightforward, the IT department quickly realized that their historical understanding of "licensing" was leading to significant compliance gaps and unnecessary expenditure.

The goal of this study is to demystify the "per user" model. We will explore how Vertex moved away from outdated device-centric thinking to a modern identity-based framework. By the end of this narrative, you will understand not just what "per user" means for your budget, but how it dictates your technical deployment strategy, particularly regarding Microsoft 365 per user vs per device comparison logic.

Note: While standalone OEM licenses are often marketed at low price points, they are strictly for hardware manufacturers to pre-install. For a growing organization like Vertex, Retail or Volume Licensing (via CSP or EA) is the only legitimate path for managing a professional workforce.

The Challenge: When Devices Outnumber People 📱

Vertex Solutions faced a complex environment. Of their 450 employees, 300 were "Knowledge Workers" (engineers and admins) who each had a dedicated laptop. The remaining 150 were "Field Technicians" who shared 50 ruggedized tablets in the warehouse and on-site. The IT Manager, Sarah, initially assumed that "per user" simply meant "one subscription per person," but the reality was more nuanced.

The firm encountered three primary challenges:

• The Multi-Device Paradox: Engineers were using a desktop at the office, a laptop at home, and a smartphone for email. Under the old model, this would have required three licenses. Sarah needed to confirm if Microsoft 365 per user licensing explained the ability to cover all these devices under one cost.
• Shared Device Compliance: In the warehouse, technicians were logging into a single Windows account on shared tablets to check inventory. They were using a single "Warehouse_Admin" M365 license. During a internal self-audit, they realized this was a major violation of the Product Terms.
• License Bloat: The procurement team was still buying licenses for every new computer arriving from the vendor, not realizing the users already had roaming rights. This resulted in a 15% over-spend on unnecessary subscriptions.

Furthermore, the team was confused about Microsoft 365 Business Premium user limits in 2026. They were rapidly approaching the 300-seat cap for the "Business" family and didn't know how the "per user" rules would change if they moved to Enterprise E3 plans.

Options Considered: Identity vs. Hardware vs. Kiosk Models 🔍

Sarah and her team evaluated three distinct pathways to resolve their licensing confusion and prepare for their upcoming contract renewal. Each option had different implications for their licensing Microsoft 365 for shared workstations and overall budget.

Option 1: The "Status Quo" with Generic Accounts

This involved staying on their current path—assigning one license to a generic user account (e.g., ShopFloor@vertex.com) and letting multiple people use it. Verdict: Rejected immediately. This is a direct violation of Microsoft's Online Service Terms. Licenses are for individuals, not roles. In the event of an audit, this would result in heavy fines and back-payments.

Option 2: Device-Based Licensing (M365 Apps for Device)

Microsoft offers a specific license for devices rather than users, often used in kiosks or labs. Pros: Ideal for the 50 tablets shared by 150 people. Cons: It does not include individual OneDrive storage or personal Exchange mailboxes. Since the technicians needed their own email addresses for safety alerts, this option was incomplete.

Option 3: Pure Per-User Licensing with Shared Computer Activation (SCA)

This involved purchasing a license for every single human being (all 450) and utilizing a technical feature called Shared Computer Activation. Pros: Full compliance, individual data security, and simplified management. Cons: Higher upfront subscription count compared to "sharing" accounts, but lower than the old "per device" model where engineers had 3+ devices.

Sarah also had to investigate reassigning Microsoft 365 licenses after termination. In a high-turnover sector like field tech, she needed to know if she could reclaim a license from a departing tech and give it to a new hire without purchasing a new seat every time.

Decision and Reasoning: Why Identity Won Over Devices ✅

Vertex Solutions decided to adopt Option 3: A 100% User-Subscription model. They transitioned their 300 engineers to Microsoft 365 E3 (to bypass the 300-seat limit of Business Premium) and placed their 150 technicians on Microsoft 365 F3 (Frontline) plans.

The reasoning was based on three pillars:

1. Compliance Security: By assigning a license to a person's Entra ID (Azure AD) identity, the license "follows" them. Whether an engineer logs into their work PC, their home Mac, or their mobile phone, the license is valid. This eliminated the common Microsoft 365 licensing audit triggers associated with generic accounts.
2. Feature Parity: The F3 plan for technicians was cheaper than the E3 plan but still provided a "per user" entitlement for web and mobile apps, plus a 2GB mailbox. This met the requirement for individual communication without the cost of a full desktop suite license.
3. Technical Enablement: To handle the shared tablets, they utilized Microsoft 365 apps for enterprise shared computer activation. This specific setting allows the Office software to be installed on a machine without it "consuming" one of the user's 5 allotted device installs. Instead, it checks the user's entitlement every time they log in.

Sarah confirmed that "per user" meant the person could use Office on up to 5 concurrent devices. For the engineers, this was a massive win. For the technicians, the "per user" F3 license meant they were compliant even when picking up any of the 50 available tablets in the warehouse.

Implementation and Results: Metrics of Success 📊

The implementation took place over a 90-day window. The most critical technical step was reconfiguring the warehouse tablets. Instead of a standard Office installation, the IT team used the Office Deployment Tool (ODT) to enable SharedComputerLicensing. This is the "secret sauce" for licensing Microsoft 365 for shared workstations correctly.

Step-by-Step Implementation:

• Identity Cleanup: Vertex audited their Active Directory to ensure no "ghost" users or generic accounts were assigned licenses.
• F3 Rollout: Technicians were given individual credentials. They were trained to sign out of the tablets at the end of their shifts.
• Policy Update: The procurement policy was updated. Instead of buying a "license for the new laptop," the HR trigger for a "New Hire" now automatically generated a request for a "New User Subscription."

The results were measurable and immediate:

• Cost Reduction: Vertex avoided purchasing 120 extra licenses they previously thought were necessary for "multi-device" engineers.
• Audit Readiness: A mock audit performed by a third-party consultant resulted in a 100% compliance score, a significant improvement from the "Red" status they would have received under the generic account model.
• Zero OEM Risks: By moving to a Volume-based CSP model, they ensured all licenses were portable and legally assigned, avoiding the pitfalls of non-transferable hardware-bound keys.

In terms of Microsoft 365 Business Premium user limits in 2026, they successfully migrated to the Enterprise tier before hitting the 300-seat ceiling, ensuring no disruption in service during their growth phase.

Lessons Learned: Navigating the 2026 Licensing Landscape 💡

The journey of Vertex Solutions provides several critical lessons for IT Directors and Procurement Managers navigating the Microsoft 365 per user vs per device comparison.

1. "Per User" is a Legal Definition, Not Just a Technical One
Even if the software technically allows you to sign in with a generic account, the legal contract (Product Terms) requires that a license be assigned to a specific human. Automation and "clever" workarounds are the fastest way to fail an audit.

2. Shared Computer Activation (SCA) is Vital
If you have more users than devices (like Vertex's warehouse), you must use the ProPlus/Apps for Enterprise version of Office that supports SCA. The standard "Business" versions (Business Standard/Premium) do not support SCA in the same way on traditional RDS/VDI environments, which is a common point of confusion.

3. License Reassignment Requires Discipline
When considering reassigning Microsoft 365 licenses after termination, remember the 90-day rule. You cannot flip-flop a license between two part-time employees every week to save money. The license must stay with the user for at least 90 days unless their employment is ended.

4. The Total Cost of Ownership (TCO) Shift
While monthly subscriptions might look more expensive than a one-time OEM purchase (which we advise against for organizations), the value lies in the 15-device entitlement per user. Vertex saved money not by finding "cheap" licenses, but by maximizing the utility of the licenses they already had across multiple platforms (Windows, macOS, iOS, Android).

By focusing on Microsoft 365 per user licensing explained in this comprehensive way, Vertex Solutions transformed their IT department from a cost center into an efficient, compliant, and modern operation.

📊 Comparison