Between 20 and 40 percent of F3 seats belonged to roles that never opened the mailbox

Moving deskless staff off E3 onto F3 is the first frontline saving and the one most estates find. There is a second move underneath it that almost nobody makes, because F1 and F3 differ by an inbox and admins default to the one that has it.

Prepared by Redress Compliance · August 16, 2026 · Microsoft advisory. 15 to 25 frontline licensing reviews, 2024 to 2025.

Both are frontline SKUs for deskless staff, capped per user and intended for shift based roles. The difference is narrower than the price gap suggests, which is exactly why the default matters.

• Shared breakroom kiosks and shop floor terminals fit F1 cleanly. The worker needs a secure identity and Teams, not an inbox, and these scenarios were licensed at F3 anyway in the reviews we ran.
• Warehouse scanner and handheld device roles fit F1 where the task is scanning and status updates rather than correspondence.
• Store tablets used for forms, rotas, and web Office fit F3, because the web apps and the mailbox both get used.
• Frontline staff who own an inbox fit F3. If the role receives external email, the mailbox justifies the higher price and there is no argument to have.
• Map the device as well as the person, since shared device scenarios often carry several workers per licence and the capability question follows the device.
• Neither plan is a knowledge worker seat. If the role needs desktop Office, the answer is E3, and that is a different conversation covered in F3 versus E3.

• Neither plan is a knowledge worker seat. No desktop Office, and F1 has no mailbox at all, so assigning them to office based roles creates a capability problem rather than a saving.
• Frontline SKUs are capped per user and intended for deskless and shift based staff, which is a licensing constraint rather than a guideline.
• Copilot does not run on either. A qualifying base plan is required and only E3 and E5 qualify, so any frontline Copilot pilot carries a base plan move before the add on line ever lands.
• F1 email is not a smaller inbox, it is no inbox. Teams messaging is not an Exchange mailbox, and nothing inside the frontline tier changes that.
• Storage is not the deciding factor. The F3 mailbox is 2 GB, which suits shift communication rather than document retention, so a role with archive requirements is not an F3 role.
• Shared device scenarios follow the device population, so count the concurrent workers per terminal rather than the named staff list when sizing kiosks and shop floor stations.

The common advice is to standardise all frontline staff on F3 because the price gap is small and it avoids reassignment work. We disagree, and the arithmetic behind the disagreement is about compounding rather than about any single seat. In the reviews we ran, blanket F3 meant paying for mailboxes and web Office that 20 to 40 percent of frontline staff never touched. The reassignment effort is one time. The overspend on unused mailboxes is permanent, and it compounds across thousands of deskless seats in exactly the industries, retail, manufacturing, logistics, healthcare, where frontline headcount is largest.

This is the second move in a sequence, and the first one is better known. Moving deskless staff off an E3 seat onto F3 is the saving most estates find, because the gap there is visible: $36 against $8 a month, with desktop Office and a terabyte of storage on one side and neither on the other. Nobody argues that a warehouse scanner needs desktop Excel. The F1 question is harder precisely because the gap is narrow and the capability at stake is one most office workers cannot imagine doing without. An inbox feels like a baseline entitlement rather than a licensed feature, so it gets granted by default and never reviewed.

The administrative argument for uniformity is also genuinely reasonable, which is why it wins. One frontline plan means one assignment rule, one onboarding path, and no reclassification when someone moves between roles. That simplicity has a real operational value and the mistake is treating it as free. Priced honestly, it is a recurring payment for administrative convenience, and it should be compared against the cost of maintaining a second assignment rule rather than assumed away. In most estates with meaningful frontline headcount, the comparison does not favour uniformity.

The practical test is narrower than a full persona exercise, which is what makes it worth doing. There is only one question: does this role receive email that it must read to do the job. Not could it, not would it be convenient, but does the work require an inbox. Mailbox activity telemetry answers it directly for existing seats, and the roles that come back with zero reads over a quarter are the population to move. Do it as part of the same review that handles the E3 to F3 shift, since both are placement changes rather than reductions and both survive a headcount freeze. The full plan mix arithmetic sits in E3 against E5 against F3, and the wider library in the Microsoft practice.

Across roughly 15 to 25 frontline licensing reviews, the F1 to F3 split was almost always skewed toward F3:

F1 was underused because admins defaulted to F3 for simplicity rather than by role, and shared device and kiosk scenarios fit F1 cleanly but were licensed at F3 anyway. Neither pattern reflects a considered decision; both reflect the absence of one.

Microsoft sets out the entitlements in its frontline licensing options and the full feature matrix in the plan service description. Read the two together before assigning, because the service description is the document that settles what a plan actually carries.

Watch the briefing · 3:585 Tips for Your Microsoft NegotiationWhere placement work has to happen before the discount conversation starts.

What is the real difference between F1 and F3?

The mailbox and web Office. F1 provides a secure identity, Entra, Teams, and SharePoint access. F3 adds a 2 GB Exchange Online mailbox and the web and mobile versions of the Office apps. Both carry security and management features tuned for shared and mobile devices.

Does F1 include any email?

No Exchange Online mailbox. An F1 user can receive limited communication through Teams but cannot run a standard corporate inbox. If the role genuinely needs email, it needs F3 or higher and there is no argument to have.

Do either plan include desktop Office?

Neither does, and that is deliberate. F3 includes the web and mobile apps, which suits shared devices and shift work. If a role needs installed desktop Office, the answer is E3 rather than any frontline SKU.

How many F3 seats are typically misplaced?

Between 20 and 40 percent belonged to roles that never opened the mailbox in the reviews we ran. Since the mailbox is essentially the whole difference between the two plans, that means the entire premium was paid for a capability that went unused.

Why do estates default to F3?

Administrative simplicity. One frontline plan means one assignment rule, one onboarding path, and no reclassification when someone changes role. That has real operational value, but it is a recurring payment for convenience rather than a free choice, and it should be priced as such.

Which scenarios fit F1 cleanly?

Shared breakroom kiosks, shop floor terminals, warehouse scanners, and handheld device roles where the task is scanning and status updates rather than correspondence. These fit F1 and were licensed at F3 anyway in most estates we reviewed.

How do we identify the seats to move?

Mailbox activity telemetry over a full quarter. Roles returning zero reads are the population to move. The test is narrower than a full persona exercise because there is only one question: does the work require an inbox to be read.

Is this the same as moving deskless staff off E3?

No, it is the move underneath it. The E3 to F3 shift is the better known saving, worth $36 against $8 a month per seat. The F3 to F1 shift is the second move, and it is harder to see because the gap is narrow and an inbox feels like a baseline entitlement.

Does this require cutting headcount?

No. Both frontline moves are placement changes rather than reductions, so the seat count is unchanged and the saving survives a headcount freeze. That also means they can be pursued without cancelling anything or renegotiating volume.

Are frontline SKUs capped?

Yes, they are capped per user and intended for deskless and shift based staff rather than as a cheap alternative to a knowledge worker seat. Assigning them to office based roles that need desktop Office creates a capability problem rather than a saving.