Microsoft 365 F1 vs F3 vs Business Basic: Licensing Shift Workers

Microsoft's frontline documentation splits a workforce in two. Information workers have a desktop or laptop and work mostly on documents: headquarters, finance, sales operations. Frontline workers work on tablets or phones, directly with customers or in manufacturing and distribution: retail associates, clinicians and nursing staff, factory and warehouse workers, field technicians.

"Microsoft 365 for frontline workers" is Microsoft's name for the F3 and F1 licenses; any frontline scenario also runs on E3 or E5.

The part that matters in an audit: F plans are not cheaper seats for anyone. Microsoft restricts them to users who meet its frontline-worker definition in the Product Terms, and our Plan-Mix Optimizer carries that restriction as a review note on both plans. Read the definition before moving anyone with a desk onto F3.

A practical test that matches Microsoft's examples: the working day happens on a device pulled from a charging cradle, the person needs Teams chat, Shifts and tasks rather than a personal mailbox and installed Office, and the device goes back at the end of the shift.

Microsoft's licensing overview describes the frontline toolset as Teams chat, Shifts for scheduling, Planner for tasks, Lists for tracking, and SharePoint, OneDrive, Viva Connections and Viva Engage for company resources and training. Users on an F license also get Microsoft's tailored Teams layout: on mobile, Connections, Chat, Engage, Walkie Talkie, Planner, Shifts and Approvals are pinned by default.

What F1 leaves out is the part that gets missed. Microsoft's frontline setup guide is direct: users must have an F3 license to get access to email, and Power Apps and Power Automate are available with F3 but not F1. An F1 user can chat, see their shifts and complete a checklist, but has no mailbox of their own and cannot run a flow.

Our Microsoft 365 F1 subscription page lists a Teams-included SKU, a no-Teams SKU, and separate frontline add-on SKUs for the Microsoft Defender Suite and the Microsoft Purview Suite.

Our Plan-Mix Optimizer models F1 with no mailbox and view-only web apps, and treats Intune and Entra ID P1 as included while flagging both rows for confirmation against Microsoft's plan comparison table. Confirm those rights before you rely on them.

F3 is F1 plus the two things frontline managers ask for first: an Exchange Online mailbox, and the Power Platform pieces that turn a paper checklist into a Power App and an approval into a flow. Microsoft's setup guide puts it plainly: some services are only included with F3, such as email and the Power Platform.

Our Microsoft 365 F3 subscription page lists monthly and annual options in Teams-included and no-Teams variants, and notes that the exact workload rights are not in the source catalog. The mailbox size, the Office web and mobile app rights and any Windows Enterprise rights belong in a check against Microsoft's service-plan documentation.

Where F3 stops: it is not a desktop-Office plan. Microsoft's framing is that information workers have Microsoft 365 apps on desktops or laptops while frontline workers have them on phones or tablets; someone who needs installed Excel on a PC is an information worker in that model.

F3 also does not carry Teams Phone. Our Teams Phone Licensing Calculator records that F3, the Business plans and Microsoft 365 E3 do not include it; a store manager who needs a number adds Microsoft Teams Phone Standard.

Business Basic is not a frontline plan, which is why it keeps ending up on frontline staff. Our Microsoft 365 Business Basic page lists Exchange Online email and calendar, web and mobile Word, Excel, PowerPoint and Outlook, OneDrive, SharePoint, and Teams on the Teams-included SKU. It does not include desktop Office or the endpoint security and device management that sit in Business Premium.

Two properties decide the fit. There is no frontline eligibility rule, so if you cannot show that a group meets Microsoft's definition, Business Basic needs no argument. And the Business family is capped at 300 users per tenant: a retailer with 900 associates cannot use it for all of them; a 120-person clinic can. We covered the cap in Microsoft 365 Business: the 300-license limit.

The trade-off is shared devices. Our optimizer models Business Basic with a mailbox, web apps and Teams but no Intune and no Entra ID P1. If shift staff use pooled devices and you need device compliance, you add Intune Plan 1 and Entra ID P1 or move to Business Premium, and then compare the total against F3.

Every plan here is licensed per user. Our Exchange Online Kiosk page notes that the source pack lists no device-based or shared-device entitlement, and the same holds for the F and Business plans: the license follows the person who signs in, not the tablet in the cradle. A device that signs in with its own account, such as a common-area phone, is a separate device license.

For pooled devices Microsoft recommends shared device mode, a Microsoft Entra ID feature for Android, iOS and iPadOS. A worker signs in once to one supporting app and is signed in to every other app that supports the mode; one sign-out at the end of the shift clears them all, and Conditional Access can target shared devices specifically. Set it up manually for a pilot or at scale through Intune.

Kiosk devices, meaning devices nobody signs in to, are different. Microsoft's device guidance does not recommend them for Teams scenarios: the apps need a user identity, activity cannot be audited and MFA cannot be applied.

The kiosk mailbox is the other meaning of the word. Exchange Online Kiosk is a standalone, lightweight mailbox plan for kiosk, frontline and infrequent email users, without desktop Outlook, Teams, SharePoint or OneDrive. It answers one problem: an F1 user who needs a mailbox but not the rest of F3. For targeted staff communications, Microsoft suggests shared mailboxes backed by dynamic groups, which need no extra user license.

Sort people before plans. Put every user into one of four groups: desktop information worker, web-only worker, frontline on a shared or personal mobile device, and kiosk or device-only.

Then list the controls each group must carry: Intune enrollment or app protection, Conditional Access, Defender, Purview retention, Teams Phone. Those requirements decide the plan, not the headline price. Confirm eligibility for every group headed for F1 or F3 and write the reasoning down.

Run the numbers with our Microsoft 365 Plan-Mix Optimizer. It takes headcount by role and the controls you need and returns the lowest-cost compliant plan mix at Microsoft's list price, with an all-in E5 alternative beside it, and it shows which F1 and F3 assumptions are flagged for confirmation.

Assign licenses through groups; Microsoft calls group-based assignment the most scalable method for frontline workers, and warns that moving a user from an E plan to an F plan may require unassigning the old license first.

Can we give an F1 license to a receptionist or a bookkeeper?

Only if that person meets Microsoft's frontline-worker definition in the Product Terms. A desk-based user with a PC is an information worker in Microsoft's model; Business Basic or an E plan is the defensible choice.

Does an F1 user get a mailbox?

No. Microsoft's setup guide states that users must have an F3 license to get access to email. Move the user to F3 or add a standalone Exchange Online Kiosk mailbox.

Do shared devices need their own license?

No. The F and Business plans are per user, and the license follows whoever signs in. A device with its own resource account, such as a common-area phone, is a separate device license line.

Can we mix F3 and Business Basic in one tenant?

Yes. Many organizations run Business plans for office staff and F plans for the floor. Keep the 300-user cap and the eligibility reasoning for the F group on file.

Teams-included or no-Teams SKU?

Both F1 and F3 are listed in both forms. A no-Teams SKU carries no Teams rights, so a frontline user on it would need Teams licensed separately. Choose the Teams position deliberately across the group.