Microsoft 365 F1 vs F3 for frontline workers. The mailbox decides most of it.

F1 and F3 differ mainly by an Exchange mailbox, and F1 costs 30 percent of F3 at list. Admins default to F3, so check who reads email before you renew and move the rest to F1.

What is the difference between Microsoft 365 F1 and F3?

F1 gives a frontline worker a secure identity, Entra ID, Teams, SharePoint and read only Office on web and mobile, with no Exchange mailbox rights. F3 adds a 2 GB Exchange Online mailbox, editing in the web and mobile Office apps, and Windows 11 Enterprise E3. For most roles the mailbox is the part that decides it.

Both are frontline plans for deskless, shift based staff, and neither includes desktop Office. The gap between them is narrower than the price difference suggests, which is why the default assignment is worth a second look.

Why does the mailbox settle most F1 and F3 decisions?

F1 carries no right to an Exchange Online mailbox at all. Microsoft provisions an Exchange Kiosk service plan with F1 so the Teams calendar works, but the F1 user is not entitled to use the mailbox it creates. An F1 user can receive limited communication through Teams and cannot run a standard corporate inbox.

So if a role needs email, it needs F3 or higher and the decision is closed. The split is worth auditing because the reverse case is far more common. Roles get the mailbox because one plan for everyone is simpler to administer, and then they never use it.

What else separates the two plans besides email?

• Editing rights. F1 users can open Word, Excel and PowerPoint files on web and mobile but cannot change them. A supervisor who fills in a shared Excel rota needs F3.
• Windows Enterprise. F3 includes Windows 11 Enterprise E3 rights and F1 does not. If shared Windows terminals rely on Enterprise features through their users' F3 seats, check how those devices would be covered before you move the users.

Which frontline roles fit F1 and which need F3?

Place each role by what it does on shift. If the work needs a secure sign in, Teams and read access to documents, F1 covers it. If the role reads and answers email, or edits documents, it needs F3.

• Shared breakroom kiosks and shop floor terminals. These fit F1 cleanly. The worker needs an identity and Teams, and in the reviews we ran these scenarios were licensed at F3 anyway.
• Warehouse scanner and handheld device roles. F1, where the task is scanning and status updates.
• Store tablets used for forms, rotas and web Office. F3, because the web apps get used for editing and the mailbox gets read.
• Frontline staff who own an inbox. F3. If the role receives external email, the mailbox justifies the higher price.
• Anyone who needs desktop Office. E3, covered in our F3 versus E3 comparison.

How do shared devices affect the license count?

F1 and F3 are per user licenses, so every worker who signs in to a shared terminal needs a frontline license of their own. Count the named users of each kiosk or station, and ignore how many are on shift at once.

The device still matters for capability, since a scanner or breakroom kiosk rarely needs an inbox, and for eligibility.

Who is allowed to hold a frontline license?

Under the Product Terms, a Frontline Worker license may only go to a user who meets at least one of two conditions. Either the user's primary work device has a single screen smaller than 10.9 inches, or the user shares a primary work device with other frontline licensed users during or across shifts.

Microsoft can test this rule in an audit. A frontline plan assigned to an office worker with a dedicated laptop fails it, whatever the role needs. Our F SKU licensing guide covers eligibility in more detail.

What does leaving every frontline worker on F3 cost?

At 2026 list prices, every F3 seat that could be F1 costs an extra $7 per month, or $84 a year. Before July 1, 2026 the gap was $5.75 a month. F1 lists at 30 percent of F3, so each seat you move cuts that seat's cost by 70 percent.

A worked example across both frontline steps

Say a company has 5,000 deskless staff: 1,000 on E3 from the original tenant setup and 4,000 on F3. A usage review keeps 200 on E3 for desktop Office and puts 800 on F3. Mailbox data then shows 1,200 of the 4,800 F3 seats with no read activity for a full quarter, and those go to F1.

The E3 to F3 step saves $278,400 a year (800 seats at $29 a month). The F3 to F1 step adds $100,800 (1,200 seats at $7). Together they cut $379,200 a year at list, with the same 5,000 people licensed.

Why is the F1 saving harder to spot than the E3 to F3 saving?

The E3 to F3 shift is the saving most organizations find, because the gap is visible. It was $36 against $8 a month before the 2026 increase, with desktop Office and a terabyte of storage on one side and neither on the other. Everyone accepts that a warehouse scanner does not need desktop Excel.

The F1 question is harder because the gap is narrow and the capability at stake is one office workers cannot imagine doing without. An inbox feels like a baseline entitlement, so it gets granted by default and never reviewed.

Why we disagree with standardizing all frontline staff on F3

The common advice is to put every frontline worker on F3, because the price gap is small and it avoids reassignment work. We disagree, because the cost compounds. The reassignment effort happens once, while mailboxes and web Office that frontline staff never touch are billed every month.

That overspend grows with headcount in the sectors where frontline populations are largest: retail, manufacturing, logistics and healthcare. The better course is two assignment rules, one for roles that need an inbox and one for roles that do not, reviewed once a year.

The reassignment work is paid once. The unused mailbox is paid every month until someone checks the activity report.

How much is plan uniformity worth?

The administrative argument is reasonable. One frontline plan means one assignment rule, one onboarding path and no reclassification when someone changes role. The mistake is treating that simplicity as free.

At 2026 list, 1,000 F3 seats with unused mailboxes cost $84,000 a year more than F1. A second rule costs far less. Group based licensing in Entra ID, driven by a dynamic membership group on job code, assigns the right plan at onboarding, and dynamic groups need Entra ID P1, which both plans include.

How do you find the F3 seats that should be F1?

Ask one question per role: does this role receive email that it must read to do the job? Whether an inbox would be convenient is beside the point. Mailbox activity data answers the question for existing seats, and roles with zero reads over a quarter are the group to move.

1. Email activity report. In the Microsoft 365 admin center, open Reports, then Usage, then Exchange, and select the Email activity tab. It shows send, receive and read actions and the last activity date per user. Set the period to 90 days and export to CSV.
2. Concealed names. Usage reports hide user names by default. A global admin can switch this off in the org settings for reports, so the export can be joined to HR job codes.
3. Microsoft 365 Apps usage report. Shows who uses Word, Excel and PowerPoint, split by platform including web and mobile. Confirm with their managers whether those active users change files or only read them, since F1 allows viewing only.
4. Process check. List the business processes that email frontline staff today, such as payslips, rota changes or training notices. Each must move to Teams or SharePoint news before those staff go to F1.

Run this inside the same review that handles the E3 to F3 shift. Both are placement changes, so the seat count stays the same and the saving survives a headcount freeze. The plan mix across all three suites is set out in our E3 against E5 against F3 guide.

What happens to a user's mailbox when they move from F3 to F1?

The user loses the right to use it. The Exchange Kiosk plan stays provisioned for the Teams calendar, so the mailbox object may remain, but an F1 user is not entitled to read or send from it. Decide what happens to the mail before you switch.

What mistakes do organizations make with the F3 to F1 switch?

• Moving a role on job title alone. A title such as "store associate" can hide a subgroup that handles supplier email. Check activity per user, then decide per role.
• Using a shared mailbox as a workaround. Microsoft requires anyone who opens a shared mailbox to have a licensed Exchange Online mailbox of their own. F1 users do not qualify.
• Forgetting retention. Mail in an F3 mailbox may fall under your retention or legal hold rules. Agree with compliance how it is kept before the license changes.
• Leaving the old rule in place. If onboarding still assigns F3 to every new starter, the misplaced seats return within a year.

Can F1 and F3 users run desktop Office or Copilot?

Neither plan includes desktop Office, so neither is a knowledge worker seat, and assigning them to office based roles creates a capability problem instead of a saving. Both plans do now qualify as base plans for the Microsoft 365 Copilot add on, at $30 per user per month.

Does a frontline Copilot pilot still need an upgrade to E3?

No longer. When Copilot launched for enterprises, only E3 and E5 qualified, so a frontline pilot carried a base plan change before the add on line landed. Microsoft's current prerequisite list includes F1 and F3.

Price the pilot as $30 a month on a $3 or $10 seat. Our Copilot license requirements guide lists every qualifying plan.

Is a 2 GB mailbox enough for frontline staff?

For shift communication, usually yes, but it is not built for document retention. A role with archive requirements is not an F3 role.

What did our frontline license reviews show in 2024 and 2025?

Across roughly 15 to 25 frontline licensing reviews in 2024 to 2025, the F1 to F3 split was almost always skewed toward F3. In those reviews, 20 to 40 percent of F3 seats belonged to roles that never opened the mailbox, the one capability that separates the two plans for most users.

• F1 was underused by default. Admins assigned F3 for simplicity, not because anyone had tested the roles.
• Shared devices were the most misplaced group. Kiosk and shared device scenarios fit F1 cleanly and were licensed at F3 anyway.
• The F3 line was already large. At the old list of $8, against $36 for E3 and $57 for E5, a big deskless population made F3 a material cost before anyone looked at F1.

Neither pattern reflected a considered decision. Before assigning, read Microsoft's frontline licensing options together with the plan service description, because the service description settles what a plan actually carries.

What will Microsoft or your reseller say about moving seats to F1?

Expect some resistance, since each F3 seat moved to F1 removes 70 percent of that seat's revenue at list. These are the lines we hear, with replies that hold up.

"F1 users cannot get email and they will complain."

Agree, and show the data. You are moving only roles with zero reads over a quarter, after the processes that emailed them have gone to Teams. Anyone who needs an inbox stays on F3.

"Seat changes have to wait for the anniversary."

Reduction rights differ by agreement, so ask exactly where yours allows the change and plan the F1 quantities into that date. Our guide to the 2026 Microsoft 365 price increase covers renewal timing.

"Keep them on F3 so they are ready for Copilot."

F1 is on Microsoft's own list of qualifying base plans for the Copilot add on, so a Copilot pilot gives no reason to hold seats on F3. Ask the account team to show the prerequisite that says otherwise.

"Your shared Windows devices will lose Windows Enterprise."

Only users who sign in to shared Windows PCs that depend on Enterprise features are affected. Handheld scanners and tablets running Android or iOS need no Windows rights, so list the Windows terminals and settle their coverage separately.

What to do next

1. Pull mailbox activity for every F3 seat. Use a full quarter and list the seats with zero reads.
2. Ask one question per role. Does the work require an inbox to be read, as opposed to an inbox being convenient?
3. Put shared device, kiosk and scanner roles on F1. They fit cleanly and are the group most often misplaced. Move their email processes to Teams first.
4. Price the uniformity. Compare the cost of a second assignment rule with the recurring premium on unused mailboxes.
5. Run it with the E3 to F3 shift. Our license optimizer and the Microsoft practice can run the frontline split with you, and the wider library sits in the Microsoft hub.

Frequently asked questions