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)
- [[2026-07-20-deskless-worker-identity-agent-distribution]] states the claim verbatim as: "Copilot Chat capability is reported as included at F1/F3 tier, per the same analyst sources — but this is exactly the class of claim to verify against a Microsoft product-terms document before repeating it to a client." The only cited sources were 2Data and Redress Compliance, both labeled analyst and not vendor-confirmed.
- The same brief flags frontline licensing price moves (F1 $2.25 to $3.00, F3 $8.00 to $10.00, July 2026) from those identical analyst sources. Those price figures were not verified in this run and remain analyst-tier.
- [[2026-07-13-kwik-trip-deskless-agent-distribution]] built its headline cost math on the per-seat Copilot rate ($30/user/month), not on the F-series base, so the base-license question was always a secondary line item rather than the driver.
- [[2026-08-03-every-microsoft-copilot-studio-trap]] is the counterweight on the agent side: the "free chat plus cheap agents" story has adoption friction that licensing documents do not capture.
- Standing vault distinction worth carrying into this brief: "frontline worker" is used by vendors to mean both "worker with a cheap license" and "worker with no license," and these are different architectures with different cost curves.
What the web says
Tier 1 — Microsoft primary licensing documentation (the decisive source).
- Manage Microsoft Copilot Chat (
ms.date: 2026-10-01,updated_at: 2026-10-05), section "Microsoft Copilot Chat eligibility", states verbatim: "Microsoft Copilot Chat is available at no extra cost for eligible users who sign in with a Microsoft Entra work or school account and have a qualifying Microsoft 365 subscription." The list that follows includes, verbatim, "Microsoft 365 F3 or F1" and "Office 365 F3". Confidence: high. Source tier: primary Microsoft licensing documentation. - Precision point the analyst phrasing loses: the list contains Microsoft 365 F1, Microsoft 365 F3 and Office 365 F3. There is no Office 365 F1 entry. "F1/F3" as a shorthand is therefore correct for the Microsoft 365 family and correct only at F3 for the Office 365 family. Confidence: high (primary).
- The same page immediately qualifies it, verbatim: "Microsoft Copilot Chat is the baseline, secure AI chat experience included with eligible Microsoft 365 plans. Access to Copilot capabilities in Microsoft 365 apps, organizational data, advanced agents, and priority service depends on licensing and tenant configuration." It also notes users may see labels "Copilot Chat (Basic)", "Copilot (Basic)", or "Copilot (Premium)". Confidence: high (primary).
- License Options for Microsoft Copilot (
ms.date: 2026-09-25,updated_at: 2026-09-30) draws the line that settles the cost argument, verbatim: "Two Copilot Chat options are available: web-based chat and work-based chat. Web-based chat: Shows results from the internet. Automatically included with an eligible Microsoft 365 subscription at no extra cost. Work-based chat: Shows results that the Microsoft Entra work or school account can access. Is available with a Microsoft Copilot license." Confidence: high (primary). This is the sentence to quote if anyone pushes back. - Second finding from the same page, and it was not in the parent brief: the frontline SKUs are now valid prerequisites for the full paid add-on. The "Microsoft Copilot" add-on prerequisite list includes Microsoft 365 F1, Microsoft 365 F3 and Office 365 F3. The US Government (GCC / GCC-High / DoD) prerequisite list includes Microsoft 365 F1 and Office 365 F3 but not Microsoft 365 F3. Confidence: high (primary); the government asymmetry is read off the published list and may be a documentation lag rather than a deliberate exclusion, so treat it as a question to ask Microsoft rather than a fact to assert.
- Microsoft Copilot requirements (
ms.date: 2026-10-05) confirms the licensing matrix at a glance: for Microsoft Copilot Chat, "Microsoft Copilot license: Not required for eligible users"; "Eligible Microsoft 365 subscription or base license: Required"; "Microsoft Entra ID account: Required." Confidence: high (primary). - Microsoft Copilot service description corroborates the split at service-description tier. Its feature table marks "Work data and organizational context" with footnote 2, which reads verbatim: "Microsoft 365 Copilot (Premium) features: A Microsoft 365 Copilot license is required to access this feature." The service description does not enumerate F1/F3 at all; it is organized by cloud environment (Commercial, GCC, GCC-High, DoD), not by base SKU. Confidence: high (primary) for the Basic/Premium split; the service description is not a source for SKU eligibility.
Naming generations, dated, because the dispatch is right that this is where answers go wrong.
- Current name as of this brief: Microsoft Copilot Chat. Both Learn pages carry the note, verbatim: "Microsoft 365 Copilot is now named Microsoft Copilot, and Microsoft 365 Copilot Chat is now named Microsoft Copilot Chat." The app URL is moving from
m365.cloud.microsofttocopilot.cloud.microsoft. This rename is recent, documented on pages updated 2026-09-30 and 2026-10-05. Confidence: high (primary). - Prior generation: Microsoft 365 Copilot Chat, announced 2025-01-15 in Copilot for all: Introducing Microsoft 365 Copilot Chat, which paired the free chat experience with pay-as-you-go agents. Confidence: high for existence and date (Microsoft's own announcement blog, marketing tier); medium for any specific capability detail, because I did not fetch the blog body.
- Earlier generations: Bing Chat Enterprise, then Microsoft Copilot with commercial data protection. This lineage is from background knowledge, not verified in this run. A targeted search on microsoft.com did not surface a document explicitly stating the Bing Chat Enterprise rename. Confidence: low-medium. Do not put the lineage in a client artifact without pulling the rename note first.
Tier 2 — Microsoft marketing / pricing pages.
- The Microsoft Copilot add-on list price is $30.00 per user per month, paid yearly, enterprise, per Microsoft Copilot pricing - Enterprise, with a qualifying base plan required separately. Confidence: medium. I did not read the pricing page directly; this came through a domain-restricted search summary of microsoft.com. Verify the figure on the page before it goes in a client deck.
- Microsoft 365 Copilot Business exists as a separate lower-priced bundle track ($18/user/month after a promotional discount through 2026-12-31) aimed at Business plans, not at frontline F-series. Confidence: low-medium, same reason. Not relevant to an F1/F3 deskless population, but worth knowing it exists so a client's reseller quote at a non-$30 number does not look like a contradiction.
Tier 3 — what I could not reach.
- The Microsoft Product Terms site did not yield readable content.
https://www.microsoft.com/licensing/terms/productoffering/...is a single-page application;curlwith a browser User-Agent returned only navigation chrome (roughly 4.6 KB of extractable text), and a headless-browser render of three candidate product-offering slugs each returned "is not available on this date, please select another product or date." The site's/licensing/terms/searchpath returned an error page. I did not find the correct Copilot product-offering slug. No Product Terms citation is offered here, and none should be invented.
Convergences and contradictions
- The analyst claim is directionally right and materially incomplete. 2Data and Redress said "Copilot Chat is included at F1/F3." Microsoft's documentation agrees on the words and disagrees on the substance: what is included is the web-grounded "Basic" experience, and the organizational-data grounding that makes the capability interesting for a frontline use case sits behind the paid add-on. The analyst sources were evidence of what the market believes, and the belief is the usable half of a two-part fact.
- A contradiction with the parent brief's framing, in RDCO's favor. [[2026-07-20-deskless-worker-identity-agent-distribution]] treated the F-series as a base-license floor beneath a separate $30 Copilot decision. The licensing page shows F1, F3 and Office 365 F3 are themselves valid prerequisites for the add-on. So the deskless upgrade path is a single additive line, not a base-plan migration first. That removes an objection the parent brief implicitly left standing.
- No contradiction found on eligibility itself. Four Microsoft-controlled surfaces were consistent: the Chat eligibility list, the license-options page, the requirements matrix, and the service description's Basic/Premium footnote. The convergence is strong enough that the eligibility half of the claim can be asserted.
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
- Does the Microsoft 365 frontline-worker plans service description, or the F-series plan comparison page, carry any F1-specific or F3-specific Copilot Chat carve-out that the general eligibility list does not surface? The eligibility list and the service description were consistent, but neither is organized by F-series SKU, so a frontline-specific exclusion would not have appeared in either source read here.
- What does the documented "Copilot Chat agents for Word, Excel, and PowerPoint" entry point actually resolve to for an unlicensed Microsoft 365 F1 user, given that F1 does not include Office desktop or web editing? This is the one place where the published access-point list and the published F1 entitlements appear to be in tension, and it is load-bearing for whether a frontline use case can reach the included tier at all.
Related
- [[2026-07-20-deskless-worker-identity-agent-distribution]]
- [[2026-07-13-kwik-trip-deskless-agent-distribution]]
- [[2026-08-03-every-microsoft-copilot-studio-trap]]
- [[2026-09-25-every-copilot-org-chart-autopilot]]
Sources
Primary — Microsoft licensing documentation
- Manage Microsoft Copilot Chat —
ms.date: 2026-10-01,updated_at: 2026-10-05. The "Microsoft Copilot Chat eligibility" list; the decisive source for F1/F3/Office 365 F3 inclusion and for the "baseline experience" qualification. - License Options for Microsoft Copilot —
ms.date: 2026-09-25,updated_at: 2026-09-30. Web-based vs work-based chat split; add-on prerequisite lists including Microsoft 365 F1, Microsoft 365 F3, Office 365 F3; commercial vs US Government asymmetry. - Microsoft Copilot requirements —
ms.date: 2026-10-05. Requirements-at-a-glance matrix; Entra ID account requirement. - Microsoft Copilot service description — feature-availability table by cloud environment; footnote 2 defines Premium (paid-license) features including work data and organizational context.
Microsoft marketing / announcement tier
- Microsoft Copilot Plans and Pricing - Enterprise — $30/user/month add-on list price (read via domain-restricted search summary, not fetched directly; verify before client use).
- Copilot for all: Introducing Microsoft 365 Copilot Chat — 2025-01-15 announcement establishing the prior product generation (cited for existence and date only; body not fetched).
Attempted and unreachable
- Microsoft Product Terms,
https://www.microsoft.com/licensing/terms/— single-page application.curlwith a browser User-Agent returned navigation chrome only; headless-browser renders of three candidate product-offering slugs returned "not available on this date";/licensing/terms/searchreturned an error page. No contract-tier citation available from this run.
Secondary — evidence of belief, not of terms (inherited from the parent brief, not re-verified)
- Microsoft 365 Frontline Licensing in 2026 — 2Data (analyst source).
- Microsoft 365 F SKU Licensing Guide — Redress Compliance (analyst source).
Vault
~/rdco-vault/06-reference/research/2026-07-20-deskless-worker-identity-agent-distribution.md~/rdco-vault/01-projects/phdata/2026-07-13-kwik-trip-deskless-agent-distribution.md~/rdco-vault/06-reference/2026-08-03-every-microsoft-copilot-studio-trap.md~/rdco-vault/06-reference/2026-09-25-every-copilot-org-chart-autopilot.md