O6: Copilot Ecosystem

“Copilot” is a brand and product family, not a single product. Microsoft has embedded Copilot across its entire stack — from code editors to security operations. This module maps the ecosystem, explains the shared architecture, and shows how to extend Copilots with custom capabilities. For AI agent patterns that Copilots build on, see O2: AI Agents Deep Dive. For the platform hosting Copilot models, see O4: Azure AI Foundry.

Core Architecture

Every Microsoft Copilot shares the same foundational pattern:

┌─────────────────────────────────────────────┐
│              Copilot Experience              │
│  (Chat UI, inline suggestions, side panel)   │
├─────────────────────────────────────────────┤
│            Orchestration Layer               │
│  (Prompt construction, tool routing, safety) │
├──────────┬──────────────┬───────────────────┤
│  LLM     │  Grounding   │  Product          │
│  (GPT-4o)│  Data        │  Integration      │
│          │  (Graph, code,│  (Editor, Office, │
│          │   docs, web)  │   Azure portal)   │
└──────────┴──────────────┴───────────────────┘

The grounding data is what makes each Copilot different — same model, different context.

The Copilot Stack

Copilot Comparison

Microsoft 365 Copilot

Grounding: Microsoft Graph — your emails, files, calendar, chats, contacts. Copilot sees what you have access to (respects existing permissions and RBAC).

GitHub Copilot

GitHub Copilot has evolved from code completion into a full development platform:

Grounding: Your open files, repository context, language documentation, web search.

# GitHub Copilot tiers
Individual:  $10/month  — code completion + chat
Business:    $19/month  — + org policies, audit logs
Enterprise:  $39/month  — + knowledge bases, fine-tuning

Copilot for Azure

Available directly in the Azure Portal — no additional cost:

Grounding: Azure Resource Graph, Azure Monitor, Azure documentation.

Copilot Studio

Copilot Studio is the low-code platform for building custom copilots:

Best for: customer support bots, HR assistants, IT help desks — where non-developers need to build and maintain AI experiences.

Security Copilot

Purpose-built for security operations:

Extensibility

Plugins

Plugins extend Copilot’s capabilities with custom actions:

{
  "schema_version": "v1",
  "name": "contoso-crm",
  "description": "Look up customer information in Contoso CRM",
  "functions": [{
    "name": "get_customer",
    "description": "Get customer details by name or ID",
    "parameters": {
      "customer_id": { "type": "string", "description": "Customer ID or name" }
    }
  }]
}

Declarative Agents

Custom Copilot personas with specific knowledge, instructions, and tool access — deployed as M365 Copilot extensions:

Extension Types

Key Takeaways

1. Copilot = brand, not product — same LLM, different grounding data per domain
2. The Copilot Stack: User Layer → Orchestration → Data & Intelligence → Foundation
3. M365 Copilot is grounded in Microsoft Graph (your org’s data)
4. GitHub Copilot has evolved into a full development platform with agents
5. Copilot Studio enables non-developers to build custom copilots
6. Extend any Copilot via plugins (actions), declarative agents (personas), or Copilot Studio (full custom)
7. Security, cost, and grounding data sources are the key differentiators across the family