№ 06Learn With Darin · Field Guide

Microsoft Copilot: a practitioner’s field guide.

The Microsoft Copilot suite isn't one product. It's eight, with overlapping names and a licensing maze. This is the map: which Copilot does what, what each tier actually unlocks, and the workflows that survive the pricing PDF.

Updated May 2026 ~30 min read M365, BizChat, Studio, Windows
Part 01

The Copilot landscape, untangled

The single most common reason "Copilot doesn't work" complaints exist is that the complainer has the wrong Copilot. There are eight distinct Microsoft products with "Copilot" in the name as of May 2026, and they do meaningfully different things. Here's the map:

Product Audience What it actually is
Copilot Chat (free) Anyone with a Microsoft account The web/mobile chat at copilot.microsoft.com. Free tier of the consumer Copilot. Like ChatGPT Free, but Microsoft.
Copilot Pro Individuals $20/mo consumer plan. Better models, image gen, integrates with the personal Microsoft 365 (Word/Excel/etc) installs.
Microsoft 365 Copilot (Business) Small businesses (≤300 users) Copilot in Word/Excel/PowerPoint/Outlook/Teams. $18–21/user/mo. Requires an existing M365 Business plan.
Microsoft 365 Copilot (Enterprise) Larger orgs Same in-app Copilot, plus BizChat, plus Microsoft Graph access. $30/user/mo. Requires E3/E5/Business Standard/Premium.
BizChat M365 Copilot users The "Microsoft 365 Chat" product: a cross-app chat that reasons over your email, calendar, files, Teams chats. Included with M365 Copilot.
Windows Copilot Windows 11 users The OS-level Copilot button/key. Mostly the consumer Copilot Chat with some Windows-specific actions. Free.
Copilot Studio Builders & admins The agent-building platform. $200/tenant/mo standalone. Bundled into Enterprise tiers. Build custom agents, workflow bots, plugins.
GitHub Copilot Developers Code completion + Copilot Chat in your IDE. Owned by GitHub, separate billing, separate model lineup. Out of scope for this guide.

"Microsoft Copilot" by itself can mean any of the first six. When someone says "we got Copilot at work," ask three questions before you advise them on anything: which Copilot, which tier, and on which apps.

Note Microsoft also shipped a "Copilot Cowork" capability in 2026, which is (unfortunately) a Microsoft concept and a separate Anthropic product (also called "Cowork"). Microsoft's "Copilot Cowork" describes long-running multi-step agent execution within M365. Anthropic's Claude Cowork is the desktop agent surface covered in our Cowork guide. Same word, two products. The collision is real.
Part 02

The licensing maze

Before any feature decision, you need to understand the licensing. Microsoft's pricing structure for Copilot in 2026 is a pyramid of dependencies:

Individual

  • Copilot Chat (free): free with any Microsoft account. Web at copilot.microsoft.com, mobile apps, Windows integration.
  • Copilot Pro ($20/user/mo): adds Copilot inside Word/Excel/PowerPoint/Outlook for personal/family Microsoft 365 subscriptions, priority on advanced models, image gen.

Business (≤300 users)

  • You need a base Microsoft 365 Business plan (Basic, Standard, or Premium).
  • M365 Copilot Business sits on top: $18–21/user/mo (annual; promo pricing through June 2026 keeps it at $18). Monthly commitment is ~$25.20.
  • Adds Copilot in Word, Excel, PowerPoint, Outlook, Teams, Loop. Limited BizChat. No Microsoft Graph deep integration.

Enterprise

  • You need a base Microsoft 365 E3 or E5 plan. Or, in some cases, Business Standard / Business Premium.
  • M365 Copilot Enterprise: $30/user/mo.
  • Adds full BizChat (cross-app, cross-Graph), Copilot in all M365 apps, Microsoft Graph integration, semantic search across SharePoint/OneDrive/Outlook/Teams, and access to Copilot Studio Lite.

The new top tier: M365 E7 Frontier Suite

Launching May 1, 2026, the E7 Frontier Suite bundles M365 E5 + M365 Copilot + Agent 365 into a single SKU at $99/user/mo. Agent 365 is Microsoft's unified control plane for AI agents: think governance, observability, and policy enforcement across all the agents your org runs (Copilot Studio, in-app Copilots, third-party agents).

If you're an enterprise procurer, E7 is the SKU on the slide deck right now. If you're a practitioner: it's a meaningful capability uplift on the agent governance side, but for everyday Copilot-in-Word work, the difference vs an E5 + M365 Copilot bundle is mostly invisible day-to-day.

Copilot Studio standalone

  • $200/tenant/month for 25,000 messages across all custom agents.
  • Additional capacity packs.
  • Separate from per-user Copilot. Copilot Studio is tenant-level licensing for the platform, not per-seat.
Warn The "Copilot is an add-on, not a standalone" framing matters. You cannot purchase M365 Copilot without a base Microsoft 365 plan. If you're evaluating cost, calculate: base plan + Copilot. The $30/user/mo Enterprise number is the add-on on top of your existing E3/E5 spend.

What this means in practice

If your IT department says "we have Copilot," they mean one specific configuration. The questions to clarify:

  1. Is this the Business or Enterprise SKU?
  2. Is it deployed to all users, or a pilot group?
  3. Is BizChat enabled? (Often gated behind admin consent + a tenant configuration step.)
  4. Is Copilot Studio enabled? Who can build agents?
  5. What's the data residency posture? (Microsoft Graph integration means Copilot reads your corporate data; admins gate this.)
Part 03

Per-app: what's actually useful

The Copilot suite spans every M365 app. Most aren't equally useful. Here's the practitioner take on each, and the one feature per app that's worth turning on first.

Word

Copilot in Word can draft, edit, summarize, rewrite. The killer feature is "Rewrite this section in [tone/length]". Select a paragraph, ask for the change, watch it execute in place. Faster than ChatGPT for in-document iteration because there's no copy-paste round-trip.

What disappoints: long-document coherence. For a 30-page report, Copilot's rewrites of section 3 don't have full awareness of section 19. Use it for paragraph-level surgery, not document-level vision.

Excel

Excel got the biggest 2026 upgrades. Two killers:

  • Python in Excel via Copilot: ask Copilot to do something complex (regression, time-series forecast, data cleanup), and it generates Python that runs in your workbook. The Python infrastructure was already there; Copilot makes it accessible without writing code.
  • The Excel Agent (April 2026 release): a multi-step agent that can act across the spreadsheet, cleaning data, building a chart, generating a summary, formatting. Where regular Copilot edits cells, the Agent runs sequences.

What disappoints: Copilot's spreadsheet hallucinations are subtle. If it misreads a column header (especially with merged cells, footnote symbols, or weird formatting), the formulas it proposes can be confidently wrong. Always sanity-check formulas Copilot generates against the actual data in row 1.

PowerPoint

The 2026 PowerPoint upgrade is big:

  • Image model picker: choose between GPT-Image, Flux, or Auto when generating slide visuals. Each has different style strengths; experiment.
  • Microsoft AI Image 2 Efficient: faster image edits in-place.
  • Web grounding: Copilot can pull from public webpages as source material when building a deck, so slides reference current information without copy-paste.
  • The PowerPoint Agent: builds full decks from a prompt, with consistent style across slides.

What disappoints: brand-consistent decks. Your corporate template has fonts, colors, layouts the Copilot doesn't always respect, even with template-aware features. Expect to do a final pass to align visuals.

Outlook

Outlook is where the agentic upgrades land hardest. As of 2026 you get:

  • Copilot Chat in Outlook reasons over your entire inbox, calendar, and meeting transcripts. "What did Sarah say about the launch in our last three threads?" gets a real answer with citations.
  • Email triage agents: Copilot can categorize and respond to routine email under your direction.
  • Meeting prep: surface relevant docs and prior conversations before a meeting starts.
  • Action-item extraction: Copilot reads recent threads and proposes a list of things you owe people.

The killer feature: Copilot's awareness of "what you should be doing about this email". Hover over a thread; Copilot suggests the action: reply, schedule, delegate, ignore. It's right often enough to be useful, wrong rarely enough to not be insulting.

Teams

  • AI meeting recaps: every meeting gets an automatic summary, action items, and decision tracker.
  • Real-time translation: live captions across languages, meaningful for international teams.
  • Copilot in chat: "summarize this channel since yesterday" works.
  • Rule-based app enablement: admins can enable Copilot per-team via rules, not per-user.

The disappointment: meeting recap accuracy on multi-speaker calls with overlap or accents is good but not great. Treat the recap as a starting point you edit, not a finished artifact.

OneNote

OneNote's Copilot is best for "summarize what I wrote this week" and "find that note about X." It's quietly the most reliable Copilot in the suite because OneNote's structure is simple and Copilot's task is bounded.

Loop

Loop's Copilot helps draft components, summarize live docs, and catch up on changes. It's underrated because Loop itself is underused. But if your team uses Loop for collaborative artifacts, the Copilot makes catch-up dramatically faster.

Part 04

Windows Copilot

Windows Copilot is the system-level Copilot experience on Windows 11. As of May 2026, it's mostly a thin wrapper over the consumer Copilot Chat with a few Windows-specific actions:

  • System-level invocation: Win+C opens Copilot from any app.
  • Some Windows-specific actions: change settings ("turn on dark mode"), open apps, search files via Copilot's reasoning.
  • OS-level voice activation in supported regions.
  • Integration with Phone Link for cross-device tasks.

What it isn't: a Mac-app-equivalent productivity layer. The actions Windows Copilot can take system-wide are intentionally narrow. For real work, you reach for the in-app Copilots, BizChat, or Copilot Studio agents.

Tip Windows Copilot's main practical value is "settings on demand": instead of hunting through Settings for the toggle you want, ask Copilot. "Disable startup apps for Spotify" works. "Set Bluetooth to never auto-connect to my old earbuds" works. It's not transformative, but it saves you from Microsoft's settings UI maze, which is a real value-add on its own.
Part 05

BizChat (Microsoft 365 Chat)

BizChat is the cross-app surface of M365 Copilot. It's where Copilot gets useful for knowledge work, not because the chat itself is special, but because it has access to your work data via Microsoft Graph.

What BizChat can answer that the in-app Copilots can't:

  • "What's the latest version of the Q3 strategy doc, and what changed since the version I read in March?" This pulls SharePoint version history.
  • "Has anyone in the company written about [topic] in the last quarter?" Searches across SharePoint, OneDrive, Outlook, Teams.
  • "Summarize what's been happening on Project Atlas this week." Aggregates across email threads, Teams channels, meeting recaps, doc edits.
  • "Schedule 30 minutes with Sarah and Lin sometime next week, ideally Tuesday or Wednesday morning, on the topic of the launch checklist." Checks calendars, drafts an invite, attaches relevant docs.

The BizChat reach

BizChat reads from Microsoft Graph, which means it can see:

  • Your email and calendar.
  • Files in SharePoint and OneDrive that you have access to.
  • Teams channels and chats you're a member of.
  • Meeting recaps and transcripts where they exist.
  • People profiles and org chart.

What BizChat can't see: anything outside Microsoft Graph. Slack channels (unless mirrored), Notion docs, Google Drive, your local files (unless synced via OneDrive). The reach is broad within the Microsoft ecosystem, but it's a Microsoft ecosystem reach, not a universal one.

The web fallback problem

BizChat's known weak spot: when it can't find an answer in your enterprise data, it falls back to the public web. The transition isn't always clearly signposted, and the answers from web fallback can feel authoritative even when they're generic. Look for citations. If BizChat answered without citing internal sources, it probably went to the web. Verify accordingly.

Building agents inside BizChat

One of the late-2025 / early-2026 additions: you can build lightweight Copilot agents inside BizChat using natural language. Tell Copilot Studio (via BizChat) what you want the agent to do, choose its knowledge sources, and publish. The agent then becomes accessible to your team.

This is qualitatively easier than the full Copilot Studio experience and is the right starting point for "I want a custom agent" requests from a non-developer.

Part 06

Copilot Studio

Copilot Studio is the platform for building custom agents. It's a real product, not just a wizard. Microsoft positions it as the answer to "what's the IT-sanctioned way to build internal AI agents."

What you can build

  • Q&A bots that reason over a knowledge base (SharePoint, file shares, websites).
  • Action-taking agents (file a ticket, schedule a meeting, run an approval flow).
  • Workflow agents that orchestrate multi-step processes (onboarding, expense routing).
  • Custom agents inside M365 Copilot (so they appear next to BizChat for your users).
  • External agents (deployed to Teams, websites, mobile apps).

The 2026 capabilities

  • Generative answers: AI-generated responses grounded in sources you specify, with citations.
  • Generative actions: AI dynamically selects which plugins / tools to invoke based on conversation context.
  • Agent evaluations (GA in 2026): customizable test sets to validate agent performance across scenarios. The right primitive for "how do I know my Copilot Studio agent is reliable enough to ship?"
  • Multi-agent orchestration (GA): agents coordinating with each other, including via Microsoft's Agent-to-Agent (A2A) protocol, Microsoft's contribution to the open standards push for inter-agent communication.

Studio vs the in-app Copilots vs BizChat agents

The right tool depends on the ambition:

i.

For "this team needs an FAQ bot from our SharePoint"

→ Build it inside BizChat using natural-language agent authoring. Cheapest, fastest, accessible.

ii.

For "we need a real workflow agent for IT ticket triage"

→ Copilot Studio. Use generative actions to dynamically select tools (ticket APIs, knowledge base, approval flow). Agent evaluations to validate before rollout.

iii.

For "an agent that runs across SharePoint, Outlook, AND a third-party CRM"

→ Copilot Studio with custom connectors (or MCP servers, expanding through 2026). Multi-agent orchestration for the cross-system handoffs.

iv.

For "a Copilot inside Word that helps with our specific report style"

→ Copilot Studio agents installed into M365 Copilot. They appear alongside BizChat as scoped tools.

Studio's learning curve

Copilot Studio is meaningfully more complex than the BizChat in-line agent builder. It's closer to Power Platform than to ChatGPT: you're building flows, configuring connectors, defining triggers, writing prompts, evaluating outputs. Plan a multi-week ramp for non-technical builders. It is not a "ten minutes from idea to shipping" tool. It is, however, the right tool for production agents that touch real org data.

Part 07

Agent 365

Agent 365 is the new (May 2026) governance layer for everything agentic in your tenant. Bundled with the E7 Frontier Suite ($99/user/mo). Practical features:

  • Inventory: a tenant-wide list of every agent (Copilot Studio agents, third-party agents, BizChat-built agents), with owners, scopes, and last-used timestamps.
  • Policy enforcement: which agents can be installed, where they can run, what data they can access.
  • Observability: usage metrics, error rates, who's invoking what.
  • Lifecycle: deprecation, rollback, version pinning.

The framing Microsoft uses: "Agent 365 is to agents what Active Directory is to identities." It's pitched at orgs whose IT is starting to ask "how many AI agents are running in our tenant, who owns them, what are they doing," and finding they don't know.

If you're an individual practitioner, you won't touch Agent 365. If you're an admin in a large org with multiple Copilot Studio builders, it becomes core infrastructure.

Part 08

Capability matrix

Capability Free Chat Copilot Pro M365 Business M365 Enterprise E7 Frontier
Web/mobile chat
Copilot in Word/Excel/PPT/Outlookpersonal M365 only
Copilot in Teams
BizChat (limited)
BizChat (full Graph)
Microsoft Graph integrationpartial
Image generationlimited
Excel Python via Copilot
Excel/PowerPoint/Planner Agents
Build agents inside BizChatlimited
Copilot Studio Lite
Full Copilot Studio (standalone $200/tenant)add-onadd-onadd-onadd-onincluded
Agent 365 governance
Windows Copilot system actions
Phone Link integration
Real-time meeting translation
Part 09

Best practices

i.

Pick the right Copilot for the task, not the one that opened first.

If you're cross-app reasoning (BizChat). If you're editing in place (in-app Copilot). If you want OS settings (Windows Copilot). If you're building automation (Studio). The wrong-tool habit is the most expensive Copilot mistake. You can spend months thinking "Copilot is dumb at X" when X was just the wrong surface for the job.

ii.

Verify Excel formulas Copilot generates against the data.

Copilot's Excel hallucinations are subtle and authoritative-sounding. Mismatched columns, off-by-one row references, or misread headers produce wrong-but-plausible formulas. Always sanity-check the first cell of any formula Copilot creates against what you'd compute by hand.

iii.

Treat BizChat citations as the trust signal.

If BizChat cites internal sources (a SharePoint doc, a Teams message, an email), trust the answer to the level of the source. If BizChat answers without citations, it likely went to the public web; treat the answer the same way you'd treat any web search result.

iv.

Outlook's action-aware suggestions repay attention.

The "what should you do about this email?" affordance is undermarketed and surprisingly good. Spend a week consciously checking it on every email you'd otherwise quickly skim. By the end of the week you'll know which suggestion patterns are reliable and which ones aren't, and your inbox triage will be measurably faster.

v.

For agents, start with BizChat-built natural-language agents before Copilot Studio.

Most "we need an internal agent" requests are a Q&A bot with a knowledge source. BizChat's in-line agent authoring handles that in 10 minutes. Reach for full Copilot Studio when you actually need workflow logic, multi-agent orchestration, or evaluations, not before.

vi.

Copilot vs ChatGPT: use Copilot when the task lives in M365.

If you're editing a Word doc, working in Excel, drafting an Outlook email, or asking about your inbox, Copilot wins because it's in the document/data. If you're brainstorming, doing research, or working with non-Microsoft data, ChatGPT or Claude usually wins. The unifying principle: pick the tool whose context already contains your task.

vii.

Audit your Copilot exposure annually.

Microsoft Graph's reach is broad, and Copilot inherits it. Every year, walk through what BizChat could currently surface to a curious employee: files in SharePoint they technically have access to but no one expected them to read, calendar items, meeting transcripts. Copilot didn't create the access; it just made it queryable. Where the answer surprises you, the access lattice was already wrong; fix that, not Copilot.

viii.

Don't promote Studio agents straight to org-wide.

Use the agent evaluations feature. Run a controlled rollout. Watch the actuals via Agent 365 (if you have E7) or Copilot Studio's own metrics. An agent that worked great on the demo dataset can fail in unexpected ways on real org data. The rollout discipline is the same as any production system; it just feels easier because the building was easy.

Part 10

Troubleshooting playbook

The patterns to recognize. Each one has a short fix.

"Copilot isn't showing up in Word"

Three suspects, in priority order:

  1. License not assigned. Even with a tenant-wide M365 Copilot purchase, individual licenses must be assigned in the M365 admin center. Check your account.
  2. Old Office build. Copilot requires recent versions of the Office apps. Update via Office's built-in update or Microsoft Update.
  3. Tenant config. Some admins disable Copilot per-app or per-group. Check with your admin.
"BizChat doesn't have access to a file I expected"

BizChat respects your existing M365 permissions. If you can't open the file in SharePoint, BizChat can't read it. Common cases:

  • The file is in a SharePoint site you have access to but BizChat hasn't indexed yet. Indexing can lag by hours after permission changes.
  • The file is OneDrive-private to someone who hasn't shared it with you.
  • The file is in Teams chat (DMs) you're not part of.
"My Copilot Studio agent works in test but fails in production"

Common culprits:

  • Permissions delta: the test environment used your credentials; production uses the agent's service principal, which has different access.
  • Connector throttling: production load hits API rate limits the test never approached.
  • Edge-case input: real users phrase things differently than your test set. Use the agent evaluation feature to expand the test set.
"Excel's Python execution failed silently"

Python runs in a Microsoft-managed cloud sandbox. Common silent failures: timeouts on large datasets, unsupported imports, output formatting issues. Check the Python pane (View → Show Python Pane) for the actual error. Copilot doesn't surface Python errors in chat as clearly as it should.

"The PowerPoint Agent built a deck that ignores our brand"

Brand-aware deck generation requires a template the Agent can recognize. Set the corporate template as your default, and the Agent uses it as a baseline. If you start from blank, the Agent makes its own visual choices. The template is the brand contract.

"Outlook agentic actions are ignoring my preferences"

The agentic features learn from your accepts/rejects. Early on, expect to reject more than accept. After a couple of weeks of consistent training (consciously rejecting "no don't draft this kind of email," accepting "yes this is the right tone"), the suggestions tune meaningfully. Skipping the calibration period and concluding "Copilot is dumb at email" is the wrong inference.

"BizChat keeps returning generic answers"

Most likely the source data isn't in Microsoft Graph (check: is it in SharePoint, OneDrive, Outlook, or Teams? If not, BizChat can't see it), or BizChat is falling back to the web (check the citations). For sources outside Graph, you need a Copilot Studio connector or an MCP integration.

Part 11

Closing thought

Microsoft's Copilot strategy is the messiest and the most ambitious in the AI productivity space. Eight products. Three SKUs of the same product. A licensing pyramid that forces you to think about Copilot before you can buy Copilot. A naming collision with another vendor's product. The complexity is real and it's not going away.

Microsoft Copilot rewards the practitioner who picks the right surface for the task — and frustrates the one who treats them as one product. — TWD

The reason to pay attention anyway: the integration depth into M365 is unmatched, and for the millions of workers whose day is in Word/Excel/Outlook/Teams, that depth is the difference between an AI that helps you in your work and an AI you switch tabs to consult. BizChat reasoning over your inbox, Excel agents running Python in your workbook, PowerPoint agents grounded in public web sources: these are real productivity wins.

The strategic move for individual practitioners: get a Copilot Pro subscription if you live in personal M365, or push your IT to enable BizChat if you live in enterprise M365. Skip the rest until the use case demands it. For builders: start with BizChat agent authoring; reach for Studio when you have a real workflow to encode. For admins: enable Agent 365 governance early; the inventory question is one you'll be asked, and "we don't know" is a bad answer.

Microsoft's Copilot roadmap moves fast. What's true in May 2026 won't be true in November. The official source: microsoft.com/microsoft-365/roadmap. Treat any guide (this one included) as a snapshot.