Guide

    Understanding Microsoft AI/SI, from Copilot to Foundry.

    The guide shows what Copilot, Copilot Studio and Foundry take on, where your data runs and what your IT decides, with date and source.

    As of: October 2026 · Editor: Marcel Haas

    Stack map

    The map of the platform.

    For every block: what it does, who uses it, how it is bought, where it runs and which chapter goes deeper.

    • Microsoft 365
    • Azure
    • Across both

    For everyone

    Microsoft 365

    Microsoft Copilot

    Summarises, drafts and calculates in Word, Excel, PowerPoint, Outlook and Teams, with the rights of the person asking.

    Who uses it
    Every employee
    How it is bought
    Chat on the web included in most Microsoft 365 plans, work data with the Copilot licence per person
    Where it runs
    Microsoft 365 within the EU Data Boundary; Claude models excluded
    Microsoft 365

    Agent Store and Cowork

    Prebuilt agents such as Researcher and Analyst, your own agents from Copilot Studio and Foundry next to them; Cowork takes a described task across several programs to the end.

    Who uses it
    Every employee with a Copilot licence
    How it is bought
    In the Copilot licence; Cowork usage-based through Copilot Credits
    Where it runs
    Microsoft 365
    Across both

    Copilot Autopilot

    A persistent personal agent with its own identity, memory, computer and workspace, announced as a private preview.

    Who uses it
    Individuals with governed access
    How it is bought
    Part of the new Copilot, preview
    Where it runs
    At Microsoft, with the person's access

    Building agents

    Microsoft 365

    Copilot Studio

    Agents with sources in SharePoint and Dataverse, actions through connectors and MCP, triggers without being asked; your team maintains them itself.

    Who uses it
    Business teams with your IT
    How it is bought
    Copilot Credits, included for licensed employees within fair-use limits
    Where it runs
    Power Platform in your tenant, one Entra Agent ID per agent
    Azure

    Foundry Agent Service

    Prompt agents without code, voice agents and hosted agents with your code in a container; published to Teams, Copilot and the Entra Agent Registry.

    Who uses it
    Development teams
    How it is bought
    Consumption per token, tool call and hosting
    Where it runs
    Your Azure region; hosted agents in Switzerland North and West
    Across both

    MCP and A2A

    The Model Context Protocol connects tools with agents in Copilot Studio and Foundry, A2A lets agents talk to each other; both open protocols.

    Who uses it
    Development teams
    How it is bought
    Open protocols, no licence
    Where it runs
    On your servers or at the tool's vendor

    Applications of your own

    Azure

    Microsoft Foundry

    One resource with network, encryption and model deployments, projects per team, Foundry Tools for speech, vision and documents, evaluation and control plane.

    Who uses it
    Development teams and your IT
    How it is bought
    Consumption per token, tool call and hosting in your Azure subscription
    Where it runs
    Your Azure region; regional, in the data zone or global depending on model and deployment type
    Azure

    Model catalogue

    GPT as Azure OpenAI, Claude and Grok as partner models, Mistral, Llama, Phi and DeepSeek; the model router chooses within the set you approve.

    Who uses it
    Whoever chooses a model per task
    How it is bought
    Per token, as reserved capacity or in batch
    Where it runs
    Regional, data zone or global, per deployment
    Azure

    Fabric IQ and Work IQ

    Work IQ fetches the work context for Copilot with the person's rights, Fabric IQ and OneLake provide business data for data agents.

    Who uses it
    Business teams through Copilot, data teams through Fabric
    How it is bought
    Work IQ in the Copilot licence, the Work IQ API by consumption, Fabric through capacities
    Where it runs
    Microsoft 365 and your Fabric capacity

    Control

    Across both

    Entra ID and Entra Agent ID

    One identity for every person and every agent, Conditional Access, sign-in logs, Agent Registry.

    Who uses it
    Your IT
    How it is bought
    In Entra ID; agent features with Microsoft Agent 365
    Where it runs
    Your tenant
    Across both

    Purview, Defender, guardrails

    Labels, loss prevention, audit and retention for Copilot and Foundry; guardrails and attack detection per subscription.

    Who uses it
    Your IT and your data protection officer
    How it is bought
    In the Microsoft 365 and Azure plans, some features with E5 or an add-on
    Where it runs
    Your tenant and your Azure subscription
    Across both

    Directive and test set

    What is allowed, which tools are approved, and the test set every version is measured against.

    Who uses it
    Management, business team, data protection
    How it is bought
    Your own work
    Where it runs
    With you

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation we map your needs to the layers of the guide.