Microsoft 365 Frontline Worker Licensing:
F1 vs F3 vs E3

The Over-Licensing Problem in Frontline Workforces

Microsoft's frontline worker SKUs — F1 (£2.00/user/month) and F3 (£7.40/user/month) — exist specifically for shift workers, store associates, factory floor staff, and other workers whose Microsoft 365 requirements are fundamentally different from office-based knowledge workers. Yet in the majority of EA renewals we advise on, enterprises are running 20–60% of their frontline population on E3 licences priced at £27.40/user/month.

The overpayment is significant. A retail enterprise with 8,000 store associates on E3 is spending approximately £2.63M annually on M365 licences for workers who primarily need Teams, Shifts, and basic communication tools. Moving this population to F1 would cost £192,000 — a saving of £2.44M per year for the same functional outcome. Even F3 at £711,360 saves £1.92M annually versus E3.

How does this happen? Three mechanisms: (1) Microsoft's standard renewal proposals default to E3 for all users; (2) IT teams find it operationally easier to manage a single SKU; (3) Microsoft account teams are incentivised to sell E3 volume and do not proactively recommend downgrade. The information asymmetry is entirely in Microsoft's favour — until you engage independent advisory.

F1, F3, and E3: What You Actually Get

Understanding the SKU differences is foundational to the right-sizing decision. The commercial structure of M365 frontline SKUs is designed around a specific use case — workers who do not primarily work at a fixed desk, who may share devices, and whose productivity needs centre on communication, scheduling, and task management rather than full Office suite capabilities.

Capability	F1 (£2.00/mo)	F3 (£7.40/mo)	E3 (£27.40/mo)
Microsoft Teams (web + mobile)	✓	✓	✓
Teams Shifts (scheduling)	✓	✓	✓
Teams Walkie Talkie	✓	✓	✓ (add-on)
Exchange Online (email)	2GB (kiosk mailbox only)	50GB full mailbox	100GB full mailbox
SharePoint access	Read-only / intranet	Full	Full
Office apps (desktop)	✕ (web only)	✓	✓
Word, Excel, PowerPoint desktop	✕	✓	✓
Power Apps (1 app)	✕	✓	✓ (add-on)
Microsoft Viva Connections	✓	✓	✓
Intune device management	✕	✓	✓
Azure AD P1 (Entra ID)	✕	✓	✓
Shared device licensing	✓ (included)	✓ (included)	Requires add-on

The most significant capability difference between F1 and F3 is desktop Office apps, full Exchange mailboxes, Intune, and Entra ID P1. Between F3 and E3, the differences narrow considerably — primarily mailbox size (50GB vs 100GB), some compliance capabilities, and advanced security features. For most frontline worker populations, the E3-to-F3 gap is marginal relative to the F3-to-F1 gap.

The F1 vs F3 vs E3 Decision Framework

The right SKU for your frontline population depends on three questions. Work through them in order:

Question 1: Do they need desktop Office apps?

If your frontline workers primarily use shared devices (tablets, kiosk terminals, shared floor PCs), they almost certainly do not need desktop-installed Office applications. F1 provides web-based access to Office Online — sufficient for occasional document viewing and editing. If they work on personally-assigned Windows laptops or desktops with regular document creation tasks, F3 or E3 is appropriate. In most frontline scenarios — retail, logistics, manufacturing, healthcare non-clinical — the answer is no: desktop Office is not needed.

Question 2: Do they need a full email mailbox?

F1 provides only a 2GB kiosk mailbox — enough for Teams notifications and basic system emails, not for active email correspondence. If your frontline workers conduct meaningful business via email (customer communications, supplier coordination, regulatory correspondence), F3's 50GB mailbox is required. For many frontline populations — store associates, warehouse operatives, hospitality staff — Teams messaging has effectively replaced email, making F1's kiosk mailbox adequate.

Question 3: Do they need Intune and Entra ID P1?

Shared device management via Microsoft Endpoint Manager (Intune) is included in F3 but not F1. If your frontline workers use shared devices managed through the M365 stack, F3 is likely required. However, many organisations manage shared frontline devices through separate MDM solutions (Jamf, SOTI, VMware Workspace ONE) — in which case the absence of Intune in F1 is not a gap. Entra ID P1 (for conditional access, MFA, and identity governance) is also absent from F1 — a meaningful gap for organisations with strict identity and access controls.

Implementing a Mixed-SKU Frontline Model

The practical outcome of the decision framework above is almost always a mixed-SKU deployment: most frontline workers on F1, a minority on F3, and only exception cases on E3. Implementing this within an EA requires attention to three operational areas:

Identity and Access Management Uplift

F1 users do not have Entra ID P1 — this affects conditional access policies, group-based licensing, and some MFA capabilities. If your security team relies on Entra P1 features for frontline worker access, you have two options: (a) add Entra ID P1 as a standalone add-on to F1 users (priced at approximately £4.50/user/month — still significantly below F3 or E3), or (b) segment the frontline population so that users requiring Entra P1 receive F3 while the remainder receive F1.

Shared Device Management

F1 supports shared device licensing by default — a meaningful operational advantage over E3, which requires a separate Shared Device Licence add-on (approximately £3.00/user/month). If your frontline uses shared devices and you are currently on E3, you are paying both the E3 per-seat cost and potentially the shared device add-on, or you are not using shared device mode at all. F1 resolves both issues — it is purpose-built for shared device environments.

EA Structure and True-Up Mechanics

Within an EA, introducing F1 or F3 alongside existing E3 creates a multi-product true-up scenario. The mechanics are straightforward — each product category is true-up independently — but the reporting and governance requirements are more complex. Ensure your software asset management tooling tracks frontline worker licence consumption separately. For guidance on the overall M365 true-up mechanics, see our M365 true-up guide.

Industry-Specific Patterns

Frontline licensing requirements vary significantly by industry. Understanding the typical patterns for your sector reduces the time needed for internal analysis:

Retail (Store Associates)

The archetypal F1 use case. Store associates typically need Teams for shift coordination, Shifts for scheduling, and basic communication tools. Desktop Office is not used; email is rarely the primary communication channel; shared devices are the norm. F1 is appropriate for 85–95% of retail frontline populations. Supervisors and store managers who create reports, manage spreadsheets, and have dedicated devices may warrant F3.

Manufacturing and Logistics (Floor and Warehouse Workers)

Similar F1 profile for floor and warehouse operatives. The exception is supervisors and quality assurance roles who may need Excel for production data analysis — these warrant F3 or E3 depending on complexity. Operations managers coordinating across sites typically need E3 and should not be counted in the frontline population at all.

Healthcare (Non-Clinical Staff)

Healthcare frontline licensing is complicated by compliance requirements. For clinical staff, the healthcare-specific Microsoft 365 for Healthcare SKUs and compliance requirements may override the standard frontline framework. For non-clinical frontline staff (porters, catering, cleaning, reception), F1 is typically appropriate. Clinical staff communicating about patient care via Teams may have specific compliance requirements (HIPAA, NHS DSP Toolkit) that affect the minimum licence tier.

Hospitality and Field Services

Hotel staff, field engineers, and home care workers are typically strong F1 or F3 candidates. Field engineers who access complex systems, generate reports, or use custom PowerApps may warrant F3 for the included Power Apps entitlement. Customer-facing staff with primarily communication and scheduling needs are F1 candidates.

Teams Essentials: The Alternative for Smaller Frontline Populations

For organisations with smaller frontline populations (under 300 workers) or where frontline workers are not part of the EA, Microsoft Teams Essentials (£3.40/user/month standalone) provides a lower-cost alternative to F1 within the EA. Teams Essentials is not an EA product — it is a Microsoft 365 Business subscription — and does not include M365 compliance or security integration. For frontline populations that are fully within your EA governance and identity framework, F1 is the right product. Teams Essentials is an option only for fully separate operational entities.

Negotiating the Transition Into Your EA

Moving from E3 to F1/F3 for your frontline population is a SKU rationalisation that Microsoft account teams will attempt to slow or complicate. The standard objections are: (a) "F1 doesn't meet your compliance requirements" — test this claim against your actual compliance controls; (b) "transition costs make it not worth it" — model the 3-year cost differential, which almost always overwhelms transition costs; (c) "we can give you a better E3 discount instead" — an E3 discount of 15% still results in a per-user cost of £23.29/month versus F1 at £2.00. There is no discount path on E3 that closes the gap to F1 for genuinely frontline-appropriate users.

The transition should be timed to your EA renewal event. Mid-term SKU changes can be executed but are less commercially advantageous — Microsoft will credit the unused E3 period at a discounted rate while charging full F1/F3 from the transition date. At renewal, the full population can be rebasined cleanly.

For the broader M365 optimisation context at renewal, see our guides on reducing M365 costs at renewal and M365 licence harvesting. For M365 overall structure, see the M365 Enterprise Licensing Guide.

Quantifying the Savings Before Your Renewal

Before entering your renewal negotiation, build a precise frontline SKU model. The inputs are: (1) current frontline headcount by role type; (2) device assignment model (shared vs. personal); (3) current licence type and per-unit cost; (4) F1/F3/E3 eligibility classification by role. The output is a 3-year cost differential that serves as your anchor in the renewal negotiation.

In a recent retail engagement, we identified 6,800 store associates incorrectly classified on M365 E3 within the client's EA. The 3-year cost of moving these users to F1 was £489,600. The current E3 cost was £6.69M. The differential — £6.2M over 3 years — more than justified a dedicated frontline licence renegotiation as part of the EA renewal process. The client achieved the transition in the renewal cycle, saving £1.97M annually against their prior run rate.

This calculation is available to every enterprise with a significant frontline workforce. The question is not whether the saving exists — it almost certainly does. The question is whether your renewal negotiation team has the independence and expertise to identify it and execute against it. See our M365 Optimisation service for how we approach this systematically.