Copilot Chat (free) vs Microsoft 365 Copilot: the boundary AU buyers keep getting wrong

A consistent pattern in Copilot procurement conversations across Australian organisations is the assumption that the AI experience a user has already encountered in Microsoft Teams or at copilot.microsoft.com is the same product being discussed in the licensing quote. It is not. There are two distinct Copilot products in the Microsoft commercial line-up, and conflating them leads to budget assumptions, deployment plans and governance policies built on the wrong foundation.

What Copilot Chat actually is

Copilot Chat (previously called Microsoft Copilot) is the general-purpose AI assistant Microsoft includes at no additional charge with eligible Microsoft 365 commercial licences. It is accessible through copilot.microsoft.com, through the Microsoft 365 app, and through a pinned chat experience in Teams. When a user is signed in with their work account, Copilot Chat operates in a commercial data-protection mode: Microsoft does not use the conversation content to train models, and the session data is not retained beyond the conversation.

Copilot Chat answers from the model's general knowledge and from any files or context the user explicitly pastes or uploads in the conversation. It does not connect to the Microsoft Graph. It does not read the user's Outlook inbox, SharePoint files, Teams conversations or OneDrive documents unless the user explicitly provides that content in the prompt. The boundary is important: Copilot Chat is a capable general-purpose assistant, and it has no access to organisational data it has not been directly given.

What Microsoft 365 Copilot adds

Microsoft 365 Copilot is a paid add-on licence, currently priced in Australia at around $45 per seat per month on top of an eligible base licence (Microsoft 365 E3, E5, Business Standard or Business Premium). The "Copilot for All" promotional pricing Microsoft updated in April 2026 brings volume discounts into play at 1,000 seats and above, but the add-on remains a material per-seat cost for most Australian organisations.

What the paid licence enables is Graph grounding. Microsoft 365 Copilot connects to the Microsoft Graph at query time, which means it can reason over the signed-in user's emails, calendar, documents, SharePoint sites, Teams channels and OneDrive files in real time. It respects the Entra ID permissions the user holds, it surfaces only what the user is already entitled to see, governed by the existing permission model. That grounding is the core of the product's value for enterprise productivity, and it is the feature that is entirely absent in Copilot Chat.

• Copilot Chat: available at no extra cost on eligible M365 licences. General knowledge only. No Microsoft Graph access. No Outlook, SharePoint, Teams or OneDrive data unless the user explicitly provides it.
• Microsoft 365 Copilot: paid add-on at ~$45/seat/month. Full Microsoft Graph grounding. Integrated into Word, Excel, PowerPoint, Outlook, Teams, OneNote and SharePoint experiences. Governed by Entra ID permissions and Microsoft Purview labels.
• Meeting summaries in Teams: the Teams Premium licence adds AI-generated meeting summaries and notes as a separate feature. This is distinct from both Copilot Chat and Microsoft 365 Copilot, and the boundary between Teams Premium features and M365 Copilot Teams features is a second common source of confusion.

Who needs which licence

The question Frontrow asks in every Copilot scoping conversation is: what does this person need the AI to do? The answer determines which licence is warranted.

A staff member who wants a capable AI assistant for drafting emails from scratch, researching a topic using general knowledge, summarising a document they have been sent, or thinking through a problem gets meaningful value from Copilot Chat at no incremental licensing cost. That use case does not require Graph access and should not be used as a justification for the paid add-on.

A staff member who needs the AI to draft meeting follow-up emails from the actual Teams meeting transcript, summarise a SharePoint site they manage, locate a specific contract in OneDrive, or synthesise information from across multiple Outlook threads needs Microsoft 365 Copilot. The value of the product depends entirely on Graph grounding, and Graph grounding requires the paid licence.

The Australian organisations that land the strongest Copilot return on investment are those that start with a workflow audit, not a uniform licence-to-all rollout. The audit identifies which roles genuinely generate value from Graph-grounded AI, quantifies the productivity gain, and produces a defensible business case for the paid seats. Roles where the value case is marginal get Copilot Chat and get Copilot Chat well, rather than a paid licence that sits underused.

The governance boundary that matters

Copilot Chat in work mode does not expose the Microsoft Graph, but it does accept content the user pastes in. An organisation's AI acceptable-use policy needs to address both surfaces separately. Copilot Chat is not inherently unsafe, but it is a different data-handling surface from Microsoft 365 Copilot, and treating them as identical in the AI governance policy creates gaps that Microsoft Purview cannot close on its own.

Microsoft 365 Copilot's data handling is governed by the tenant's existing Purview labels, DLP policies and Entra permissions. Copilot Chat's data handling is governed by the Microsoft commercial terms for that product, which is a meaningful protection but not the same as the tenant-specific control plane. Both are commercially sound products. Both need to appear distinctly in the acceptable-use framework.