Why Frontline Licensing Is More Complex Than It Looks

Microsoft positions F1 and F3 as the simple, affordable options for the non-desk workforce. In practice, the decision between F1 and F3 — and whether some frontline populations should instead carry E3 — involves nuanced assessments of communication needs, device ownership models, compliance obligations, and integration with enterprise workflows.

Organisations with large frontline populations — retail, manufacturing, healthcare, logistics, construction, hospitality — face disproportionate budget pressure from Microsoft's 2026 price increases. Frontline SKUs are absorbing some of the largest percentage increases in the July 2026 pricing update, and those organisations that previously negotiated Level B, C, or D EA discounts have lost that buffer through Microsoft's November 2025 discount tier removal. The combined effect for some enterprises is an effective cost increase exceeding 40 percent.

Getting the F1 versus F3 decision right, at scale, across tens of thousands of frontline users, is now a material financial decision — not just an IT configuration question.

The M365 SKU Landscape: Where F1 and F3 Fit

Microsoft's M365 SKU stack for enterprise spans E1, E3, E5, and E7 — with E7 as the current top SKU, bundling advanced AI, security, and compliance capabilities previously sold as premium add-ons above E5. Below E1 sit the frontline worker SKUs: F1 and F3.

F1 and F3 are specifically designed for workers without a fixed office workstation — employees who interact with customers, patients, products, or the public. They are not a cost-reduced version of the E-series; they are architecturally different SKUs with different use rights, device access models, and productivity assumptions.

F1: The Entry-Level Frontline Plan

Microsoft 365 F1 is designed for workers who need lightweight communication and task management without email or Office application access. The plan includes Microsoft Teams for messaging and video, SharePoint for document access, Planner for task tracking, and 2 GB of OneDrive storage. It explicitly excludes a mailbox — users on F1 cannot send or receive email through Microsoft infrastructure — and includes no desktop Office applications.

F1 licensing is limited to web and mobile access only. Users cannot install Office applications on a device under F1 use rights. This distinction matters significantly for device management: F1 users accessing company resources on personal devices operate under mobile application management (MAM) policies rather than full mobile device management (MDM). For Intune-based full MDM enrollment and management, F3 or E-series licensing is required.

The current pre-July 2026 list price for F1 is $2.25 per user per month. From July 1, 2026, the list price increases to $3.00 per user per month — a 33 percent increase. Under NCE annual commit, a discount of up to 5 percent applies. Under NCE monthly commit, no discount applies and list price is charged.

F3: The Full-Featured Frontline Plan

Microsoft 365 F3 delivers a materially richer capability set. In addition to everything in F1, F3 includes the full Office suite (Word, Excel, PowerPoint, OneNote) installable on up to 5 devices, Outlook with a 2 GB mailbox, Power Automate and Power Apps within the M365 context, Teams Phone capability, and Windows 11 Enterprise licensing rights where applicable.

F3 users can install and use desktop Office applications, making them suitable for supervisory or team lead roles who need to edit reports, manage schedules in Excel, or correspond via email. F3 also unlocks full Intune MDM management capabilities, relevant for organisations that need to enforce device compliance policies on frontline-owned or company-owned shared devices.

The current pre-July 2026 list price for F3 is $8.00 per user per month. From July 1, 2026, F3 increases to $10.00 per user per month — a 25 percent increase. EA standard discounts are now 10 to 20 percent off list (down from historical 15 to 25 percent), meaning a negotiated F3 EA price post-July 2026 will typically land in the $8.00 to $9.00 per user per month range depending on agreement scale and leverage.

How many of your frontline users are on the wrong SKU?

Our Microsoft licensing advisory team has right-sized 50,000+ frontline seats across 20+ engagements.
Request a Review →

Feature-by-Feature Comparison: F1 vs F3

Communication and Collaboration

Both F1 and F3 include Microsoft Teams for chat, channels, meetings, and shift scheduling via Teams Shifts. The distinction at the communication layer is email. F1 includes no Exchange mailbox — users cannot send or receive email. If your frontline workers need to communicate externally with customers, vendors, or healthcare counterparts via email, F1 is insufficient and F3 is required. F3 includes a 2 GB Outlook mailbox with full Exchange Online capabilities.

Teams Phone — the Microsoft calling solution integrating PSTN capabilities into Teams — is available under F3 but not F1. Organisations deploying Teams Phone for supervisory or store manager roles within the frontline tier must license those users on F3 as the minimum qualifying SKU.

Office Application Access

This is one of the most significant dividing lines between F1 and F3. F1 provides access to Office web apps only — Word Online, Excel Online, and PowerPoint Online in the browser. No desktop application installation rights are included.

F3 includes full Office application installation rights for up to 5 devices. For frontline supervisors who manage schedules in Excel, write shift handover reports in Word, or maintain operational documentation in PowerPoint, the absence of desktop applications under F1 is a functional gap. In practice, many organisations incorrectly assign F1 to team leads who clearly require F3 capabilities, creating a compliance exposure when Microsoft audits use rights against license assignments.

Device Management and Security

F1 users can be managed via Intune Mobile Application Management (MAM), which wraps apps on personal devices in policy-controlled containers without full device enrollment. This is appropriate for bring-your-own-device frontline workers accessing Teams and SharePoint on a personal phone.

F3 enables full Intune MDM capabilities — device enrollment, compliance policies, conditional access enforcement, and remote wipe. For shared device scenarios common in retail and manufacturing (where multiple workers share a single dedicated device per shift), F3 provides the complete Intune shared device management framework including dedicated device mode for Teams.

Power Platform Access

F3 includes Power Apps for Microsoft 365 and Power Automate for Microsoft 365 use rights within the M365 context. This enables frontline teams to use — though not build — simple Power Apps applications that surface in Teams, and to run Power Automate flows triggered within M365 services. F1 does not include Power Platform use rights.

For organisations deploying custom-built frontline apps to store associates or warehouse workers through Power Apps and surfacing them in Teams, F3 is the minimum qualifying license for frontline users who need to run those applications. F1 users cannot access Power Apps applications under their license terms.

Windows Enterprise Rights

F3 includes Windows 11 Enterprise upgrade rights, which is relevant for organisations deploying company-owned Windows devices to frontline workers. F1 does not include Windows upgrade rights. For scenarios where frontline workers use shared kiosks or dedicated Windows devices, this distinction has device licensing implications beyond the M365 SKU cost itself.

The 2026 Pricing Changes: What You Need to Know Before July 1

Microsoft's July 1, 2026 price increase represents the most significant pricing change to the frontline SKU tier since F-series plans were introduced. Understanding the full financial impact requires looking beyond the headline percentage increases to the compounding effects of discount tier removal.

The Headline Increases

F1 moves from $2.25 to $3.00 per user per month — a 33 percent list price increase. F3 moves from $8.00 to $10.00 per user per month — a 25 percent list price increase. These increases apply from July 1, 2026 regardless of EA renewal date for new orders placed after that date.

The Discount Removal Compounding Effect

In November 2025, Microsoft removed volume-based EA discount tiers B, C, and D. All EA customers now start at Level A pricing, with negotiated discounts on a case-by-case basis rather than automatic volume tier discounts. An organisation that previously held Level D pricing (the highest volume tier, typically with 15 to 25 percent discount) on F1 at $2.25 list was paying approximately $1.69 to $1.91 per user per month. Post-July 2026, starting at Level A and negotiating 10 to 15 percent discount on the new $3.00 list, the same organisation will pay $2.55 to $2.70 per user per month — an effective increase of 34 to 60 percent.

The financial exposure is largest for organisations with high densities of F1 users and the strongest historical EA discount positions.

NCE Implications

Microsoft's New Commerce Experience (NCE) framework applies to frontline SKUs. Under NCE monthly commit, F1 and F3 are charged at full list price with no discount available. Under NCE annual commit, up to 5 percent discount applies. Organisations still on legacy EA structures have a window to renegotiate terms before transitioning to NCE. Once on NCE, the annual commit at up to 5 percent is the ceiling for frontline SKU discount without an EA negotiation.

How to Decide: F1, F3, or E-Series for Each Frontline Role

The Right Questions to Ask

The F1 versus F3 decision should be made role by role, not by population average. For each distinct frontline role in your organisation, the key questions are: Does this role require email communication — internal or external? Does this role need to create or edit documents using Office applications? Does the device assigned to this role need full MDM management? Does this role use Power Apps or Power Automate?

If any answer is yes, that role requires F3 as a minimum. If all answers are no — the role is purely a consumer of Teams communication, SharePoint documents, and task lists — F1 is defensible.

Role Mapping by Industry

In retail, floor associates and cashiers who use Teams for shift communication and access the company intranet through SharePoint are strong F1 candidates. Store managers who manage shift schedules in Excel, communicate with district management via email, and run reports in Word are F3 candidates. In manufacturing, production line workers performing digital checklist tasks via a Teams-embedded app (built in Power Apps) require F3 because Power Apps use rights are not included in F1. Quality supervisors who document findings in Excel and email reports externally are also F3. In healthcare, clinical assistants using Teams Shifts for scheduling and SharePoint for procedure documents may fit F1 if they have no email requirement. Charge nurses or ward supervisors communicating with external providers or managing documentation in Word and Excel need F3 or E3 depending on compliance obligations.

When to Consider E3 Instead

The F-series is designed for workers without a fixed office workstation as a primary characteristic. Microsoft's use of rights documentation defines a frontline worker as someone who does not use a PC or workstation as their primary work interface. If a role involves a dedicated, personal computing device — even a laptop shared between a small team — that role may not qualify as a frontline worker under Microsoft's licensing definitions and may require E1 or E3.

Additionally, any role requiring SharePoint Online storage beyond F-series limits, advanced compliance features (eDiscovery, audit logs, retention policies), or Entra ID P1 or P2 security features needs E3 or higher. E3 currently sits at $36 per user per month (rising to $39 from July 2026). For frontline roles that cross into office-worker territory, the additional cost of E3 versus F3 may be justified by capability requirements — and is certainly preferable to a compliance risk from improper F-series assignments.

Are your frontline workers on the right SKU tier?

We run role-based frontline licensing reviews that identify misassignments and negotiation opportunities across F1, F3, and E3.
Explore Microsoft Advisory →

Negotiating Frontline SKUs in an Enterprise Agreement

Frontline SKUs are frequently treated as secondary line items in EA negotiations, with the commercial focus placed on E3, E5, E7, and Azure. This is a mistake. At scale, frontline SKU optimisation and discounting can represent larger absolute savings than marginal improvements on the enterprise tier.

Use Q4 Leverage Effectively

Microsoft's fiscal year ends June 30. We are now in Q4 (April through June), the period of maximum field rep incentive to close and discount. This is the best window to negotiate frontline SKU pricing within an EA renewal or amendment. Field reps who have front-loaded E7 upsell conversations will still need to close frontline seat counts, and negotiating hard on F1 and F3 unit economics is far easier in Q4 than at any other time.

Anchor on Competitive Alternatives

Google Workspace Frontline Starter and Frontline Standard provide genuine competitive alternatives to Microsoft F1 and F3. Frontline Starter at approximately $2 per user per month undercuts F1 even at post-July 2026 pricing. Frontline Standard at approximately $6 per user per month competes directly with F3. Using Google Workspace pricing as an explicit anchor in EA negotiations has proven effective in driving Microsoft field reps to improve frontline SKU terms. The credibility of this anchor requires documented evaluation evidence — Microsoft responds to concrete pilot deployment plans far more than hypothetical threats.

Volume Concentration Across SKUs

Negotiating frontline seats as part of the total EA seat count creates volume concentration leverage. An organisation with 10,000 E3 seats and 15,000 F1 seats that presents them as a single 25,000-seat EA conversation has significantly more negotiating leverage than one that treats frontline licensing as a separate procurement. Microsoft's commercial team values total seat commitment — concentrating volume in a single EA maximises the buyer's position.

True-Up Strategy for Frontline Populations

Frontline workforces are frequently subject to significant headcount fluctuations — seasonal workers, temporary staff, high turnover. The EA True-Up mechanism requires reporting the highest seat count over the agreement period. Organisations that sign up for a fixed frontline seat count above their average headcount are paying for phantom licenses through the True-Up.

The correct strategy is to negotiate a base frontline count at or slightly below average headcount and rely on the True-Up mechanism to capture seasonal peaks, rather than pre-committing to a peak count year-round. Microsoft field teams often push customers to overcommit on frontline seats at renewal; resist this and align the EA commitment to modelled average usage.

Copilot and AI Considerations for Frontline Workers

Microsoft 365 Copilot — priced at $30 per user per month as a standalone add-on, or included in M365 E7 for the enterprise tier — has a distinct frontline variant: Copilot for Microsoft 365 Frontline Workers. This is a separate, lower-priced AI capability designed for F-series users, focusing on Teams-embedded AI assistance, shift briefing summarisation, and task prioritisation rather than the full knowledge-worker Copilot experience.

The frontline Copilot is currently in limited availability and is not available as a standalone add-on on F1 or F3. Organisations planning AI deployments across frontline populations should clarify the licensing availability and terms for frontline Copilot before committing to E7 upgrades for their office workers with the expectation that frontline AI capability will follow automatically. The AI roadmap for frontline workers diverges from the E-series Copilot path.

Common Mistakes in Frontline Licensing

Assigning F1 to team leads and supervisors: The most common compliance risk in frontline licensing. Supervisory roles almost universally require email and desktop Office, which are F3 minimum requirements. Assigning F1 to supervisors for cost reasons creates an audit exposure that can exceed the licensing savings if Microsoft performs an effective licensing review.

Over-assigning F3 to pure communication workers: The reverse problem is equally common. Floor workers, warehouse pickers, and frontline healthcare assistants who only use Teams Shifts and SharePoint document access are paying more than double the correct license cost if assigned F3 when F1 is the right fit.

Ignoring device-type constraints: F1 is for web and mobile access only. If your frontline workers are accessing Office applications from dedicated Windows kiosks, those users may require F3 or E-series licenses depending on how the applications are accessed — web vs. installed.

Treating seasonal peaks as steady-state commitments: EA True-Up mechanics mean organisations that pre-commit to peak frontline headcount overpay through the entire agreement term. Model average headcount, not peak, for the base EA commitment.

Not reviewing frontline eligibility: Some roles that have historically been licensed as office workers (E3) qualify as frontline workers under Microsoft's definition and could be re-classified to F3 or F1 at renewal with significant cost savings. A proper role-based licensing review typically identifies 5 to 15 percent of enterprise seats that are eligible for frontline classification.

Six Practical Recommendations

1. Conduct a role-based frontline audit before your next renewal: Map every distinct frontline role against F1 and F3 use rights. Identify current misassignments in both directions. Quantify the cost impact at the July 2026 pricing. This audit is the foundation of any credible commercial conversation with Microsoft.

2. Act before July 1, 2026 if your EA allows: Organisations with EA renewals in the second half of 2026 may be able to negotiate an early renewal to lock in current F1 ($2.25) and F3 ($8.00) pricing before the July 1 increases take effect. Calculate whether the cost avoidance justifies the renewal timing adjustment.

3. Use Q4 (April to June) to negotiate: Microsoft's field reps are under maximum commercial pressure to close in Q4. Frontline SKU pricing, volume commitments, and True-Up terms are all more negotiable in this window than at any other point in the fiscal year.

4. Introduce Google Workspace as a credible anchor: Prepare a documented competitive evaluation of Google Workspace Frontline for your negotiation. Even if Google is not genuinely in consideration, the pricing evidence creates negotiating leverage that Microsoft field reps are responsive to during Q4.

5. Negotiate frontline seats as part of total EA volume: Do not separate frontline licensing from the enterprise tier conversation. Total seat commitment creates leverage across all SKU tiers. A 25,000-seat EA negotiation is materially stronger than two separate 10,000 and 15,000 seat conversations.

6. Engage independent Microsoft EA negotiation specialists before the renewal: The gap between organisations that negotiate Microsoft EA frontline terms independently and those that engage specialist advisors is typically 12 to 20 percent in effective unit pricing. At scale frontline populations, this difference represents material annual savings that exceed advisory fees by a multiple of three to five times.

Stay Ahead of Microsoft Pricing Changes

Get quarterly Microsoft licensing intelligence — pricing updates, SKU changes, and negotiation tactics — delivered directly to your inbox.

MA
Morten Andersen
Co-Founder, Redress Compliance

Morten Andersen is a Co-Founder of Redress Compliance and a specialist in Microsoft Enterprise Agreement strategy, frontline licensing, and M365 cost optimisation. He has led 200+ Microsoft licensing engagements across EMEA and North America, working exclusively on the buyer side. Redress Compliance is Gartner recognised and has completed 500+ enterprise software licensing engagements.

Connect on LinkedIn →