Microsoft Scout: The Always-On Agent for Microsoft 365

Microsoft Scout, announced at Microsoft Build on June 2, 2026, is a new kind of agent: always on, with its own persistent identity, acting on your behalf without a prompt every time. Microsoft calls this category Autopilots, and Scout is the first. Instead of waiting to be asked, it works in the background across email, calendar, chats, files and meetings, keeping work moving within boundaries you set. This guide explains what Scout is, how it differs from Microsoft 365 Copilot, and what admins should prepare.

What is Microsoft Scout?

Scout is built on OpenClaw, the open-source personal agent framework, combined with Microsoft’s enterprise identity and compliance stack. Each user names their own Scout, gives it feedback, and builds up skills and memories that persist, so it learns how that person works over time. It runs in the cloud and also operates across the desktop and web browser.

Omar Shahine, who leads the Scout team, described the idea at Build: people codify their working patterns into memories and skills, and the agent becomes more capable as it understands them better.

Microsoft Scout vs. Microsoft 365 Copilot

Scout and Copilot are designed to work side by side.

Copilot answers explicit requests; Scout handles ongoing coordination. For how Copilot itself changed at Build, see Copilot Agent Mode is now the default.

What Scout can do

According to Microsoft’s announcement, Scout works across four areas, showing its work as it goes and pausing for approval before sensitive actions:

• Files and documents: create, edit and search Word, Excel, PowerPoint and code files in a defined workspace.
• Shell and scripts: run commands under a tiered permission model, with some auto-approved by rule and others always requiring sign-off.
• Browser automation: navigate sites, fill forms and extract information within the boundaries your organization sets.
• Microsoft 365: connect to Teams, Outlook, OneDrive and SharePoint to schedule meetings, flag unanswered email, surface deadlines and prepare meeting materials.

Scout also has background modes. A recurring “heartbeat” runs a prompt you define on a schedule while you’re away, and automations run tasks on a schedule or when a condition is met, such as a new email from a particular sender. For complex work it can hand pieces to sub-agents and combine the results.

Skills and extensibility

Scout ships with prepackaged skills, including calendar management, meeting agenda drafting and Office document editing. Users and organizations can add custom skills by placing SKILL.md files in a skills directory, and extend Scout through Model Context Protocol (MCP) servers to reach other data sources and tools.

Microsoft Scout security model

An always-on agent that can send email and run scripts raises obvious questions. Microsoft describes several layers of control:

• Its own Entra identity: each Scout instance acts under a governed Microsoft Entra identity, so its actions are attributable and auditable.
• Granular permissions: capability categories (files, shell, browser, Microsoft 365) can be turned on or off, and sensitive directories can require confirmation.
• Policy conformance: a built-in system continuously checks that Scout stays within configured guidelines, and each check produces its own audit trail. Microsoft contributed this system back to the OpenClaw project.
• Purview integration: Microsoft says sensitivity labels and DLP policies are enforced before Scout sends or writes anything.
• Approval gates: sensitive actions need explicit human approval.

How to get access

At launch, Scout was an experimental release through Microsoft’s Frontier early-access program. Microsoft listed three requirements: Frontier enrollment for the organization, specific Intune policies configured in the tenant, and a GitHub Copilot license for each user. The desktop app runs on Windows 11 and recent macOS versions. Check Microsoft Learn for current availability, since early-access terms change.

What admins should do now

1. Decide on Frontier. If you can run structured previews and give feedback, early access gives your team time to learn Scout’s behavior safely.
2. Clean up Entra and Intune. Scout depends on sound identity governance, Conditional Access and device compliance baselines.
3. Review Purview policies. Scout enforces the labels and DLP rules you actually have, so make sure they’re current. See our Purview DSPM for AI checklist.
4. Plan capacity governance. Background modes consume agent capacity; decide how to allocate it before users build automations at scale.
5. Communicate early. An agent that can send email and edit files changes how work is done, and users need to know what to expect.

Bottom line

Microsoft Scout is the first product in a new category of always-on agents, and others will follow. Whether you join Frontier now or wait for broader availability, the preparation is the same: clean identity, current data protection policies and clear communication. Those are also the foundations for Copilot Cowork and every other agent coming to Microsoft 365.

Last reviewed: October 2026. Originally published June 13, 2026.

Sources

• Introducing Microsoft Scout, your always-on personal agent (Microsoft 365 Blog)
• Microsoft Scout overview (Microsoft Learn)
• Microsoft launches Scout, an OpenClaw-inspired personal assistant (TechCrunch)
• Build 2026: Microsoft unveils Scout personal work agent (Thurrott)