Microsoft 365 F3 vs E3 in 2026. Which workers belong on each plan.

F3 is the frontline suite and E3 the knowledge worker suite, with E3 close to four times the list price. Put frontline staff on F3, keep desktop Office users on E3, and cover the roles in between with an add on.

How do Microsoft 365 F3 and E3 differ in features and price?

F3 is Microsoft's frontline suite and E3 is its knowledge worker suite. F3 gives a user web and mobile Office, Teams, SharePoint and a 2 GB mailbox. E3 adds the desktop Office apps, a 100 GB mailbox, a terabyte of OneDrive and the full management and security tooling.

The price gap is wide. Until June 2026, F3 listed at $8 per user per month against $36 for E3, a ratio of roughly 4 to 1. Since July 1, 2026 the list prices are $10 and $39, so E3 still costs close to four times as much per seat.

Why is F3 more than a cut down E3?

F3 was built for deskless, shift based staff who need mobile access, Teams and light email. Microsoft aims its F plans at employees whose main work is direct contact with customers, patients or the public, or who support essential services. For that group it does the job well.

Problems start when the license crosses the role boundary, in either direction. A knowledge worker placed on F3 loses the desktop tools the job runs on. A deskless worker left on E3 carries a desktop suite, a 100 GB mailbox and a terabyte of storage they never open.

What did the July 2026 price change do to the gap?

It narrowed the ratio a little, because frontline prices rose faster. F3 went from $8 to $10, an increase of 25 percent, and F1 from $2.25 to $3, an increase of 33 percent. E3 rose $3, or about 8 percent.

• Ratio at list. F3 used to cost 22 percent of E3. It now costs about 26 percent.
• Gap per seat. The monthly difference grew from $28 to $29, so each seat placed correctly is worth slightly more than before.
• Timing. If you signed before July 2026, your price sheet may hold the old prices until renewal. Check it, because the renewal is where the new list lands.

How much can moving frontline staff from E3 to F3 save?

Right sizing the F3 and E3 mix cut the frontline license line 30 to 60 percent in the reviews we ran. At a thousand frontline workers, the gap between the two list prices is $348,000 a year at 2026 prices, or $336,000 at the old $8 and $36. The larger the deskless population, the more there is to recover.

A worked example at 2026 list prices

Say a company has 3,500 store, warehouse and depot staff, all on E3 since the tenant was set up. A usage review keeps 600 on E3 for desktop Excel or heavy email. It puts 300 boundary roles on F3 plus Microsoft 365 Apps for enterprise at $14, and the other 2,600 on F3.

The saving at list is $958,800 a year, about 59 percent. Discounts and the roles that turn out to need E3 pull real results lower, which is why our reviews produced a range of results.

Why do discounts shrink the gap?

E3 is usually discounted harder than F3, so the gap shrinks once you price on net. At the old list prices F3 was 22 percent of E3. In our reviews, after discount, it typically came to 30 to 40 percent of the E3 net price, so model the mix on your own net prices.

Say your E3 nets at $31.20 after a 20 percent discount and F3 at $9.50 after 5 percent. F3 then costs 30 percent of E3, and the mix is still one of the largest structural savings in a frontline heavy organization.

Which workers belong on F3 and which need E3?

Place people by what they use every week. Staff who work on mobile devices, in Teams and in light email belong on F3. Anyone who lives in desktop Office or runs heavy email belongs on E3 without debate.

• F3 candidates. Retail associates, manufacturing and logistics staff, field workers and shift based healthcare roles, each confirmed against the feature fit for the role.
• E3 by default. Knowledge workers, finance and analyst roles working in desktop Excel, and anyone whose mailbox is past 2 GB or depends on an archive.
• Boundary roles. Frontline profiles with occasional desktop needs, such as a store manager who builds the weekly roster in Excel.
• Teams Phone users. Microsoft warns these users may not suit an F plan. If they move, price the Teams Phone Standard for Frontline Workers license first.

The deeper frontline split, deciding which light roles fit F1 rather than F3, is worked in our F1 versus F3 guide. The knowledge worker side of the same organization faces a parallel choice, covered in the E3 versus E5 decision guide.

How does F3 plus an Office add on work for boundary roles?

Licenses on one user are cumulative, so a user holding F3 and Microsoft 365 Apps for enterprise can install and activate the desktop apps. At $10 plus $14 the pair lists at $24 against $39 for E3. That is $15 per user per month, or $180 a year, and it is the placement most organizations never price.

The mailbox stays the 2 GB Kiosk mailbox with no archive. Desktop Outlook cannot connect to a Kiosk mailbox over the Exchange protocol, so email stays in the browser and mobile apps. The pair suits occasional Excel or Word users rather than heavy email users, and our Microsoft 365 Apps standalone guide covers the add on in more detail.

Why we advise against putting as many users as possible on F3

The common advice is to push every worker you can to F3 and bank the difference. We disagree with it in that blanket form. In the reviews we ran, knowledge workers moved down to hit a savings number lost desktop Office, broke their workflows and flooded the service desk.

The support cost that followed ate much of what the downgrade was meant to save. In our reviews the saving came from precise placement: frontline staff on F3, knowledge workers on E3, and boundary roles on F3 plus the Office add on.

A frontline worker left on E3 wastes budget every month. A knowledge worker pushed onto F3 loses a working day to missing tools, and the help desk pays for it.

How do you check which of your users fit F3?

Use the usage data Microsoft already collects in your tenant. The org chart misplaces people in both directions, while the admin center reports show who opens desktop Office, how large each mailbox is and how much OneDrive each user holds.

1. Microsoft 365 Apps usage report. Under Reports, then Usage, in the Microsoft 365 admin center. It shows which users run the desktop apps on Windows or Mac and who works only on web and mobile.
2. Microsoft Office activations report. Shows how many devices each user has activated desktop Office on. A frontline user with no activations is a strong F3 candidate.
3. Mailbox usage report, or Get-MailboxStatistics in Exchange PowerShell. Anyone over 2 GB either cleans up before the switch or stays on E3. Check for archive mailboxes too.
4. OneDrive usage report. OneDrive turns read only for F3 users above the 2 GB limit, so flag every candidate near or over it.
5. Teams Phone assignments. List users with Teams Phone enabled before you change a single license.
6. Current license assignments. Export which plan each user holds today. Exports list plans by string ID, and our license types comparison maps each ID to its product.

The reports hide user names by default in many tenants. A global admin can turn off concealed names in the org settings for reports before you export. Repeat the pass quarterly, the cadence our Microsoft 365 licensing guide recommends, and correct misassigned seats at the true up, where the count bills.

What goes wrong when organizations change the F3 and E3 mix?

Four placement errors cause most of the waste we find, and two more cause data problems during the switch itself.

• Leaving frontline staff on E3. The inertia default and the most expensive error: $29 per seat per month at list for capabilities deskless roles never open.
• Downgrading the wrong workers. Knowledge workers pushed to F3 lose desktop Office and generate the support tickets that eat the saving.
• Stepping boundary roles up to full E3. Roles with occasional desktop needs go to E3 when F3 plus the Office add on covers them at a fraction of the cost.
• Segmenting by job title. Org chart placement misplaces users in both directions and never corrects itself.
• Removing E3 before assigning F3. Microsoft advises swapping licenses in one operation, because removing a license and reassigning later can affect the user's data.
• Skipping the cleanup. Desktop apps drop into reduced functionality mode after the switch. Move local files into OneDrive, trim mailboxes and uninstall the desktop apps as part of the change.

What have we seen in frontline license reviews in 2024 and 2025?

Across roughly 20 to 30 Microsoft 365 reviews with large frontline populations that I ran in 2024 and 2025, the license mix rarely matched the workforce. Frontline staff sat on E3 by default in most organizations with deskless populations, through inertia more than any decision.

• The errors ran both ways. Deskless staff sat on E3 by inertia, while knowledge workers placed on F3 raised tickets.
• The reduction came from correction. The savings range quoted above came from placing frontline staff on F3 and fixing the misassignments in both directions.

What will the Microsoft account team say about moving users to F3?

Expect pushback, since every seat moved from E3 to F3 removes about three quarters of that seat's revenue at list. These are the lines we hear most, with replies that hold up.

"Those users are not frontline workers."

Answer with usage data per role: device activations, mailbox size and whether the role serves customers or the public directly. Match each group to Microsoft's own description of the F plans and show the evidence.

"Your E3 discount was priced on the full seat count."

Ask for the per SKU price with and without the change, in writing. A few points of E3 discount rarely outweigh a $29 monthly gap per seat across hundreds of seats, and the written comparison makes that visible.

"The change has to wait for your anniversary."

Rules on reductions differ by agreement, so ask exactly where your contract allows one. Then write the F3 price and quantities into the current amendment, so the anniversary change is administrative.

"Users will complain and your help desk will pay for it."

That happens when placement is wrong. Pilot one site, fix mailbox and OneDrive sizes first, and keep anyone with regular desktop activity on E3 or the add on.

What to do next

1. Segment by tooling use. Pull the Apps usage, activations, mailbox and OneDrive reports and group users by what they run, since job titles misplace in both directions.
2. Move confirmed frontline groups to F3. Check the feature fit role by role, clean up mailboxes and OneDrive, and swap licenses in one operation.
3. Keep knowledge workers and heavy email users on E3. A downgrade that breaks their day costs more in tickets than it saves.
4. Price F3 plus Apps for enterprise for boundary roles. Compare it with E3 on your net prices before stepping anyone up to the full suite.
5. Correct the misassignments at the next true up. Model the saving across the full frontline headcount on net prices. Our license optimizer and the Microsoft practice can run the mix with you.

Frequently asked questions