The Microsoft 365 frontline plans F1 and F3 carry a separate user-eligibility test, a separate seat-count cap and a separate device-class limitation. The Admodum read on qualifying populations, the F1-to-F3 step-up and the renewal-time right-tiering disposition.
The frontline plans carry a published eligibility test: the qualifying user is shift-based or task-based, is not a knowledge worker as the primary role, is primarily mobile or non-PC-bound, and works in roles such as field service, retail, hospitality, healthcare clinical-floor, manufacturing-floor, logistics. The eligibility test is enforced through the Volume Licensing product terms and is read against the seat-assignment construct, not against headcount alone.
The buyer-side discipline is to map the qualifying population: the named operational roles, the named seat-assignment construct, the named licensing population. Where the operational role sits inside the eligibility test, the F1 or F3 plan is the right tier; where the role sits outside (the back-office knowledge worker who happens to share an office with a frontline population), the E-series tier is the right tier.
The wider M365 plan-tier context sits at Microsoft 365 plans; the wider editorial sits in the Microsoft pillar.
F1 is the entry frontline tier. It carries Teams (the principal collaboration workload), Exchange Online mailbox capped at two gigabytes, SharePoint web-only access (no desktop sync, no Office desktop integration), OneDrive capped at two gigabytes, and the web-only Office apps for viewing-only on documents the user did not create.
F1 carries no desktop Office apps, no Office on a primary device (the user accesses Office through a shared kiosk or through the web), no OneNote, no Bookings premium, no Project, no Visio. The mailbox cap is binding and is the most frequent over-reach when an F1 user has a knowledge-worker shadow workload (signing up to email lists, retaining attachments).
The wider seat-assignment hygiene sits at the seat-assignment hygiene spoke; the per-user per-device construct sits at per-user versus per-device; the wider plan-by-tier context sits at Microsoft 365 plans.
F3 adds the web-and-mobile Office apps (Word, Excel, PowerPoint, Outlook), the mobile Office apps on iOS and Android (full editing on devices below 10.1-inch screen size), Stream, Yammer, Power Apps for frontline (a limited Power Apps entitlement scoped to frontline-friendly templates), and the broader SharePoint and OneDrive workload at the same two-gigabyte cap.
F3 still carries no desktop Office apps on a Windows or macOS desktop, no Project, no Visio, no premium security overlay (no Defender for Office, no Entra ID P2). The licence is the right tier where the user needs mobile editing of documents (a field service technician completing a job sheet on a tablet) but does not need a Windows or macOS desktop with the full Office desktop suite.
The frontline plans carry a separate pricing curve. At list price: F1 is roughly two dollars twenty-five US per user per month, F3 is roughly seven dollars sixty-five per user per month, E3 is roughly thirty-six dollars per user per month, E5 is roughly fifty-seven dollars per user per month. F1 sits at one-twelfth to one-tenth of E3; F3 sits at one-fifth to one-fourth of E3.
At enterprise discount the curve flattens slightly (the frontline plans are typically less discounted than the E-series), but the relative ratios hold. The right-tiering economics on a fifty-thousand-frontline-worker estate: moving from E3 to F3 saves roughly twenty-eight dollars per user per month, or roughly seventeen million dollars per year at list and roughly eleven to thirteen million per year at typical enterprise discount.
The wider M365 economics context sits at Microsoft 365 plans; the E3-to-E5 step-up arithmetic sits at Defender suite licensing and Entra ID licensing; the Copilot overlay sits at Copilot seat economics.
The seat-assignment hygiene runs against the workload signal. The buyer-side discipline is to read the workload exercise rate per frontline user against the assigned tier: a user assigned F3 who only uses Teams and mailbox is over-licensed; a user assigned F1 who uses mobile Office editing daily is under-licensed (and the licence is non-compliant). The reconciliation runs through the Microsoft 365 admin portal usage report against the AD-export and the workload-signal log.
Right-tiering at scale typically reveals between fifteen and thirty percent of an F3 estate sitting on F1 workload signals, and between five and twelve percent of an F1 estate sitting on F3 workload signals. The renewal-time disposition is a net rightsizing (the F3-to-F1 step-down on the over-licensed population net of the F1-to-F3 step-up on the under-licensed population).
The wider SAM context for seat-assignment audit sits at SAM audit anatomy; the scope-control read sits at SAM scope control; the settlement posture sits at SAM settlement position.
At renewal the buyer holds five artefacts on the frontline estate: the qualifying-population map (the operational roles inside the eligibility test, the headcount per role), the assigned-seat inventory (F1 versus F3 versus E-series, per user per role), the workload-signal exercise rate (per user per workload over the trailing twelve months), the right-tiering arithmetic (the F3-to-F1 step-down and the F1-to-F3 step-up populations) and the renewal-quantum forecast (the net F1 and F3 seat counts for the next term).
The wider engagement sits at the Microsoft practice; the aggregated reading list sits at the Microsoft knowledge hub; the renewal moment routes to the Renewal Programme; the engagement-models read sits at Fixed Fee, Contingency and Annual Retainer; the engagement opens at contact.
The workload-signal discipline the F1 / F3 read runs against.
A senior Admodum Microsoft advisor will read your qualifying-population map, the assigned-seat inventory and the workload-signal exercise rate against the F1 / F3 / E-series construct on a private call. Renewal moments route to the Renewal Programme.