06-reference/research

copilot chat f1 f3 licensing verification

2026-10-06·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
microsoftcopilotlicensingfrontline-workersprimary-source-verification

Is Copilot Chat Actually Included at Microsoft 365 F1/F3? Primary-Source Verification

The question

"Verify the 'Copilot Chat included at F1/F3' licensing claim against Microsoft product terms rather than analyst blogs."

Context: [[2026-07-20-deskless-worker-identity-agent-distribution]] recorded the claim as analyst-sourced and explicitly flagged it as unsafe to repeat to a client. It is load-bearing for the deskless-population cost argument, where "they already have Copilot Chat" would remove a per-seat line item from a scoping conversation.

VERDICT: CONFIRMED WITH CAVEATS. F1 and F3 are explicitly listed in Microsoft's own eligibility documentation. But the thing that is included is web-grounded chat only. Chat grounded in the customer's own data requires the paid Microsoft Copilot add-on, so the version of the cost argument that actually matters in a scoping room is not supported.

What we already know (from the vault)

What the web says

Tier 1 — Microsoft primary licensing documentation (the decisive source).

Naming generations, dated, because the dispatch is right that this is where answers go wrong.

Tier 2 — Microsoft marketing / pricing pages.

Tier 3 — what I could not reach.

Convergences and contradictions

Synthesis for RDCO

The practical output of this verification is a replacement sentence. The claim "your frontline workers already have Copilot Chat, so there is no incremental per-seat AI spend" should not be said. The claim that can be said, with a citation and a date, is: "Microsoft 365 F1, Microsoft 365 F3 and Office 365 F3 users are eligible for Microsoft Copilot Chat at no extra cost when they sign in with a Microsoft Entra work or school account. That included experience is grounded in the web. Grounding in your own data requires the Microsoft Copilot add-on, which can be attached directly to those same F-series licenses." That is a longer sentence than the analyst version and it is the one that survives a procurement person reading the documentation.

This matters for scoping work more than for cost work. The web-grounded Basic tier is a general-purpose assistant with Enterprise Data Protection, which is genuinely useful for a store associate drafting a message or looking something up, and genuinely useless for the class of use case a deskless-agent engagement is usually about: answering a question from the operations manual, checking a schedule, looking up a part, filing a report. Every one of those is work-grounded. So the included tier does not reduce the priced scope of a deskless agent engagement at all. It changes a different thing: it means the identity and sign-in work described in the parent brief has a visible payoff the day it lands, before any agent ships, which is a useful adoption argument for funding a provisioning phase that otherwise reads as pure plumbing.

The second finding is the one worth carrying into a phData Deal Solutions Architect discovery conversation. Because the paid add-on attaches directly to F1/F3, the cost curve for a deskless population is a clean per-seat decision at the full enterprise rate rather than a two-step SKU migration. At any realistic deskless headcount that number is large, which is exactly what makes the Copilot Studio published-agent and metered-capacity path the live alternative rather than a theoretical one. The right move in the room is to present both as named options with the licensing basis stated, not to present "Copilot is included" and have it unravel under a licensing review.

Calibration note on the overall confidence shape. The SKU eligibility question is settled at Microsoft's own documentation tier with a dated quote. The contract tier is not settled, because the Product Terms site was not readable in this run. For an internal scoping conversation or a discovery document, the Learn citation is sufficient and is what Microsoft's own field teams cite. For anything contractual, or anything where a client's procurement will push back on the word "included," the document that settles it is the Microsoft Product Terms Online Services product-offering entry for Copilot under that customer's specific licensing program and effective date. That has to be pulled from an interactive browser session on the Product Terms site or from the customer's own licensing paperwork, and this brief does not substitute for it.

Why this is in the vault

This closes the first open follow-up on [[2026-07-20-deskless-worker-identity-agent-distribution]] and converts a flagged-unsafe analyst claim into a quotable, dated, primary-sourced sentence plus an explicit do-not-say. It is directly consumable in the founder's phData Deal Solutions Architect discovery work on deskless-population agent scoping, where it replaces a cost-reduction argument that would not have survived a client licensing review with a scope-and-adoption argument that will.

Open follow-ups

Related

Sources

Primary — Microsoft licensing documentation

Microsoft marketing / announcement tier

Attempted and unreachable

Secondary — evidence of belief, not of terms (inherited from the parent brief, not re-verified)

Vault