Five-Layer Capability Model

Microsoft’s five-layer capability model is a practical map for choosing the right starting point in the Microsoft AI portfolio. It distills the official “adopt → extend → build” journey from Adopt, extend and build Copilot experiences across the Microsoft Cloud, expands it with the hands-on tiers from the Explore the Copilot stack module and the Copilot stack view in Creating Generative AI Experiences with the Microsoft Cloud, and grounds it in Azure’s Application design for AI workloads.

The result is a single progression—from turnkey Microsoft 365 copilots, to governed extensibility, to Copilot Studio and Microsoft Foundry platforms, to shared Azure AI services, to specialized domain copilots—that helps you decide whether to infuse AI into an existing experience or build agents and orchestration when the scenario demands more control.

How to use this page: Start at Layer 1 and move up only when your requirements demand more control (data boundaries, governance, orchestration depth, channel reach, or hosting). Most successful programs combine layers over time; this model helps you do that intentionally.

Orientation: Three Capability Buckets

Before the five-layer model, align on the three core capability buckets that describe how AI shows up. This keeps early conversations grounded in outcomes (who uses it and how) before you debate platforms.

Bucket What It Is Key Distinction
Copilot for Everyone AI as personal assistant Helps you do your work and life tasks
AI as Product/Capability AI is the value delivered to end users Standalone agents, embedded features, LLM-powered integrations—users consume AI outcomes
Agentic Coding Autonomous technical builder AI builds software or systems; output may or may not contain AI features

Insight:

  • Copilot for Everyone: AI boosts individual productivity and meets people where they work by clearing routine friction.
  • AI as Product/Capability: AI is the product value users consume; this bucket is about shipping AI features and agents as core product components.
  • Agentic Coding: AI is the builder (autonomous creation); GitHub Copilot’s coding agent generates and ships code—whether it’s AI-powered features or conventional apps—and behaves like a co-developer, not a helper.
%%{init: {'theme':'dark'}}%%
flowchart LR
    Personal[Copilot for Everyone<br/>Personal assistant]
    Product[AI as Product/Capability<br/>AI is the value]
    Agentic[Agentic Coding<br/>Autonomous builder]

    M365[Microsoft 365 Copilot / Copilot Chat]
    StudioFoundry[Copilot Studio / Microsoft Foundry]
    Embedded["Traditional app with AI features (API, UI, data layer)"]
    GHCAgent[GitHub Copilot / coding agents]

    Productivity[Productivity outcomes]
    Outcomes[AI-led product outcomes]
    Software["Shipped software or agents (AI optional)"]

    Personal --> M365 --> Productivity
    Product --> StudioFoundry --> Outcomes
    Product --> Embedded --> Outcomes
    Agentic --> GHCAgent --> Software

    style Personal fill:#107C10,color:#fff
    style Product fill:#0078D4,color:#fff
    style Agentic fill:#5C2D91,color:#fff
    style M365 fill:#107C10,color:#fff
    style StudioFoundry fill:#0078D4,color:#fff
    style Embedded fill:#0078D4,color:#fff
    style GHCAgent fill:#5C2D91,color:#fff
    style Productivity fill:#107C10,color:#fff
    style Outcomes fill:#0078D4,color:#fff
    style Software fill:#5C2D91,color:#fff

Table of contents

  1. Orientation: Three Capability Buckets
  2. Layer 1: Consumption (End-User AI)
  3. Layer 2: Extensibility (Enhance Existing Copilots)
  4. Layer 3: Development Platforms (Build Custom Agents)
  5. Layer 4: Infrastructure & AI Services (Building Blocks)
  6. Layer 5: Specialized Copilots (Domain-Specific)
  7. Sources

Layer 1: Consumption (End-User AI)

Ready-to-use AI experiences for immediate productivity.

Feature Description Documentation
Microsoft 365 Copilot Chat Free (included) enterprise-secure chat (m365copilot.com, Teams, Outlook, Edge) with GPT-4o web grounding, Copilot Pages, file uploads, image creation, and optional pay-as-you-go agents under IT control. Overview · Copilot for all announcement
Microsoft 365 Copilot Paid hero add-on for work-grounded Copilot Chat (Graph data, multi-turn reasoning), in-app copilots, and ongoing drops (RSVP search, multi-turn image editing). Nov 2025 adds shared-mailbox grounding, agent registry export, unified permissions, org sharing, voice input. Overview · Nov 2025 release notes
Built-in Agents Researcher, Analyst, Visual Creator, Prompt Coach, Idea Coach, Writing Coach Docs
Agent Store Discover, acquire, and manage Copilot agents through the in-app Microsoft 365 store (Word and PowerPoint; Excel coming) Release notes
Excel Surveys Agent Build/analyze surveys inside Excel (Web/Win/Mac) Nov 2025 release notes
Custom engine agents in Office apps Run custom agents directly inside Word/PowerPoint/Excel clients (engine agents surfaced in desktop apps) Nov 2025 release notes

When to use: Reach for Layer 1 when the use case is satisfied by turnkey Microsoft 365 experiences—give users immediate productivity gains with the free Copilot Chat surface and in-app copilots, even if you plan to layer on extensibility, custom platforms, or infrastructure later.


Layer 2: Extensibility (Enhance Existing Copilots)

Extend M365 Copilot with organizational knowledge and actions.

Extension Type Description Documentation
Copilot connectors (formerly Microsoft Graph connectors) Ingest external content into Microsoft Graph so Copilot and Microsoft Search can discover, summarize, and cite it Docs
Model Context Protocol (MCP) Standardized protocol for exposing data and tools to agents; allows Dynamics 365, Logic Apps, and custom services to act as “MCP Servers” for any agent Docs
API Plugins Enable declarative agents in Microsoft 365 Copilot to interact with REST APIs that have an OpenAPI description Docs
Teams Message Extensions Extend Copilot with Teams-based actions Docs
Declarative Agents Configure agents with instructions, knowledge sources, and actions (MCP now GA with analytics/tracing; Dataverse/D365 MCP servers) Docs

When to use: Start (or graduate to) Layer 2 anytime the use case demands company data or governed actions that turnkey copilots can’t reach—connect repositories, expose APIs, and assemble declarative agents while staying inside the Microsoft 365 trust boundary.


Layer 3: Development Platforms (Build Custom Agents)

Platforms for building agents with varying levels of control and complexity.

Technology Description Key Capabilities Documentation
Copilot Studio Low-code to pro-code SaaS for custom agents Managed governance, multi-channel, BYOM/BYOK, Agent2Agent (A2A) orchestration Docs
Power Apps Plan Designer AI-assisted solution architecture Generates Dataverse tables, roles, and app structure from natural language; accelerates Layer 3 builds Docs
Microsoft Agent Framework Successor to Semantic Kernel and AutoGen that unifies agent and workflow development (Public Preview) Multi-agent workflows (sequential, concurrent, handoff, Magentic), thread-based state, MCP and tool integration Docs
AG-UI Protocol Integration (Preview) Standardized protocol to surface Agent Framework experiences in custom web and mobile clients Seven protocol capabilities (streaming, backend tool rendering, human-in-loop approvals, generative UI, shared/predictive state) with ASP.NET Core and FastAPI adapters; CopilotKit interoperability Docs
M365 Agents SDK Full-stack SDK for publishing custom engine agents across Microsoft 365 Copilot, Teams, web, and custom apps Channel adapters, conversation state, orchestrator-agnostic (Agent Framework, Semantic Kernel, LangChain) Docs
Microsoft Foundry (Azure) Unified development environment for model catalog, prompt flow, evaluations, and agent runtime (formerly Azure AI Foundry) Integrates with Foundry Agent Service; Model Router GA (routing profiles/custom subsets, billing Nov 2025) Docs
Foundry Agent Service Managed runtime for building, hosting, and scaling agent experiences Built-in memory, tool calling, secure connectors, catalog samples; Foundry Control Plane links to policy/Defender/Purview Docs
LangChain Ecosystem (Third-party) OSS framework for LLM applications (Python/JS) LangChain: Azure integrations, prompt flow; LangGraph: agent workflows, state management; LangSmith: tracing & observability LangChain Docs | LangGraph Docs | LangSmith Docs

When to use: Choose Layer 3 when your scenario requires bespoke logic, orchestration, or channel reach that low-code extensibility can’t deliver—this is where pro-code teams build custom agents (and you can enter here directly if the use case demands it).


Layer 4: Infrastructure & AI Services (Building Blocks)

Foundational services that power agents across all platforms.

Service Description Key Capabilities Documentation
Azure OpenAI Service Enterprise GPT models with VNet, RBAC, tokens per minute (TPM) quotas Managed LLM infrastructure Docs
Azure AI Search Agentic retrieval/knowledge bases with reasoning effort + partial responses, Foundry IQ integration, SharePoint ACL + sensitivity label enforcement Semantic ranker + agentic retrieval on free tier; knowledge sources (SharePoint/OneLake/web) with content extraction Docs
Azure API Management (AI Gateway) Centralized governance layer Token rate limiting, model routing, chargeback, content safety, observability Docs
Azure AI Content Safety Content filtering, groundedness detection Moderation and safety controls Docs
Azure AI Content Understanding (Preview) Multimodal content processing with generative AI Document, image, audio, video analysis; zero-shot extraction; grounding & confidence scoring; RAG-ready Docs
Prompt Flow GenAIOps for evaluations and orchestration Model testing and deployment Docs
AI Builder Comprehensive prebuilt & custom AI models for Power Platform Document processing (invoices, receipts, contracts), GPT text generation, sentiment analysis, entity extraction, vision (object detection, OCR), predictions Docs
Copilot Studio Agent Flows Native automation workflows within Copilot Studio Deterministic automation for agents; natural language or visual designer; billed via Copilot Studio capacity Docs
Azure Document Intelligence Prebuilt and custom document models OCR and document understanding Docs
Azure Logic Apps Enterprise workflow automation with 1,400+ connectors Expose Standard logic apps as remote MCP servers for agent tools, integrate with enterprise systems, monitor via Application Insights Docs
Azure Cosmos DB Globally distributed NoSQL database with AI capabilities Vector search (IVF, HNSW, DiskANN), AI agent memory system, integrated vector database Docs
Azure Database for PostgreSQL Fully managed PostgreSQL with AI extensions azure_ai extension (OpenAI + Cognitive Services), pgvector for vector search, in-database embeddings Docs
SQL Server 2025 (Preview) Enterprise database with native AI capabilities VECTOR data type (float32/float16), vector functions & indexes (DiskANN), external AI model management, Copilot in SSMS Docs
Microsoft Fabric Unified analytics platform with AI capabilities Platform: Lakehouse (Delta tables), Warehouse (T-SQL), OneLake (unified storage), SQL analytics endpoint, Microsoft Foundry integration. AI Layer: Copilot in Fabric (data science, factory, warehouse, Power BI, Real-Time Intelligence), Fabric Data Agents (Preview) Docs
Agent 365 (Preview) Entra-backed agent identity, registry, conditional access, prompt shield/risky-agent detection Agent registry and lifecycle governance for agents across experiences Docs
Foundry Control Plane Agent registry and policy/security hub Integrates Defender, Purview, Azure Policy for agent posture and RBAC Docs
Windows AI Foundry / Edge AI Local inference runtime for Windows Foundry Local: Run OSS models (Phi-4-mini) on NPU/GPU/CPU; Edge AI APIs: Zero-latency inference in browser; MCP on Windows: Local agent tools Docs

When to use: Prioritize Layer 4 when the use case hinges on shared AI infrastructure (vector storage, automation, governance, evaluations) or strict compliance/scale requirements—even if higher layers are still in-flight, these building blocks keep every copilot sustainable.


Layer 5: Specialized Copilots (Domain-Specific)

Purpose-built AI assistants for specific workflows and industries.

Copilot Description Primary Use Cases Documentation
GitHub Copilot Code generation and developer productivity AI-assisted coding Docs
Security Copilot Security operations and threat analysis SOC automation Docs
Security Copilot (M365 E5) Included with Microsoft 365 E5; 12 built agents for SOC SOC workflows with agent catalog, no extra license for E5 Announcement
Dynamics 365 Copilots Sales, Service, Marketing, Finance agents CRM and ERP workflows Docs
Microsoft Fabric Data Agents (Preview) Conversational AI agents for analytics data Transform enterprise data into Q&A systems; integrate with Copilot Studio, Foundry Agent Service, Power BI Copilot Docs
Azure SRE Agent (Preview) AI-powered site reliability engineering assistant Incident automation, explainable RCA, proactive monitoring, natural language Azure resource insights Docs
GitHub Copilot Coding Agent Agentic multi-file editing and autonomous issue resolution Assigned GitHub issues create PRs; workspace-wide edits; Azure MCP Server integration Docs

When to use: Enter at Layer 5 when a Microsoft or partner copilot already addresses the domain outcome (developer, security, CRM, analytics); deploy it for fast impact, then supplement with lower layers only where gaps remain.


Next: Decision Framework - Apply BXT and critical questions to shortlist technologies


Sources

Layer 1 & 2:

Layer 3:

Layer 4:

Layer 5:

Model Overview:


Back to top

Copyright © 2025. This documentation is based on official Microsoft sources and best practices.