Microsoft uses Copilot across several products, but the important distinctions are account, grounding, licence and action. Start with what the user signs in with and what data the experience can access.
Microsoft is also changing names. Its current documentation says Microsoft 365 Copilot is now named Microsoft Copilot, while Microsoft 365 Copilot Chat is now Microsoft Copilot Chat. Some interfaces may retain older labels during the transition (Microsoft Learn).
Microsoft Copilot Chat for work or education
Copilot Chat is available to eligible Microsoft 365 work and education users without the dedicated Copilot add-on licence. It is primarily grounded in the web.
Users can provide work content directly, use awareness of open content in some apps, or access enabled agents. That is not the same as broad work-data grounding across their Microsoft Graph.
Use it for controlled web research, drafting and work with explicitly supplied context. Confirm the tenant's admin settings and teach users how to recognise their signed-in work experience.
Microsoft Copilot with the add-on licence
The licensed Microsoft Copilot experience adds grounding in work data such as files, email, meetings and chats the user is permitted to access, plus deeper integration in Microsoft 365 apps and additional administrative capabilities.
This is why data readiness matters. Copilot honours existing access. It does not repair an overshared SharePoint site for you.
Check current eligible subscriptions, feature availability and terms on Microsoft's licensing page. Do not use an old annual price from a blog post as procurement evidence (Microsoft licensing).
Microsoft Copilot for personal use
The consumer experience uses a personal Microsoft account. It is separate from the work and education experiences governed through a Microsoft 365 tenant.
For business data, the practical rule is simple: use the service and account approved by your organisation. A familiar Copilot logo does not prove that enterprise controls apply to the session in front of you.
Copilot Studio
Copilot Studio is Microsoft's platform for creating and managing agents. Builders can add knowledge, instructions, tools and channels.
Licensing and metered usage depend on the scenario. Connections to SharePoint, Microsoft 365 data or external systems can introduce additional permissions and governance work. The person creating an agent remains responsible for its design, testing and end-user warnings (Copilot Studio overview).
Copilots inside Microsoft products
Microsoft also uses the Copilot name for experiences in products such as GitHub, Security and Dynamics 365. These are product-specific services with their own licences, data boundaries and administration.
Do not assume a policy written for Microsoft Copilot automatically covers every product containing the word Copilot.
A five-question buying check
For any Copilot experience, ask:
- Which account signs in?
- Which data can ground the response?
- Which actions or connected agents are available?
- Which licence and consumption charges apply?
- Which admin, audit and data-protection controls govern it?
The proof boundary
This map reflects Microsoft's public documentation on 24 August 2026. Product names and capabilities change quickly. Your tenant configuration, licence agreement and enabled agents determine what a particular user can actually do.
For help turning the product map into a sensible tenant decision, join Microsoft Copilot Adopters.