F3 sits at roughly forty percent the cost of E3 and looks like a free saving. Most enterprises that attempt the move end up either misclassifying populations they cannot defend at audit, or pulling back to E3 after employees hit the F3 ceilings inside the first quarter. The F3 versus E3 evaluation is a use case test, a workload test, and a documentation test. The savings only land when all three converge on a defensible population.
The Microsoft Product Terms define F3 as a license for frontline workers who perform their primary job duties outside of a traditional office environment. The phrasing is deliberately broad and audit defensible classification needs to be tighter than the Microsoft framing.
Microsoft describes F3 as appropriate for first line workers including retail associates, manufacturing operators, service technicians, field staff, healthcare workers in clinical settings, and similar roles where the user does not sit at a primary desk during the working day.
Our internal classification standard tightens the Microsoft framing into five tests that survive contested audit.
F3 has product ceilings that often surface only after deployment. Procurement should know each one before the SKU change moves to the order.
F3 includes Exchange Online Kiosk at 2 GB. Users who exceed this hit a hard cap and stop receiving mail. The threshold is reached faster than most procurement teams expect.
Personal OneDrive storage is capped at 2 GB. Document collaboration is restricted to SharePoint and Teams shared content, which is fine for most frontline workflows and a stop for any user expected to retain personal document history.
F3 does not include installed Office desktop apps. Users access Word, Excel, and PowerPoint through the browser. Power Apps and Power Automate are limited to specific app types and connector tiers.
F3 is materially cheaper than E3. The savings scale linearly with the defensible population. The financial model needs to be honest about the population size and the operational overhead of running a mixed tier estate.
Twenty five thousand store associates currently on E3 at roughly $23 per user per month. Annual base spend $6.9M. F3 at roughly $9 per user per month on the same population brings annual spend to $2.7M. The annual saving sits at $4.2M before adjusting for operational overhead.
The operational overhead is the cost of managing two tiers, including shared device deployment, training on web only Office, and the F3 specific mailbox and storage policies. The overhead frequently lands at four to seven percent of the gross saving in year one and reduces in year two as the mix stabilizes.
Eight thousand clinical staff currently on E3. The defensible F3 population is the nursing and allied health roles that work shifts and use shared devices, roughly five thousand seats. The remaining three thousand stay on E3 for back office and supervisory functions.
Annual saving on the five thousand seat F3 conversion at typical concession bands lands between $700K and $850K. The figure is smaller than the retail case because the defensible population is smaller, not because the SKU economics differ.
F3 is one of the most commonly contested SKUs in audit because the Microsoft Product Terms language is deliberately broad. The buyer needs evidence that survives a deliberate challenge from a Microsoft audit team motivated to reclassify the population upward.
The first test is whether the buyer has consistent HR role documentation that identifies the user as a frontline worker. The job code, the role description, the salary band, and the reporting structure all need to point to the same answer. Inconsistency surfaces immediately in audit.
The remediation is upstream. The HR data model needs a frontline classification flag that flows to the licensing group rule. Without it, the audit team can argue that the F3 assignment was at administrator discretion rather than at a defensible classification.
The second test is whether the actual workload pattern matches an F3 use case. The audit team will look at mailbox size, OneDrive size, desktop Office installation records, and authentication patterns. Users at the F3 ceilings or pushing them are flagged.
The third test is whether device assignment matches. Shared device or kiosk pattern supports F3. Personally assigned and persistently configured PC undermines it. The Intune or device management telemetry tells the story.
Our internal five test classification standard, the HR data model requirements, and the audit defensible documentation template. Sent on request.
The defensible classification is the precondition for the saving. Without it, the F3 attach becomes audit exposure rather than recovered spend.