Guide Microsoft AI/SI · Chapter 1

    Microsoft AI/SI at a glance, from Copilot to Foundry.

    Copilot works in Word, Outlook and Teams, Copilot Studio adds agents, Foundry carries your own applications in Azure, and Entra and Purview govern all three layers.

    As of: October 2026 · Editor: Marcel Haas

    • Microsoft Copilot
    • Copilot Studio
    • Microsoft Foundry
    • Entra Agent ID
    • Microsoft Purview
    • Azure OpenAI

    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
    01

    The work starts in the programs that are open anyway.

    A head of sales prepares the quarterly meeting in Teams and has Copilot gather the open points from emails, chats and the last minutes; the answer draws only on content he may open himself. That is the first layer: Microsoft Copilot in Word, Excel, PowerPoint, Outlook and Teams, with Microsoft Graph as the way to the work data and a router that picks the model per request. Chat with web data belongs to most Microsoft 365 subscriptions, answers from your own work data need the Copilot licence. On the same layer sit the prebuilt agents such as Researcher and Analyst, the Agent Store and Cowork, which takes a described task across several programs to the end.

    02

    Copilot Studio builds the agent that stays in Microsoft 365.

    In sales, an agent in Teams reports that a quote has gone unanswered for days, pulls the history from Dynamics 365 and proposes the next message; a person sends it. Agents like this are built in Copilot Studio, with sources in SharePoint and Dataverse, actions through connectors, agent flows or an MCP server, and triggers that start without being asked. Every new agent gets its own identity in Entra, so permissions, conditions and data rules apply per agent. It is published in Teams, in Copilot or on a website, usage is billed in Copilot Credits, and after handover the business team maintains the agent in the interface itself.

    03

    Foundry carries what an application of your own needs.

    An application that reads meter readings from submitted photos and writes them into the billing system needs no chat window, but a model that understands images, a workflow in your own code and an interface to the line-of-business system. That is what Microsoft Foundry is for: a resource in your Azure subscription where network, encryption and model deployments are set once, with a project per team beneath it. The Agent Service runs prompt agents without code of your own, voice agents and hosted agents with your code in a container; evaluations check every version against the test set, and the control plane shows agents, models and cost across all projects.

    04

    The models come from a catalogue, and the route sets the place.

    Under Copilot a router picks the model per request, and models from Anthropic sit next to it as a subprocessor, in the EU, the EFTA and the UK only after approval. In Foundry you deploy GPT models as Azure OpenAI, Claude, Grok and open models from Mistral, Meta and Microsoft itself, and the deployment type sets whether a model computes in Switzerland North, in the EU data zone or globally. The Model Context Protocol connects tools with agents in Copilot Studio and Foundry, A2A lets agents talk to each other; both are open protocols that Microsoft backs.

    05

    The control layer belongs to your IT.

    Above every layer sits what your IT runs anyway: Entra ID with an identity for every person and, since April 2026 with Entra Agent ID, for every agent; Purview with labels, loss prevention and the log of every prompt and answer; Defender and the guardrails in Foundry against manipulated inputs. This layer stays in place when a model or a layer beneath it changes, and it is the reason why choosing a layer is no decision for years. Over time one agent will carry most of the work; which one is open today, and identities, data boundaries and logs apply to it just the same.

    What you decide.

    How many layers do you need at the start?

    Options

    1. 1Copilot only, with clean permissions
    2. 2Copilot and a first agent in Copilot Studio
    3. 3All of it, from Copilot to an application of your own on Foundry

    Our recommendation: As many as the first case demands, and the control layer complete from day one. An organisation whose work lives in emails, documents and meetings starts with Copilot and tidies up sharing, guests and labels first. An organisation with a recurring workflow in Teams adds the first agent. An application of your own comes when a case needs a specific model, a workflow without a chat or an interface outside Microsoft 365.

    What we advise against: Setting up every layer before a case exists. Licences, credits and an Azure subscription without a task produce cost and questions, but no test set that anything could be measured against.

    Which controls are in place before the first case starts?

    Options

    1. 1Entra ID with Agent ID and the Copilot controls in the admin centre
    2. 2Plus Purview with labels, the data security posture view and the policy for the Copilot location
    3. 3Plus the guardrails, networks and budgets in Foundry

    Our recommendation: Identities and the Copilot controls on day one; Purview with labels and the policy for the Copilot location before the first agent reads company data; the guardrails, networks and budgets in Foundry with the first application of your own. Every stage comes with the case that needs it, and none afterwards.

    What we advise against: Opening an agent to everyone before it has its own identity and the directive says what it may read.

    Who keeps the overview current?

    Options

    1. 1Your IT as the platform owner
    2. 2One person per system in the business
    3. 3A partner who maintains both

    Our recommendation: Your IT owns the control layer and the list of approved layers; every system on it has a named person in the business who maintains sources, instructions and the test set; and every entry carries a review date. We maintain the overview with you for as long as you want, and hand it over so your team carries it on.

    What we advise against: An overview without a date. What Microsoft changes in one quarter turns an undated plan into a guess.

    Status and sources.

    As of: October 2026

    • Licensing as of 25 September 2026

      Web chat is included, chat with work data needs the licence.

      Copilot Chat with internet results comes at no extra cost with eligible Microsoft 365 subscriptions. Answers from your work data need a Copilot licence. For smaller organisations, Microsoft offers a «Copilot Business» variant for the Business plans.

      Source: Microsoft Learn: License options for Microsoft Copilot
    • Since July 2026

      Every new Copilot Studio agent gets an Entra Agent ID.

      Copilot Studio automatically creates a Microsoft Entra Agent ID for every new agent; opting out at environment level is no longer possible. Connector permissions, Conditional Access and DLP policies therefore apply per agent.

      Source: Microsoft Learn: What's new in Copilot Studio
    • As of 25 September 2026

      Prompt, voice and hosted agents in Foundry, published to Teams and Copilot.

      Foundry Agent Service offers prompt agents without code, voice-based prompt agents for phone and browser (preview) and hosted agents with your own code. Published agents appear in Microsoft Teams, Microsoft Copilot and the Entra Agent Registry. The A2A protocol 1.0 for agent-to-agent communication is generally available.

      Source: Microsoft Learn: What is Microsoft Foundry Agent Service?
    • Since April 2026

      Entra Agent ID, one identity for every agent.

      Microsoft Entra Agent ID is generally available: an identity and authorisation framework for AI agents based on OAuth 2.0, MCP and A2A, for agents from Microsoft Foundry, Copilot Studio and third-party platforms. Access, conditions and logs therefore apply per agent as they do for people.

      Source: Microsoft Learn: What is Microsoft Entra Agent ID

    Frequently asked questions.

    Is Copilot Studio part of Microsoft Copilot?

    With Copilot Studio you build the agents that employees then find in Microsoft Copilot next to the prebuilt ones. Such an agent appears in Teams, in the Agent Store or on a website and is billed in Copilot Credits; Copilot itself is licensed per person. The two belong together but are bought and governed separately: Copilot in the Copilot controls of the admin centre, agents additionally in the Power Platform admin centre.

    Do we need an Azure subscription to use Foundry?

    Yes. Foundry runs as a resource in your Azure subscription, and network, encryption, model deployments and consumption billing hang off it. An existing Azure OpenAI resource can be extended to a Foundry resource; endpoint and keys stay the same. Without Azure, you start with Copilot and Copilot Studio in Microsoft 365.

    Do we need an additional licence for agents?

    Agents are billed in Copilot Credits, through prepaid packs or pay-as-you-go; for people with a Copilot licence, internal use is included within fair-use limits, computer use excepted. In the Power Platform admin centre you set a monthly cap per agent. For Foundry, consumption in the Azure subscription applies: models per token, tools per call, hosted agents by processor and memory of the active sessions.

    Which models work under Copilot?

    In Auto mode Copilot decides whether a fast model is enough or one for deeper reasoning is needed, and the person can choose themselves. Models from Anthropic are available in licensed experiences as a subprocessor; in the EU, the EFTA and the UK they are enabled for no users by default and excluded from the EU Data Boundary. Whether Copilot includes the web is governed by your IT through a policy in the admin centre.

    Why do Copilot Studio and Foundry speak MCP?

    Because the Model Context Protocol describes how an agent calls a tool, independent of the vendor. An MCP server provides functions and data, and an agent in Copilot Studio or Foundry uses them; the same servers are reached by agents on other platforms too. Since December 2025 the protocol sits with the Agentic AI Foundation of the Linux Foundation, backed by Microsoft, OpenAI and Anthropic. A tool you build once as an MCP server is therefore open to every layer.

    Where do employees find the agents we build?

    In the Agent Store, in Teams and in Copilot; agents from Foundry appear there too and additionally in the Entra Agent Registry. Who sees which agent is governed by your IT through approvals in the Copilot controls of the admin centre and in the Power Platform admin centre.

    Next chapter · Chapter 2

    Which AI model does which work at Microsoft.

    Which model does which work at Microsoft, and how do we choose?