Microsoft Scout is an AI assistant Microsoft launched at Build 2026 (June 2, 2026), built on the OpenClaw framework and surfaced inside Teams as a "virtual coworker." It has persistent access to your calendar, inbox, and Teams messages, and handles meeting conflicts, drafts replies, and executes repetitive office tasks automatically.
This guide is for Microsoft 365 users with a GitHub Copilot subscription. It covers how to enable Scout, complete initial setup, and three workflows.
Prerequisites
- A valid Microsoft 365 Business or Enterprise subscription
- A GitHub Copilot subscription (required by Scout as of Build 2026)
- Enrollment in the Microsoft Frontier program (early-access feature channel)
- Teams desktop or web app
Enabling Scout
- Sign in to the Microsoft 365 admin center and confirm your tenant has Frontier feature previews enabled.
- In Teams, find the Scout entry in the left navigation bar (compass icon) and click to start the first-time setup wizard.
- Name your Scout instance. Microsoft used "Sebastian" in its demo. This name is how Scout appears in Teams conversations.
- Grant Scout the necessary permissions to access your calendar, inbox, and Teams messages.
Configuring Preferences and Rules
Once enabled, you need to tell Scout your working preferences so it knows how to handle scheduling and communication.
Preference Types
| Type | Example | Behavior |
|---|---|---|
| Time rules | "Always protect dinner time—don't schedule meetings 18:00–20:00" | Scout auto-declines or reschedules meeting requests in that window |
| Priority preferences | "Always accept meeting requests from management first" | Scout resolves conflicts by this priority |
| Communication style | "Use formal tone for external emails, concise style for internal messages" | Scout follows these tone rules when drafting replies |
| Delegation rules | "If someone sends only a one-line question, ask them for context first" | Controls when Scout can reply autonomously |
Shahine demonstrated a key use case at Build 2026: after setting "always protect dinnertime," Scout automatically flagged conflicts and sent reschedule suggestions to anyone proposing a meeting during that window (source: Microsoft Build 2026 keynote demo).
Configuring via Chat
@Scout in Teams and send "start preference setup" or open the Scout settings panel to add rules through natural conversation. Scout remembers each rule and asks whether to auto-apply the same logic when similar situations come up.
Example conversation:
You: Don't schedule meetings before 2 PM on workdays, unless urgent.
Scout: Got it. Meeting requests before 2 PM will be auto-declined unless marked urgent. Should I apply this to other time slots too?
You: No, just this one.
Scout: OK. If I receive a meeting invitation before 2 PM next time, should I ask you first?
You: No, just decline and suggest an alternative time.
To edit or delete existing rules, @Scout again with "show my rules" to see the current list, then follow the prompts to modify or remove entries.
Workflow 1: Automatic Meeting Conflict Management
- Set protected hours: Tell Scout "don't schedule meetings during 12:00–13:30 on weekdays—that's lunch and break time."
- Set buffer rules: For example, "keep at least 15 minutes between back-to-back meetings."
- Set priority rules: For example, "auto-accept meetings from the CEO, but prompt me if it conflicts with protected hours."
Result: When a new meeting invitation arrives, Scout checks your calendar against your rules and accepts, declines, or reschedules accordingly. Participants receive the reschedule message from Scout, labeled "automatically arranged by your assistant."
Workflow 2: Auto-Generating Meeting Agendas and Talking Points
Scout can generate agendas from pre-meeting messages and documents.
- Create or open a meeting event in Teams.
- @Scout and send "generate an agenda for Tuesday's all-hands meeting."
- Scout scans participants' Teams messages from the past 24 hours and related documents, then compiles a draft agenda.
- Review the draft and publish it or ask for revisions.
TechCrunch confirmed at Build 2026 that Scout's prebuilt skills include calendar management and agenda drafting (source: TechCrunch, 2026-06-02).
Workflow 3: Drafting Automated Email and Message Replies
Scout drafts replies based on context, reducing repetitive communication.
- For an email or Teams message that needs a reply, @Scout and send "draft a reply."
- Scout reads the message context and your preference style, then generates a draft.
- Edit the draft in Teams before sending, or ask Scout to adjust the tone, add details, or shorten it.
Risk boundary: Scout's autonomous replies require your confirmation before sending by default. To enable auto-reply (no confirmation needed), you must explicitly enable it in Scout settings and use it only for low-risk message types such as acknowledgment receipts and automatic reschedules. Scout has built-in safety measures to prevent unsupervised AI agent mishaps (source: TechCrunch, 2026-06-02).
Scout vs. Microsoft Copilot
Scout is an active agent inside Teams and Microsoft 365, complementary to Microsoft Copilot's passive Q&A interaction. Both share the same Microsoft 365 data permissions system, but their roles differ: Copilot handles information lookup, Scout handles office workflow automation. See FAQ for details.
FAQ
Q: What's the difference between Scout and Microsoft Copilot? A: Microsoft Copilot is a Q&A AI assistant (you ask, it answers). Scout is an active agent that runs continuously and handles tasks proactively. Copilot is better for information lookup; Scout is better for automating office workflows.
Q: Can I use Scout without a GitHub Copilot subscription? A: Not currently. As of Build 2026, Scout requires a GitHub Copilot subscription.
Q: Can Scout read my personal emails? A: No. Scout only reads messages from your work account (the Microsoft 365 account you connect). You must grant this access explicitly during initial setup.
Q: Is Scout available in all regions? A: Currently available only in the US through the Frontier program. Timelines for other regions have not been announced.