Chapter 2 · Models
Claude in Microsoft Foundry
You subscribe to Claude models through Azure Marketplace and deploy them in your Foundry resource, hosted on Azure or on Anthropic's infrastructure. All versions run as Global Standard, and some Azure-hosted ones also in the US data zone. Billing goes through your Azure invoice, with sign-in through Entra ID or an API key.
Security: For Claude in Foundry Anthropic is the data processor, and Mythos models accept Entra ID only. CSP subscriptions and credit-only subscriptions are not supported, and we clarify this before deployment.
Where it runs: Claude in Microsoft Foundry through Azure Marketplace, with the Messages API at the Foundry resource endpoint.
- Microsoft Foundry
- Azure Marketplace
- Global Standard
- Entra ID
Chapter 3 · AgentsIn both guides
Coding agent
In the editor or terminal it runs alongside a developer; in the cloud it starts from the ticket and works alone. Several agents handle different tickets in parallel, each on its own branch. The result is always a pull request, never a direct push to the main branch.
Security: Copilot cloud agent can neither approve nor merge its own pull requests. For the other agents the same branch rules enforce this.
Where it runs: Codex, Claude Code and GitHub's Copilot cloud agent, in the editor, in the terminal or in the vendor's cloud environment.
Exampleterminal
$ git branch -r
origin/main
origin/copilot/export-cost-centre
origin/codex/fix-vat-rounding
origin/claude/docs-api-v2
$ gh pr list --draft
#231 Export: cost centre and VAT code copilot
- OpenAI Codex
- Claude Code
- GitHub Copilot
- VS Code
Chapter 8 · Identity, security and guardrailsIn both guides
Conditional Access
At every sign-in Entra ID checks who is signing in, from which device, from which network and with which risk, and then demands a passkey, a compliant device, or blocks. Because agents have an identity of their own, the same rules apply to them: an agent that wants to reach the ERP at night from a foreign network does not get through. A rule starts in report-only mode, then goes live group by group.
Security: Break-glass accounts are excluded from every blocking rule, and every change to a rule is in the Entra ID audit log.
Where it runs: Conditional Access in Microsoft Entra ID P1, for agents with Entra Agent ID and a Microsoft Agent 365 licence; at OpenAI, ChatGPT signs in through SAML with Entra ID, so the same rules protect the sign-in.
- Conditional Access
- Entra ID
- Entra Agent ID
- SAML SSO
Chapter 2 · ModelsIn both guides
Context window
Everything the model sees for one answer has to fit into the context window: instructions, conversation history, retrieved documents, tool descriptions and the answer itself, counted in tokens. A long contract fits into current models in one piece; a long session still fills the window, which is why agents condense the history into summaries. More context costs tokens and time.
Security: The model sees everything in the context in full, including personal data in an attached document. So only the sources the question needs and the person may open end up in the window.
Where it runs: The context window per model in the Foundry catalogue data sheet and as a per-model setting in Ollama; at OpenAI per model in the API documentation, with context compaction in Agents API sessions.
- Token
- Responses API
- Microsoft Foundry
- Ollama
Chapter 3 · Agents
Copilot Autopilot
While the person sits in a meeting, Autopilot keeps working in Teams and Outlook: always on, with its own identity, memory, computer and workspace. You give it a name, a role and a goal; it prepares and puts results up for review. Microsoft introduced it with the new Copilot; it was called Scout before.
Security: Autopilot has an identity of its own in your tenant, so Entra policies apply to it and IT decides what it may do; the person sets goals and boundaries.
Where it runs: Copilot Autopilot in the new Microsoft Copilot, announced as a private preview; the counterpart at OpenAI is dots in ChatGPT.
- Copilot Autopilot
- Microsoft Copilot
- Entra Agent ID
- Personal agents
Chapter 1 · Overview
Copilot Chat
Staff open Copilot Chat at copilot.cloud.microsoft, in the Microsoft Copilot app, in Edge, Outlook and Teams. Without a Copilot licence it works with the web and with files the person uploads or has open; with a licence it brings in emails, chats, meetings and files by itself. In the pilot we show both on the same tasks so the difference becomes visible.
Security: Anyone signed in with their Entra account has prompts and answers protected by Enterprise Data Protection. We control personal Microsoft accounts on company devices with Tenant Restrictions v2.
Where it runs: Microsoft Copilot Chat on the web, in the Microsoft Copilot app, in Edge, Outlook and Teams, included with eligible Microsoft 365 subscriptions.
Examplecopilot-chat.yaml
entry: copilot.cloud.microsoft, Copilot app,
Edge, Outlook, Teams
basic: web, uploaded and open files
premium: web, emails, chats, meetings, files
through Microsoft Graph and Work IQ
sign_in: Entra account, Enterprise Data Protection
network: allow *.cloud.microsoft- Copilot Chat
- Microsoft Copilot app
- Enterprise Data Protection
- Tenant Restrictions v2
Chapter 4 · Knowledge and data
Copilot connectors
A connector reads tickets, knowledge articles or project data from a system outside Microsoft 365 into the index, together with the access rights from the source. Copilot, Copilot Search and agents then find this content next to emails and files. For common systems we set up prebuilt connectors; for your own systems we build them through Microsoft Graph.
Security: Every item carries the permissions from the source system, or we limit it explicitly to groups. Personal data that answers do not need is never read in.
Where it runs: Copilot connectors in the Microsoft 365 admin center, prebuilt or custom-built through Microsoft Graph, usable in Copilot, Copilot Search and agents.
Exampleconnectors/service-tickets.yaml
connector: Service ticketing system
type: Copilot connector, custom build
items: tickets, solutions, customers
acl: from the source, per item
schema: title, status, customer (searchable)
exclude: phone numbers, home addresses
refresh: incremental every 15 minutes
- Copilot connectors
- Microsoft Graph
- Copilot Search
Chapter 8 · Identity, security and guardrails
Copilot controls
The Copilot controls in the Microsoft 365 admin center bring together security and governance, management of licences and agents, and measurement and reporting. The AI Administrator role manages Copilot without anyone needing global admin rights. Usage reports show active people and prompts per app, and Copilot Analytics links usage to your own metrics.
Security: Every change to the Copilot settings is recorded in the audit log. We conceal names in the reports, and the analysis works with groups and roles.
Where it runs: Copilot controls in the Microsoft 365 admin center, the Power Platform admin center and Copilot Studio, usage reports and Copilot Analytics.
ExampleMicrosoft 365 admin center, Copilot
Microsoft 365 admin center > Copilot
pin_copilot_chat: everyone, pilot group first
web_search: allowed
agents: approved agents only
pay_as_you_go: billed via Azure subscription
reports: names concealed
role: AI Administrator, no Global Admin
- Microsoft 365 admin center
- AI Administrator
- Copilot Analytics
- Copilot Credits
Chapter 7 · Licences and cost
Copilot Credits
Agents are billed in Copilot Credits: every answer, tool call and trigger activation consumes credits, through prepaid packs or pay-as-you-go. For people with a Microsoft Copilot licence, internal use is included within fair-use limits, computer use excepted. In the Power Platform admin center you set a monthly cap per agent.
Security: The cap per agent and a look at the consumption reports before every expansion keep the bill within the agreed frame; the figures per case come from the pilot.
Where it runs: Copilot Credits for Copilot Studio, Copilot Cowork, advanced work in SharePoint and Dataverse MCP server calls outside Copilot Studio, managed in the Power Platform admin center and the Microsoft 365 admin center.
- Copilot Credits
- Copilot Studio
- Power Platform Admin Center
- Copilot Cowork
Chapter 1 · Overview
Copilot in the apps
Copilot drafts in Word from minutes, calculates in Excel with formulas and pivot tables, builds slides in PowerPoint from a report and summarises threads and meetings in Outlook and Teams. With the Premium licence the person has priority access there; without it, standard access that depends on capacity. Which of these tasks hold up in daily work, we measure in the pilot.
Security: New content built from labelled sources inherits the highest sensitivity label where supported. Sending and filing remain up to the person.
Where it runs: Copilot in the Microsoft 365 apps on Windows, Mac, the web and mobile; priority access with Microsoft Copilot (Premium).
Examplepilot/tasks.txt
App Pilot task
Word Q3 minutes -> quarterly report
Excel deviations from budget, with formula
PowerPoint report -> eight slides for the board
Outlook customer thread, open questions
Teams decisions and tasks from the meeting
- Word
- Excel
- PowerPoint
- Outlook
- Teams
Chapter 7 · Licences and cost
Copilot licences
Copilot Chat (Basic) comes with eligible Microsoft 365 subscriptions and works with web data and uploaded files. Microsoft Copilot (Basic) adds standard access in Word, Excel, PowerPoint and OneNote, and only the Microsoft Copilot (Premium) add-on fetches work data through Microsoft Graph. For the Business plans Microsoft offers the Copilot Business variant.
Security: We assign licences through groups, so it can be traced who has worked with which tier since when.
Where it runs: Add-on to Microsoft 365, Office 365 and other plans, Copilot Business for the Business plans, already included in Microsoft 365 E7.
Examplelicensing.txt
Tier Work data Apps
Copilot Chat (Basic) upload -
Microsoft Copilot (Basic) upload standard access
Microsoft Copilot (Premium) automatic priority
Work-data agents Basic: by consumption
As of Microsoft Learn, 2026-09-25
- Copilot Chat
- Microsoft Copilot
- Copilot Business
- Microsoft 365 E7
Chapter 1 · Overview
Copilot Studio
A business team builds an agent in Copilot Studio from instructions, knowledge sources such as SharePoint and Dataverse, tools through connectors and MCP, agent flows for fixed procedures and triggers that start it unasked. It is published to Teams, Microsoft Copilot and further channels and maintained in one place. Environment, data policies and the solutions for transport belong to the Power Platform.
Security: Every new agent receives an Entra Agent ID, it queries knowledge sources with the sign-in of the person asking, and data policies in the Power Platform admin center limit connectors, channels and triggers.
Where it runs: Copilot Studio in the Power Platform, billed through Copilot Credits or included for people with a Microsoft Copilot licence; the counterpart at OpenAI is workspace agents in ChatGPT.
- Copilot Studio
- Power Platform
- Agent Flows
- Entra Agent ID