Microsoft Scout: the first Autopilot agent, and the governance layer that isn’t finished yet
Quick summary
Microsoft Scout, described by Microsoft as the first “Autopilot” agent, is available now in Frontier preview on Windows and macOS, covering:
This is a new product category, not a feature update, and it’s worth treating with the scrutiny that deserves. General availability timing hasn’t been officially confirmed by Microsoft at the time of writing.
Scout is Microsoft’s first “Autopilot,” a new category of agent that works continuously in the background, holds its own identity, and acts on a user’s behalf without being prompted each time. It’s a genuinely different kind of thing to Copilot Chat or an agent built in Copilot Studio, and it’s already live, gated behind Frontier enrollment, for organisations willing to evaluate it early.
What’s changing
Scout is available now through Frontier as an early desktop experience on Windows and macOS, the same experience Microsoft says its own employees have been using internally. General availability timing has not been officially confirmed; Microsoft states only that broader rollout timing will be communicated at a later date, so treat any specific GA date you see reported elsewhere as unconfirmed until Microsoft says otherwise directly.
Scout integrates across Teams, Outlook, OneDrive and SharePoint, using Work IQ to build an ongoing picture of how a person works, what they prioritise, and what needs to happen next, rather than requiring users to brief it each time. The app is off by default and requires admin enablement before anyone can sign in.
Access is gated by four things together: Frontier enrollment, Intune policy configuration, a required admin opt-in and attestation, and a GitHub Copilot licence for eligible users, all four need to be in place, or sign-in simply fails without a clear explanation to the user of why.
Why this matters more than it first appears
This is the most significant update in this set so far, and it deserves proper attention rather than a routine read:
- Data flows outside Microsoft 365 as a documented, intentional part of this preview. Microsoft’s own compliance answers confirm the preview includes data paths outside Microsoft 365, described as GitHub-based inference, and that admin attestation is required specifically because of this. That’s a materially different data governance question to anything else covered in this set.
- Scout requires a paid third-party licence to function at all. Eligible users need a GitHub Copilot licence for AI credit billing, meaning this isn’t purely a Microsoft 365 licensing decision, it pulls in a separate vendor relationship and a separate cost line that procurement and finance stakeholders should know about, not just IT.
- The governance control layer appears to still be catching up to the product itself. Independent reporting on Scout’s rollout (not part of Microsoft’s own roadmap message, so treat this as a signal to verify directly rather than a confirmed fact) suggests full tenant-level admin controls are still in development, with fuller availability expected later in 2026. If accurate, that means Scout is live and usable before the governance tooling to fully manage it at scale is complete, worth confirming directly with Microsoft before enabling anything beyond a tightly controlled pilot.
- There is a real safeguard worth acknowledging. Scout uses a tiered permission system and requires human sign-off before executing highly sensitive operations, this isn’t an agent acting with no checks at all, but the guardrail is action-level, not a substitute for reviewing the data governance question first.
Who’s affected
- Organisations already enrolled in, or considering, Microsoft’s Frontier programme
- IT admins managing Intune, identity and access controls
- Security and compliance stakeholders, who should be involved before this is enabled, not after
- Finance or procurement teams, given the GitHub Copilot licensing dependency
- End users who meet licensing and admin-configured prerequisites
What we’d recommend doing now
Given the scale of what this actually is, treat this differently to a routine feature rollout:
- Review this with security and compliance stakeholders before enabling anything, specifically around the confirmed data flows outside Microsoft 365 and what that means for your regulatory or contractual obligations.
- Confirm the current state of tenant-level governance controls directly with Microsoft rather than relying on third-party reporting, given the gap between the product being live and full admin controls reportedly still maturing.
- Loop in finance or procurement early, since Scout’s dependency on GitHub Copilot licensing is a genuine cross-vendor cost and contract consideration, not just an internal IT decision.
- If you proceed, start with a tightly scoped pilot, complete the Intune configuration and attestation carefully, and brief helpdesk that sign-in failures usually indicate a missing prerequisite rather than a fault.
- Set clear expectations with any pilot users that this is an early Frontier experience, likely to change, rather than a finished product.
Where we can help
Scout is a genuinely different category of risk and opportunity to most updates in this set, worth a proper conversation before any enablement decision, not a quick review.
Talk to our support team →
Talk to a consultant →
Explore our Copilot security and compliance training →
This update is based on Microsoft 365 Message Centre update MC1332811, published 2 June 2026. Rollout dates are provided by Microsoft and may change.
Don’t enable Scout before your security team has seen it
Frequently Asked Questions
What is Microsoft Scout?
Microsoft’s first “Autopilot,” a new category of always-on AI agent that works continuously in the background with its own identity, acting on a user’s behalf across Teams, Outlook, OneDrive and SharePoint without needing to be prompted each time. It’s built on the open-source OpenClaw framework and powered by Work IQ.
Is Microsoft Scout available now?
Yes, but only through Frontier preview on Windows and macOS, for organisations enrolled in Microsoft’s Frontier programme. General availability timing has not been officially confirmed by Microsoft.
Does Microsoft Scout send data outside Microsoft 365?
Yes. Microsoft’s own compliance documentation confirms the preview includes data paths outside Microsoft 365, described as GitHub-based inference, which is why mandatory admin attestation is required before enabling the feature.
Do you need a GitHub licence to use Microsoft Scout?
Yes. Eligible users need a GitHub Copilot licence, used for AI credit billing, in addition to Microsoft 365 and Frontier enrollment requirements.
Are there admin controls for Microsoft Scout?
Some. Access is gated through Intune configuration, Frontier enrollment, and required admin opt-in and attestation. Independent reporting suggests fuller tenant-level governance controls are still being developed, worth confirming the current state directly with Microsoft before wider deployment.
When is Microsoft Scout rolling out more broadly?
Microsoft states only that broader rollout timing will be communicated at a later date. Any specific general availability date reported elsewhere should be treated as unconfirmed until Microsoft states it directly.