A family of personal and work AI experiences whose identity, grounding, editing, and agent boundaries matter.
Conversation & research · Changing · Documentation checked 2026-10-04
Personal Microsoft Copilot and Microsoft 365 Copilot / Copilot Chat, identified per guide.
Subscription, identity, tenant policy, app, and regional rollout determine capabilities. GitHub Copilot is a separate coding product.
What the platform is for
Copilot can help with public questions, supplied files, grounded work answers, persistent Pages, Notebooks, and Researcher reports. The first step is identifying the product and account. A personal chat and a work-grounded answer can look similar while drawing on very different information and policies.
Know the product boundary
Personal Microsoft Copilot, Microsoft 365 Copilot Chat, the licensed Microsoft 365 Copilot experience, Agent Builder, and Copilot Studio differ. Researcher has documented license requirements and replaces the older Deep Research experience. GitHub Copilot is a separate coding product with its own platform map.
How the components connect
Identity and licensing establish available context. Files and Notebook references deliberately narrow information. Researcher investigates; Pages supports refinement and collaboration. Agent Builder provides a limited knowledge-agent path, while Studio supports richer orchestration. Power Automate can provide a separately governed fixed workflow. None of these names automatically grants access to every work record.
A beginner starting point
Start with the editions-and-context guide. Ask one public or supplied-file question and verify it. Then learn Pages and Notebook source scope. Use Researcher for a broader report when eligible. Approach agents only after you understand knowledge permissions and the differences between drafting and taking an action.
Limits and data choices
Existing organizational oversharing can be exposed through permitted retrieval. File grounding is not unlimited, and shared Pages / Notebooks have their own source and audience concerns. Personal and work privacy rules should not be mixed. This release does not give complete per-app Word, Excel, PowerPoint, or every Frontier / preview walkthrough.
The technical path
Continue to Power Automate for cloud / desktop processes and approvals. Use official Copilot Studio and Microsoft Learn material for agents, connectors, identity, administration, and deployment. A custom application or metered agent needs its own licensing and security design rather than inheriting a personal Copilot subscription.
Feature map
Personal Copilot, Copilot Chat, and work context
Identify the Copilot edition and the information it is entitled to use.
Researcher and evidence checks
Create a scoped report from web sources and, where licensed, permitted work information.
File uploads and Copilot Pages
Move supplied information into a persistent editable page without confusing personal uploads and work grounding.
Copilot Notebooks and reference scope
Build a bounded collection of references for grounded answers and reusable instructions.
Voice and Vision across Copilot editions
Share only the screen, camera, or page needed for a spoken explanation.
Agent Builder and Copilot Studio
Separate a knowledge assistant from a broader agent with tools, workflows, and publishing channels.
Complete workflows
From Researcher report to a reviewed Page
Build a cited briefing and a persistent draft Page using the correct Copilot identity.
From a reference collection to a FAQ agent
Use a bounded source collection to design a retrieval-only workshop FAQ agent.
Coverage and availability
Models, modes & conversation
Covered: Personal / work conversation context explained; exact model selector is account-specific.
Search, research & sources
Covered: Researcher and work / public-source boundary; older Deep Research retired.
Files, analysis & code
Covered: Personal uploads differ from work grounding; exact application features vary.
Images, video, audio & voice
Not established: Personal Voice / Vision covered; full edition-specific media generation not established.
Projects, instructions & memory
Covered: Notebook references and instructions; universal memory parity not inferred.
Editing surfaces & deliverables
Not established: Pages and Notebooks; detailed Word / Excel / PowerPoint guides deferred.
Agents, skills, plugins & MCP
Covered: Agent Builder versus Studio; external action / connector authority distinguished.
Orchestration & scheduling
Covered: Studio orchestration and Power Automate are separate implementation paths.
APIs, SDKs, deployment & evaluation
Separate product: Developer APIs and deployment are separate products, with Microsoft Learn as technical path.
Sharing, privacy & governance
Covered: Source permissions, sharing, licensed grounding, and identity boundaries.
Plans, devices & accessibility
Not established: License and client relationships included; full device, region, quota, and accessibility matrix not established.
Sources and verification
Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.
Personal Copilot and Microsoft 365 boundaries · Microsoft
Copilot Chat FAQ · Microsoft
Get started with Researcher · Microsoft
File upload in personal Copilot · Microsoft
How Copilot Pages works · Microsoft
How Copilot Notebooks works · Microsoft
Add references to a Copilot Notebook · Microsoft
Copilot Vision and Voice · Microsoft
Agent Builder versus Copilot Studio · Microsoft
Copilot Studio technical documentation · Microsoft