Microsoft Scout Is the Always-On AI Agent Built Into M365
Microsoft introduced Scout on 2 June 2026, its first Autopilot agent for Microsoft 365, designed to run continuously across Teams, Outlook, OneDrive, and SharePoint without waiting to be prompted. Scout handles meeting preparation, scheduling conflicts, and status updates in the background using each user's own governed Entra identity. It is available now for Frontier programme members, with a broader preview in late June and general availability targeted for October 2026.
Operator Insight
Every AI assistant released in the past three years has been fundamentally reactive. You ask, it answers. You prompt, it produces. Scout breaks that pattern. It is the first generally available Microsoft product that runs without being asked, monitors your meetings and communications in real time, and takes action on routine work before you think to request it. For operators running lean teams, this is not a feature upgrade. It is a new operating model: one person with Scout handling their scheduling, preparation, and follow-up is functionally doing the work of one and a half people. The governance gap is real (tenant-level controls are still in development) and the current Frontier-only availability means most businesses cannot deploy it today. But operators who prepare now, by auditing which employee workflows are routine, repetitive, and low-risk, will be ready to move on day one of general availability in October.
30-Second Summary
Microsoft announced Scout on 2 June 2026, its first Autopilot-class agent for Microsoft 365. Unlike Copilot, which responds to prompts, Scout runs continuously in the background across Teams, Outlook, OneDrive, and SharePoint, proactively handling scheduling, meeting preparation, and routine task coordination without waiting to be asked. Each Scout instance operates under its own dedicated Microsoft Entra identity, meaning every action is attributable to a specific, directory-managed account rather than an anonymous shared service. Scout is available now as an experimental release for Frontier programme members, with broader preview in late June and general availability targeted for October 2026.
At a Glance
- Topic: Agent Systems
- Company: Microsoft
- Date: 2 June 2026
- Announcement: Microsoft Scout, the company's first Autopilot agent for M365, launched in experimental preview for Frontier programme members.
- What Changed: AI within Microsoft 365 moved from reactive (prompt and respond) to proactive (always-on background execution without prompts).
- Why It Matters: Every organisation running on M365 will encounter Scout. Understanding it before GA in October 2026 is a governance and readiness decision, not just a feature evaluation.
- Who Should Care: Operations leaders, IT managers, and any business operator with 10 or more people on Microsoft 365.
Key Facts
- Company: Microsoft
- Launch Date: 2 June 2026 (Frontier experimental preview); broader preview late June 2026; general availability October 2026
- What Changed: Scout introduced autonomous background execution to M365, handling routine work without prompts
- Who It Affects: Microsoft 365 users, IT administrators, operations teams, and any employee with a calendar, email, or document workflow
- Primary Source: Microsoft 365 Blog, Microsoft Build 2026
What Happened
Microsoft introduced Scout at Build 2026 on 2 June 2026, positioning it as the company's first Autopilot agent, distinct from its Copilot line of AI assistants. Where Copilot waits for a prompt and returns a response, Scout runs continuously, monitoring email, calendar, files, and communications across Teams, Outlook, OneDrive, and SharePoint, then taking action on routine tasks without being asked.
The initial task set is focused on time and meeting management: Scout proactively prepares briefing documents before meetings, flags scheduling conflicts across time zones, coordinates availability on behalf of users, and generates status updates for ongoing work. Users interact with Scout through the Teams interface and can extend its reach to local resources and Model Context Protocol servers, giving it access to external systems and tools.
The security architecture is designed for enterprise environments. Each Scout instance runs under its own governed Microsoft Entra identity rather than a shared service account, meaning every action Scout takes is attributable to a named, directory-managed actor. Credentials are scoped to individual tasks, redacted from logs, and managed under the same standards as other Microsoft first-party services. Microsoft acknowledged that tenant-level controls, allowing administrators to define what Scout can and cannot access across an organisation, are still in development and expected later in 2026.
Pricing is bundled with M365 E7 at $99 per user per month. An Agent 365 standalone add-on is available at $15 per user per month with an annual commitment. Current access requires Frontier programme enrolment, Intune policy configuration, and an opt-in attestation step.
Why It Matters
- The shift from reactive to proactive AI is the most significant change in how AI integrates with daily work. Scout is the first Microsoft product to cross that threshold in a governed enterprise deployment.
- Meeting preparation and scheduling coordination are among the highest-frequency, lowest-complexity tasks in knowledge work. Automating them at scale has a direct, measurable impact on how much time employees spend on high-value work versus administrative overhead.
- The dedicated Entra identity model means Scout's actions are auditable in the same systems already used for security and compliance. This is architecturally different from AI tools that operate under shared service accounts or anonymous session tokens.
- General availability in October 2026 is approximately four months away. Organisations that prepare governance policies, Intune configurations, and workflow mapping now will have a material deployment advantage over those starting from scratch at GA.
- The $15 per user per month standalone Agent 365 add-on is within the adoption range of small and mid-size businesses that do not require a full E7 licence.
- The governance gap (tenant-level controls still pending) is a legitimate constraint for regulated industries or businesses handling sensitive data. Deployment in those environments should wait for the control layer.
The David and Goliath View
There is a meaningful difference between an AI tool that helps your team do things faster and an AI agent that does things for your team while they work on something else. The first is a productivity multiplier. The second is a headcount question. Scout is the first Microsoft product that belongs in the second category: it does not require a prompt to start working, and it does not stop when the user closes a tab.
For operators running organisations with 10 to 200 people, Scout's initial task set targets exactly the administrative overhead that consumes disproportionate time in lean teams. A five-person sales team spending forty minutes per day per person on meeting prep and scheduling is burning three and a half hours daily on work that Scout can handle. At GA pricing, the return is straightforward to calculate.
The preparation that matters is not technical. It is operational: identifying which workflows in your team are routine, repetitive, and low-risk, and building the governance documentation that IT and legal will need before an autonomous agent runs inside your communications and file systems. Operators who treat October as an implementation deadline, and work backward from it now, will have a functional deployment in week one rather than month four.
Where This Fits in the AI Stack
Employee Amplification Systems: Scout is the most direct implementation of always-on amplification yet available in a governed enterprise platform. One employee with Scout handling scheduling, preparation, and routine coordination effectively operates with the administrative bandwidth of a larger team.
Secure AI Brain: The Entra identity model and per-task credential scoping mean Scout's architecture aligns with enterprise security requirements. The pending tenant-level controls are the remaining governance gap, and operators should factor that into deployment timing.
Questions Operators Are Asking
How is Scout different from Microsoft Copilot? Copilot responds when you ask it something. Scout operates without being asked, running continuously across your M365 environment and acting on routine tasks it identifies from your calendar, email, and files. They are different products with different operational models. Copilot is an assistant; Scout is an agent.
Is Scout available to businesses not on M365 E7? The Agent 365 standalone add-on ($15/user/month annually) gives non-E7 users access at a lower price point. However, current experimental access still requires Frontier programme enrolment, and general availability is October 2026 regardless of licence tier.
What can Scout actually do today? In the current experimental preview, Scout focuses on calendar and meeting workflows: preparing briefing documents before meetings, flagging scheduling conflicts, coordinating availability, and generating status updates. The scope will expand as the product moves from experimental to general availability.
Should we be concerned about Scout accessing our business communications? The Entra identity model means Scout's access is governed and auditable, which is better than many AI tools in use. The legitimate concern is the tenant-level control gap. Until Microsoft ships organisation-wide governance controls, IT administrators have limited ability to enforce policies on what Scout can access across all users. Deployments in regulated industries or handling sensitive data should wait for that control layer.
What should we do to prepare before October? Three steps: audit your Intune and Entra configuration to confirm the prerequisites are in place; map which employee workflows are suitable for Scout's initial capabilities (scheduling, meeting prep, status updates); and draft a data handling policy for AI agent access to communications and calendar data. These three steps take the long delay out of a GA deployment.
Citable Summary
What happened: Microsoft introduced Scout on 2 June 2026, its first Autopilot agent for M365, which runs continuously across Teams, Outlook, OneDrive, and SharePoint handling routine tasks without prompts. It is available in experimental preview now, with general availability in October 2026.
Why it matters: Scout marks the shift from reactive AI assistants to proactive AI agents within the world's most widely deployed enterprise productivity platform, with direct implications for how routine work gets done across every organisation on M365.
David and Goliath view: The operational preparation that matters now is identifying which workflows are routine and low-risk, and building the governance documentation needed before an autonomous agent runs inside your communications and files. Operators who start that work now will deploy in week one of GA rather than month four.
Offer relevance:
- Employee Amplification Systems: Scout's background execution of scheduling, preparation, and coordination tasks amplifies per-person output without adding headcount.
- Secure AI Brain: The Entra identity model and per-task credential scoping create an auditable agent security architecture, though operators should wait for tenant-level controls before regulated-environment deployments.
Why This Matters for Operators
- ✓
Map the routine, repetitive tasks across your team's calendars and inboxes now. Scout's first capabilities target exactly those workflows: meeting prep, scheduling coordination, and status updates. Understanding your volume is the prerequisite to measuring Scout's impact.
- ✓
Check whether your organisation is enrolled in the Microsoft 365 Frontier programme. If not, determine whether your current M365 licensing qualifies and whether a Frontier enrolment makes sense before broader preview opens in late June.
- ✓
Review your Microsoft Entra and Intune configuration before Scout reaches general availability in October. Scout requires Intune policy configuration and opt-in attestation, so IT readiness is the constraint, not commercial availability.
- ✓
Do not adopt Scout for sensitive communications or compliance-critical workflows yet. Microsoft has acknowledged that tenant-level governance controls are still in development, with broader controls expected later in 2026.
Related Intelligence
Related Briefings
- Meta Business Agent Goes Global on WhatsApp and InstagramMeta | Agent Systems
- OpenAI Brings Codex to Non-Developers with Six Business PluginsOpenAI | Agent Systems
- Microsoft Launches Its Own AI Coding Models to Cut OpenAI RelianceMicrosoft | Enterprise AI
- Microsoft Build 2026: Windows Becomes an Operating System for AI AgentsMicrosoft | Agent Systems
Related Signals
- [High] Anthropic launches Claude Agent SDK
Standardised framework for deploying production AI agents with built-in tool orchestration and safety guardrails.
Explore Related Intelligence
How This Maps to David & Goliath
Apply This to Your Business
Want to see what this means for your team?
Tell us a little about your business and we will map the specific opportunity for your sector and team size.