Ben Stegink
Microsoft Scout is a new desktop application designed to serve as an always-on personal agent, bridging your local environment with cloud intelligence. It connects to LLMs, interacts with your local file system and web browser, supports MCP server integrations, and pulls in workplace data through Work IQ. It runs on both macOS and Windows, and it arrived with enough capability to be genuinely interesting and enough friction to be genuinely frustrating. It also lands in an increasingly crowded desktop-agent space; we previously compared Claude Cowork and Copilot Cowork, and Scout is Microsoft’s most direct answer to the former.
What It Takes to Get Running
Before you see a single prompt, Scout requires two separate Copilot licenses: a Microsoft 365 Copilot license and a GitHub Copilot Enterprise license. GitHub Copilot Pro does not qualify. Tally those up and you are looking at roughly $50 per month before the application does anything at all.
Beyond licensing, an administrator must enable Scout through the Microsoft 365 admin center, then push a configuration policy to end devices via Microsoft Intune or Group Policy. If your organization is starting to take agent governance seriously, that admin-gated rollout is a feature rather than a bug. The admin access overview walks through this, but the setup path is fragmented enough that first-timers should expect to spend real time on prerequisites before reaching the splash screen. Once you clear all of that, the getting started guide covers the rest of initial configuration.
The Core Experience
Once you are inside, Scout presents a clean interface with new chat, automations, and co-create workspaces. A model selector lets you choose from whatever models your organization has enabled through GitHub Copilot, which may include Claude Opus, GPT, or others depending on your admin configuration. Model selection matters more here than in most tools because every interaction draws from your GitHub Copilot token budget. A single lightweight query can run around sixteen cents, and iterative work on documents or code adds up quickly.
The chat experience covers what you would expect: reading and summarizing your Microsoft 365 inbox, drafting replies, managing calendar events, browsing the web, and working with local files. Work IQ provides the Microsoft 365 connectivity, and under the hood Scout shells out to command-line calls rather than routing everything through the LLM context window, which helps contain token costs.
Where Scout Pulls Ahead
The clearest advantages Scout has over Microsoft 365 Copilot alone are local file access and MCP integration. Microsoft 365 Copilot cannot reach files on your desktop or interact with MCP servers. Scout does both, which opens up workflows that would otherwise require switching between multiple tools.
The automations and heartbeat system is where Scout gets genuinely interesting. Heartbeats are persistent background checks that run on a schedule, such as scanning your inbox and Teams messages every thirty minutes for anything urgent. Automations are more structured multi-step workflows: crawl specific news aggregators each morning, compile an industry briefing, or monitor a GitHub repository for pull request conditions. You can specify which model each automation uses, run browser interactions headlessly, and format outputs in whatever structure you need.
The catch is that the application must remain open and the machine must stay awake for any of this to run. There is no background service. Scout sessions and memories sync to OneDrive, so your context follows you across devices, but the scheduling itself is entirely dependent on a live, running application.
Skills and MCP configurations work similarly to other agentic tools. You can add remote or local MCP servers, import skills from GitHub or a marketplace, and toggle them on or off per session to manage context. The full documentation covers available capabilities in detail.
The Pricing Reality
Work IQ, the API layer Scout uses to access Microsoft 365 data, carries its own consumption-based pricing on top of the two Copilot licenses you already need. That means three meters are running at once: the flat monthly cost for the licenses, the GitHub Copilot token budget every chat and automation draws down, and the Work IQ calls each time Scout reaches into your mail, calendar, or files. None of these is alarming in isolation, but they compound. An ambitious set of heartbeats and automations that feel free to configure can quietly become the most expensive thing on your bill.
The honest takeaway is that Scout rewards deliberate use. Pick efficient models for routine automations, reserve the premium ones for work that actually needs them, and treat every scheduled heartbeat as a recurring charge rather than a set-and-forget convenience. Used that way, the cost stays reasonable. Used carelessly, it does not.
Should You Use It?
Scout is a capable tool that does things Microsoft 365 Copilot simply cannot, namely reaching your local files and speaking MCP. For technical users who already hold both Copilot licenses and want a single agent that bridges the desktop, the browser, and their Microsoft 365 data, it is worth a serious look. The automations and heartbeat model is the standout feature and points clearly at where this category is headed.
For everyone else, the math is harder. The dual-license requirement, the consumption-based Work IQ pricing, the admin-driven rollout, and the requirement that the app stay open for any automation to fire all add up to a tool that asks a lot before it gives anything back. It is a strong 1.0 with rough edges, and the absence of a true background service is the limitation most likely to frustrate the people who would otherwise get the most out of it.
Conclusion
Microsoft Scout is a genuine step forward for desktop agents inside the Microsoft ecosystem, with local file access, MCP support, and a scheduling model that hint at how useful this kind of always-on assistant can be. It also comes with a steep price of entry, both in dollars and in setup, and a few design choices that will give some teams pause. If you are weighing whether Scout fits your environment, or how to govern its licensing and token costs before they get away from you, reach out and let’s talk.
