Editorial photograph of an enterprise frontline workforce using shared devices, with a Microsoft 365 license assignment overlay
Guide · Microsoft · F SKU

Microsoft 365 F SKU. Frontline licensing decoded.

Microsoft 365 F licenses cover the frontline workforce at 60 to 80 percent below the E SKU equivalent. The buyer side framework that maps eligibility, designs the right F SKU mix, avoids the most expensive deployment traps, and captures 30 to 55 percent unit savings.

Read the Framework Microsoft Hub
30 to 55%Unit savings vs E SKU
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Microsoft 365 F licenses are designed for the frontline workforce. The frontline workforce is defined as workers who use shared or kiosk devices, do not have a primary office desk, and need limited productivity functionality. The F SKU price reflects the reduced functional scope.

The unit price runs 60 to 80 percent below the E3 SKU equivalent. The savings on a retail, manufacturing, healthcare, hospitality, or logistics workforce of 10,000 plus frontline employees compound into the millions of dollars per year.

This guide reads the F SKU mix from the buyer side. Pair it with the EA renewal playbook, the E5 negotiation tactics, the M365 license optimizer, and the Microsoft Hub.

Key Takeaways

What a CIO needs to know in 90 seconds

  • F SKUs are for the frontline workforce only. Microsoft defines frontline as shared device, kiosk, or non desk based workers.
  • The F SKU mix runs F1, F3, F5 Security, and F5 Compliance. The mix sits inside the broader Microsoft 365 lineup.
  • F1 has no Office apps. It runs Teams, Exchange Online Kiosk, SharePoint, OneDrive, and basic services.
  • F3 adds web Office, Stream, Power Apps for frontline. It is the typical frontline default.
  • F5 Security and F5 Compliance are F SKU add ons. They mirror the E5 Security and E5 Compliance scope at frontline price.
  • The 300 device cap on shared device sign in matters. Microsoft tracks F SKU shared device sign in patterns.
  • F SKU savings on a 10,000 frontline workforce often exceed two million dollars per year.

Why F SKUs exist

Microsoft introduced the F SKU line to address customer concerns about over licensing frontline workers. Retail clerks, factory operators, warehouse pickers, hospital nurses, hotel housekeepers, and restaurant staff do not use a primary office laptop. The E SKU functional scope is wasted on these workers. The F SKU fits the actual usage pattern.

Four frontline workforce segments

  • Retail. Store associates, cashiers, fulfillment staff.
  • Manufacturing. Production line operators, warehouse staff, drivers.
  • Healthcare. Nurses, technicians, ward clerks, allied health.
  • Hospitality. Front desk, housekeeping, food service.

Microsoft 365 F SKU map

The F SKU line includes three core licenses plus two F SKU specific add ons. The three core licenses cover the productivity scope. The two add ons cover the security and compliance scope for customers who need parity with the E5 tier. The map below shows the 2026 functional scope at a high level.

Microsoft 365 F SKU map in 2026

SKUList price (USD per user per month)Office appsEmailNotable inclusions
F1$2.25NoneExchange Online KioskTeams, SharePoint, OneDrive, Yammer
F3$8Web and mobile onlyExchange Online Plan 1Stream, Power Apps for frontline, Forms
F5 Security$10 add onn/an/aDefender for Endpoint Plan 1, Defender for Office Plan 1
F5 Compliance$10 add onn/an/aInformation Protection, Insider Risk, eDiscovery
F5 Security plus Compliance$16 bundledn/an/aCombined add on at bundle discount

F1 versus F3

F1 has no Office apps and no Exchange mailbox beyond a 2 GB kiosk mailbox. F3 adds web and mobile Office, a 2 GB mailbox, and the broader collaboration scope. Most frontline workforces need F3 rather than F1 because the frontline app pattern increasingly requires Outlook web access and Teams calling.

Frontline eligibility rules

Microsoft defines frontline workforce in the Product Terms and the Microsoft Volume Licensing Customer Agreement. The eligibility rule turns on the work pattern. Workers must not use the F SKU as a primary information worker license. The rule is enforced at the EA renewal and through usage telemetry.

Five eligibility tests Microsoft applies

  • No primary device. The worker does not have an assigned laptop or desktop.
  • Shared device pattern. Sign in patterns show shared kiosk or device usage.
  • Limited Office usage. Office app telemetry confirms light usage.
  • Job role match. The role description fits the frontline worker definition.
  • Headcount mix. F SKU share fits the workforce demographics.

Three eligibility traps to avoid

  1. Office worker mis assigned to F SKU. Information workers must be on E SKUs.
  2. Hybrid worker mis assigned. A worker who splits between frontline and office may need E.
  3. Persistent device pattern. A worker who uses one device persistently signals E.

Common deployment traps

Frontline deployments fail at four recurring points. The buyer side review catches all four before the EA renewal closes. Each one costs money or compliance exposure if left unfixed.

Four F SKU deployment traps

  • Headcount over assignment. Office workers misclassified as frontline.
  • Wrong F SKU tier. F1 assigned where F3 or full E is needed.
  • Missing F5 add on. Security and compliance gaps on the frontline estate.
  • Shared device sign in failure. Identity policy not configured for shared device F1 access.

F SKU plus add ons

The F SKU sits inside the wider Microsoft 365 lineup. Customers can add Power BI, Power Apps, Visio, Project, and Teams Phone on top of F SKUs. The add on availability is narrower than on E SKUs. The buyer should map the planned add ons before committing to the F SKU mix.

Add ons available on F SKU in 2026

Add onF1F3F5 SecurityF5 Compliance
Teams PhoneAllowedAllowedAllowedAllowed
Power BI ProAllowedAllowedAllowedAllowed
Power Apps per userAllowedAllowedAllowedAllowed
Visio Plan 1 or 2LimitedAllowedAllowedAllowed
Project Plan 1 or 3LimitedAllowedAllowedAllowed
Defender for Endpoint Plan 2Allowed via add onAllowed via add onIncluded if F5 Secn/a

The Copilot question for frontline

Microsoft 365 Copilot is not available on F SKUs in 2026. Microsoft positions Copilot as an information worker tool requiring Microsoft 365 E3 or E5 as the base license. Customers who want Copilot for frontline workers must move those workers to E SKUs or wait for a Microsoft frontline AI product line.

Migration from E to F

The migration from E to F runs as a workforce segmentation project. The work pulls payroll data, role descriptions, device assignment data, and Office usage telemetry. The output is a tagged headcount file that maps each user to the correct M365 SKU at the next EA anniversary.

Six step migration workflow

  1. Pull payroll headcount. Job titles and department codes.
  2. Pull device assignment. AD and Intune data on primary device assignment.
  3. Pull Office telemetry. Light usage flags from M365 admin center.
  4. Map roles to SKUs. Build the role to SKU translation table.
  5. Run the financial model. E to F unit savings on the tagged headcount.
  6. Negotiate the EA amendment. Change the SKU mix at the EA anniversary.

What to do next

The eight step checklist below moves an F SKU deployment from rumor to documented enrollment. Open it nine months before the EA anniversary. The earlier the work starts, the cleaner the segmentation and the deeper the recovery.

  1. Define frontline scope. Document which roles qualify.
  2. Pull the four data sets. Payroll, device, Office telemetry, identity.
  3. Build the role to SKU table. Map each role to F1, F3, E3, or E5.
  4. Add the F5 add ons. Decide F5 Security and F5 Compliance scope.
  5. Plan the identity configuration. Shared device sign in policies on F1.
  6. Model the financial impact. Three year savings projection.
  7. Negotiate the EA amendment. Change the SKU mix at the anniversary.
  8. Schedule the audit hygiene review. Document the eligibility position.

Frequently asked questions

Who qualifies for Microsoft 365 F licenses?

Frontline workers qualify. Microsoft defines frontline as workers who do not have a primary assigned device, use shared or kiosk devices, and have limited Office usage patterns. Typical roles include retail associates, factory operators, warehouse staff, drivers, nurses, technicians, ward clerks, and hotel front desk and housekeeping. Information workers do not qualify and must remain on E SKUs.

What is the difference between F1 and F3?

F1 has no Office apps and only a 2 GB kiosk mailbox. F3 adds web and mobile Office, a 2 GB mailbox, Stream, Power Apps for frontline, and Forms.

F3 fits the most common frontline use case where workers need light Outlook on web access and basic productivity. F1 fits kiosk only roles where the worker does not need an email mailbox at all.

Can I add Copilot to an F SKU?

No. Microsoft 365 Copilot is not available as an add on to F SKUs in 2026. Microsoft positions Copilot as an information worker tool requiring Microsoft 365 E3 or E5 as the base license. Customers who want Copilot for frontline workers must move those workers to E SKUs first or wait for a Microsoft frontline AI product line.

How much can a frontline organization save by moving from E to F?

The unit price gap runs at 60 to 80 percent between F SKUs and E SKUs. A 10,000 frontline workforce running on E3 at full price will spend roughly 4.5 million dollars per year.

The same workforce on F3 at full price spends roughly 1 million dollars per year. The annual saving runs at approximately 3.5 million dollars before any further discount.

What are the F5 Security and F5 Compliance add ons?

F5 Security and F5 Compliance are F SKU specific add ons that mirror the E5 Security and E5 Compliance scope. F5 Security includes Defender for Endpoint Plan 1 and Defender for Office Plan 1. F5 Compliance includes Information Protection, Insider Risk, and eDiscovery. Each add on runs at 10 dollars per user per month list, or 16 dollars combined.

How does Microsoft enforce frontline eligibility?

Microsoft monitors shared device sign in patterns, Office app telemetry, and headcount mix at the EA renewal. The eligibility rules sit in the Product Terms and the Microsoft Volume Licensing Customer Agreement. Customers who mis assign information workers to F SKUs face a true up at the EA anniversary plus potential audit exposure on the deployed estate.

How Redress engages on F SKU deployment

Redress runs the F SKU work as a 10 to 14 week segmentation engagement. The work pulls the four core data sets, builds the role to SKU translation, models the financial impact, and negotiates the EA amendment. The deliverable is a documented frontline policy, a tagged headcount file, and a 24 month watch list against eligibility drift.

Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.

Optimize your Microsoft 365 license mix in under five minutes.
Open the M365 License Optimizer →
White Paper · Microsoft

Download the Microsoft EA Renewal Playbook.

A buyer side framework for the next Microsoft EA renewal. F SKU and E SKU benchmarks, frontline segmentation rules, true up arithmetic, and the negotiation calendar Microsoft does not want customers to run.

Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for enterprise customers running Microsoft 365 at scale across frontline and information worker estates.

Microsoft EA Renewal Playbook

Open the white paper in your browser. Corporate email only.

Open the Paper →
30 to 55%
Unit savings vs E SKU
5 SKUs
In the F SKU family
9 months
EA negotiation lead time
500+
Enterprise clients
100%
Buyer side

We segmented 22,000 frontline workers across 480 retail stores, mapped 14,800 to F3, 2,400 to F1 for kiosk only roles, kept 4,800 store managers on E3, modeled a 4.2 million dollar annual unit saving, and renegotiated the EA amendment with a documented eligibility policy.

Director of Workplace Technology
Global retail group
More Reading

More from this practice.

Microsoft Hub →
Microsoft EA Renewal Playbook
Microsoft · Landing
Microsoft EA Renewal Playbook
The EA renewal framework.
22 min read
E5 Negotiation Tactics
Microsoft · Guide
E5 Negotiation Tactics
E5 specific negotiation moves.
20 min read
M365 Copilot Licensing
Microsoft · Article
M365 Copilot Licensing
Copilot licensing framework.
16 min read
M365 License Optimizer
Microsoft · Tool
M365 License Optimizer
Interactive optimization tool.
10 min read
Audit Microsoft License Usage
Microsoft · Article
Audit Microsoft License Usage
Step by step optimization workflow.
18 min read
Editorial photograph of enterprise contract negotiation strategy

Your frontline workforce is your envelope.

We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.

Microsoft licensing intelligence, monthly.

F SKU eligibility enforcement patterns, frontline AI product line announcements, EA renewal movements, and the wider Microsoft commercial signals across every cycle.