Microsoft unveils Scout, an always-on Teams AI agent to automate office workflows

Microsoft introduced Scout at its Build developer conference: An always — on AI assistant inside Teams that can read work messages, calendars and email to reschedule meetings, draft replies, track commitments and act proactively based on user goals.

Microsoft announced Scout at the Build developer conference on Tuesday: an always — on AI agent that lives inside Teams, reads work messages, calendar entries and email, and automates routine office tasks such as rescheduling meeting conflicts and drafting professional — sounding responses. The company pitches Scout as a colleague — like assistant that can act proactively on a user’s behalf, reducing time spent on administrative work for nontechnical office workers.

Technically, Scout is built on an OpenClaw — style agent approach that drew attention earlier in 2026 and is positioned as an enterprise assistant geared toward everyday employees rather than developers. Microsoft says people can address Scout directly in Teams as if speaking to a coworker. Omar Shahine, the newly appointed corporate vice president of Microsoft Scout, described the product as a company — hired assistant that continues working when the employee is off the clock.

Scout can be configured with personal goals and preferences to take initiative. Shahine said he instructs Scout to protect family dinnertime, prompting the agent to flag meetings proposed during that period and propose rescheduling options. He also has Scout continuously scan his data to compile lists of promises made to and by him, enabling automatic reminders and drafted follow — ups tailored to outstanding commitments.

Microsoft has begun a limited rollout with a small group of customers and is testing a desktop client. The desktop app is rolling out today to subscribers who opted into Microsoft’s 'frontier' feature access and currently requires an active GitHub Copilot subscription. The staged launch is intended to let Microsoft iterate on Scout’s behaviors and monitor real-world use before a broader release.

The company acknowledges rough edges as the agent evolves. Shahine recounted that his Scout, nicknamed Sebastian, once sent an unformatted, run-on email — an example Microsoft uses to illustrate why users must choose which tasks to delegate and which to supervise. Internally, Microsoft sees sales teams among the earliest and fastest — growing adopters, while coders were the first group broadly affected by agent — driven workflow changes.

Scout’s rollout raises practical and security considerations for builders and administrators. Agentic tools increase exposure to prompt — injection and related attacks, so Microsoft has paired the limited launch with admin tools that log agent activity. For developers and IT teams, Scout’s Teams integration, proactive workflows, dependency on Copilot for desktop access, and early opt-in model are concrete signals to consider when planning integrations, permission models and monitoring.