Microsoft Scout is not another Copilot feature. It is Microsoft's first work agent that runs around the clock — not reactively on command, but proactively in your context. At Build 2026, Microsoft opened a new category with this announcement: the continuously running, autonomously acting work agent inside the Microsoft 365 ecosystem.
Those who have worked with Copilot know the pattern: prompt in, response out. Scout breaks this pattern. It continuously observes your work, recognises patterns, handles routine tasks independently and only checks in when it needs a decision or has noticed something relevant to you.
Source: Microsoft — official "Introducing Microsoft Scout" video. More information on Microsoft Learn.
What Scout actually does
Scout is a software entity with its own Microsoft Entra identity — that is the decisive architectural difference from previous Copilot capabilities. It has its own service account in your tenant, managed and monitored through Microsoft Entra ID. Admins can see what Scout has done, which data it accessed and what actions it performed — just like a human employee.
Concretely, Scout acts in four environments:
Teams: Scout tracks conversations, recognises tasks and commitments made in chat, and automatically creates follow-up items. If someone in a meeting says "I'll send you the numbers by Thursday", Scout creates a task and reminds the relevant person — without anyone needing to do anything manually.
Outlook: Scout classifies incoming emails by priority, summarises long email threads and suggests replies. Based on your previous emails and calendar, it can identify which requests are urgent and which can wait.
OneDrive and SharePoint: This is Scout's file backbone. It indexes your documents, understands the context (what am I working on now, what is relevant to the current project) and surfaces information before you ask for it. It can prepare documents, summarise status reports and create drafts based on existing templates.
The Entra identity: governance, not a security risk
The biggest objection to always-on agents is: security. What has this agent seen? Can it access things it shouldn't? Who is responsible if something goes wrong?
Microsoft took this objection seriously and equipped Scout with a complete Entra identity from the start. This means:
- Permissions are explicit and limited: Scout can only access what the admin explicitly allows. No broader access than necessary.
- Complete audit logs: Every action by Scout is logged in Microsoft Purview — when, what, which data. This meets compliance requirements under the Swiss DPA and ISO 27001.
- Conditional Access applies to Scout too: If your tenant has Conditional Access policies (e.g. no actions outside the EU), these apply to Scout as well.
- Admin control centre: The Microsoft 365 Admin Center has a dedicated Scout management console. Admins can restrict the scope of action, disable specific features and retrieve reports.
For Swiss companies with elevated data protection requirements, this is a critical prerequisite. Scout does not process data outside your tenant — your Microsoft 365 data residency settings also apply to Scout.
Copilot Autopilots: structured automation with agent logic
Alongside Scout, Microsoft introduced the concept of Copilot Autopilots at Build 2026. Where Scout is a continuously running personal agent, Autopilots are configurable workflows with agent logic — similar to Power Automate, but with genuine AI decision logic.
An Autopilot could, for example:
- Automatically classify incoming customer emails, retrieve relevant information from SharePoint and generate an initial reply — only escalating when it cannot find a suitable answer.
- Compile weekly status reports from Teams data, OneDrive documents and Outlook calendars and send them to management.
- Guide new employees through the onboarding process: present documents, answer questions, create tasks.
The difference from classic Power Automate flows: Autopilots make real decisions based on context. They are not rigidly rule-based but can assess situations and respond adaptively.
OpenClaw: the technological foundation
For the technically curious: Scout and Autopilots are built on Microsoft's OpenClaw technology, an internally developed framework for agent-based task execution. OpenClaw is being made available to the community as an open-source project, meaning developers can use the same infrastructure to build their own agents — and connect them seamlessly with Microsoft services.
This is strategically significant: Microsoft opens the agent infrastructure while retaining the ecosystem (Entra, Teams, SharePoint, Outlook) as the integration layer. Those who build their own agents build them automatically within the Microsoft ecosystem.
What this means for Swiss companies
Availability and licensing
Scout is rolling out as part of Microsoft 365 Copilot — no separate purchase, no additional add-on. Anyone who has already licensed M365 Copilot gets Scout with it. The rollout begins in the second half of 2026, with priority for enterprise tenants.
Data protection and Swiss DPA compliance
Scout processes data exclusively within your Microsoft 365 tenant. Data neither leaves the tenant nor is it used to train Microsoft models. For Swiss companies that must comply with the revised Federal Act on Data Protection (FADP), this is a clear prerequisite — one that Scout meets.
Practical implications for IT departments
Introducing Scout requires active IT involvement:
- Admin configuration: Scout's scope of action must be defined — what may it do, what may it not?
- Governance framework: Which processes should be partially automated through Scout?
- Change management: Employees must understand what Scout does and develop trust in the automation.
- Monitoring: Audit logs must be reviewed regularly, especially during the introduction phase.
The good news: companies that have already introduced Microsoft Purview and Entra governance can activate Scout relatively quickly. The infrastructure is already in place.
Our assessment
Microsoft Scout is the first credible attempt to anchor a continuously running work agent in an enterprise context — with the governance that enterprise IT requires and the integration points that create real value.
The concept of Copilot Autopilots shows that Microsoft wants to close the gap between "intelligent search" (existing Copilot) and "autonomous task execution" (Power Automate). Whether this works as smoothly in practice as it did on the Build keynote slide will become clear in the second half of 2026.
For Swiss companies, the recommendation is: lay the governance foundations now — set up Entra identity management cleanly, activate Purview logging, update your data protection concept. Then you will be ready when Scout rolls out.
CNEXT accompanies Swiss companies in building the technical and organisational prerequisites for using Scout and Copilot Autopilots — from Entra configuration to the change management concept.
Related article: How Scout technically works — Topics, Feeds, Scout Cards and privacy boundaries — is covered in Microsoft Scout Explained: How the Proactive AI Assistant Works.

