Microsoft Copilot EVP Jacob Andreou on Closing AI's Product Gap and Managing Agent Autonomy

Microsoft Copilot EVP Jacob Andreou on Closing AI's Product Gap and Managing Agent Autonomy In a Q&A with The Rundown, Microsoft's EVP of Copilot, Jacob Andreou, discussed how the company redesigned its Copilot strategy around product value rather than entry-point volume, the necessity of multi-model routing, and the boundaries required for enterprise AI agents. Microsoft pulled Copilot from several Windows apps after finding high traffic did not translate into real user value, leading to higher per-user usage through fewer entry points. Copilot introduced an Auto mode to route tasks between different frontier models based on task suitability rather than relying on a single provider. Andreou highlights an AI product 'overhang' where powerful models lack appropriate form factors to translate raw intelligence into broad practical value. Agent autonomy must be constrained by separating reversible actions from irreversible 'one-way door' decisions that mandate a human in the loop. Copilot's new structure centers on three capabilities: Home, Code, and Autopilot, with internal adoption driven heavily by sales teams and inbox workflow reimagining. Refining Entry Points and Consumer Utility Microsoft scaled back Copilot integrations across multiple Windows apps after observing that prominent, high-traffic entry points delivered relatively low user value. Andreou noted that early consumer features like Copilot Tasks provided brief convenience—such as scheduling rides or food delivery—but lacked the depth needed for complex tasks like financial planning. Consequently, reducing entry points resulted in increased usage per active user as Microsoft shifted focus toward earning product retention through substantial utility. The Shift to Multi-Model Architectures Andreou argued that no single AI provider currently dominates across every use case. OpenAI's models, such as the 5.6 class, excel at structured analysis in tools like Excel, whereas Anthropic's models show superior understanding of visual code implications for presentations. Because requiring professionals to manually select models introduces friction, Copilot implemented an Auto routing mode that automatically allocates tasks to the best-suited model while preserving manual selection options. Bridging the AI Product Overhang Andreou described the current state of generative AI as an 'overhang' period, where advanced models like OpenAI's Astra and Anthropic's Fable lack intuitive product form factors comparable to what chat interfaces did for GPT-3 or Claude Code did for Opus 4.5. He warned that unless software products effectively package raw model intelligence into functional applications for everyday workers, industry value and technical capability will centralize within a few model developers. Governing Enterprise Agent Autonomy To address enterprise security risks, Andreou recommended categorizing agent tasks into reversible 'two-way doors' and irreversible 'one-way doors.' Any action involving contacting external persons, deleting files, or making unalterable changes requires a human in the loop. For Autopilot, Microsoft pre-computes operational boundaries for browser sessions; if an agent's initial plan fails and it attempts an alternative solution path, it must request secondary user approval before continuing. Internal Workflows and AI-Native Work Internally at Microsoft, the sales team emerged as the earliest high-volume adopter of Autopilot, applying it to pipeline management, meeting prep, and automated follow-ups. Andreou uses Autopilot as his primary email client to generate triage briefs and escalate high-priority items, such as messages from CEO Satya Nadella. He characterized AI-native workers as those who redesign broad workflows rather than marginally accelerating discrete tasks, pointing to non-technical staff using Copilot Code to develop team-wide research dashboards.

微软Copilot副总裁Jacob Andreou谈AI产品断层与落地反思 微软Copilot执行副总裁Jacob Andreou在专访中阐述了AI产品设计的新思考，强调单纯增加功能入口无法带来持久价值，未来关键在于打造承载模型能力的产品形态，并通过多模型智能路由与安全边界重塑工作流。 微软削减了Windows中低价值的高流量Copilot入口，反而提升了单用户使用率与留存深度。 单一模型无法垄断所有任务优势，Copilot引入Auto模式自动为不同场景匹配最合适的基础模型。 当前AI处于能力与产品形态脱节的悬空期，若缺乏优秀产品承载，价值将高度集中于少数底层模型公司。 企业级Agent治理需区分可逆与不可逆行为，不可逆操作必须由人类在环审核。 AI原生员工不仅追求任务提效，更利用自然语言开发工具重塑协作流程与决策分工。 削减入口与聚焦真实深度 Andreou表示，增加流量入口并不等同于交付价值。微软此前在Windows多款应用中嵌入Copilot，虽然带来了曝光，但在部分场景中显得突兀且价值有限。团队随后削减了入口，反而实现单用户使用量与用户基数的提升。消费级任务代理初期虽能带来订餐或叫车的新奇感，但在财务规划等复杂任务上浅尝辄止，验证了AI工具必须具备深层解决能力才能持续留存。 多模型路由与Auto模式 业内不再存在各方面均具绝对优势的单一模型，不同模型在Excel计算或PowerPoint视觉代码呈现等不同任务上各有所长。让企业和专业人士自行辨析模型适配成本过高，因此Copilot推出Auto模式，在保留手动选择权的同时，由系统自动将具体任务路由至最合适的模型以优化输出质量。 模型能力与产品形态的悬空期 新一代模型正处于缺乏适配产品形态的悬空阶段，类似于早期未被对话界面激活的GPT-3。Andreou指出，若无法通过优秀的产品形态将底层原始智能转化为用户可感知的实际价值，AI的技术红利与商业价值将高度集中于极少数模型研发厂商手中。 Agent自主性与单向门安全边界 针对智能体自主性带来的企业安全担忧，Andreou提出以决策可逆性设立权限界限。联系他人、删除文件等不可逆的单向门操作必须实行人类在环确认；可逆操作可在预先设定的执行边界内自主运行。此外，由于智能体具备持续尝试的特性，当其陷入停滞或尝试变更解决路径时，必须再次触发权限申请。 AI原生工作流的实践与重塑 微软内部数据显示，销售团队是Autopilot采用率最高的部门，常用于商机管理与跟进。Andreou个人亦使用Autopilot进行收件箱智能分流与重点邮件上报。真正的AI原生员工并非仅加速单项任务，而是重新审视工作流与人机决策分工，例如非工程岗位的研究主管使用Code能力开发团队共享应用，将个人流程转化为组织级协作资产。

[Read Online](https://therundownai.beehiiv.com/p/microsoft-s-jacob-andreou-on-ai-s-product-gap) ^| [Sign Up](https://www.therundown.ai/subscribe?utm_source=therundownai.beehiiv.com&utm_medium=newsletter&utm_campaign=rundown-1019) ^| [Advertise](https://therundownai.typeform.com/to/kraZ1TSO?utm_source=therundownai.beehiiv.com&utm_medium=newsletter&utm_campaign=rundown-1019) **Good morning, {{ first\_name | AI enthusiasts }}.** AI is built into almost every app we open, but that doesn't automatically make it useful. Microsoft's answer is to bring it all into one place with Copilot. Built around [three new capabilities](https://www.microsoft.com/en-us/copilot/?OCID=CGE_csocial_MG_CopilotAppEngagement_868meb6uh&utm_source=therundownai.beehiiv.com&utm_medium=newsletter&utm_campaign=rundown-1019) — Home, Code, and Autopilot — it's being pitched as an “OS for work” where you can chat, build apps, and work alongside agents. In partnership with Microsoft, we sat down with Jacob Andreou, the company's EVP of Copilot, for an exclusive Q&A on what the new Copilot is trying to fix, where agents still need a human in the loop, and the lessons that changed how he thinks about AI products. **In today’s AI rundown:** What Microsoft had to relearn with Copilot How much freedom should an agent have? Smarter models aren't enough Does the model still matter? What AI-native work looks like **LATEST DEVELOPMENTS** *Image credits: Kiki Wu / The Rundown* **The Rundown**: Microsoft removed Copilot from several Windows apps after finding they brought traffic but little value. Andreou says he hit the same wall as a user of the company's own consumer agent, and expects this fall's personal agents to hit it too. **Cheung:** Microsoft pulled back on Copilot in some of its Windows apps. What did that teach you about where AI doesn't belong? **Andreou:** We had to relearn that putting more people into the top of the funnel doesn't equal delivering more value to them. We picked a bunch of entry points that looked high traffic but were relatively low value. There were even a couple places where you could be using your Windows machine and then suddenly, Copilot. That doesn't help anyone. **Andreou added:** I really, really instead believe in products earning their right to exist. Usage is fleeting unless you're delivering real value. We have less entry points that exist today, but have more usage per user and more people using it. **Cheung**: What's something you've changed your mind about with AI agents, and what changed it? **Andreou:** At the beginning of this year, we released Copilot Tasks in the consumer product. It increased my consumption a lot. I was ordering more food delivery, and it would call Ubers for me when my meetings ended. That felt magical for a few weeks, and then at some point it was like eating too much ice cream. **Andreou added:** For the harder stuff in my life, like financial planning or planning a vacation around work commitments, it was kind of an inch deep. That was a big learning for me: something that was cool in the early days needs more meat to be something I feel amazing about using. The consumer side of this right now is very hectic. You now have Muse, Instinct, and all these other folks. I think those products will learn similar lessons and evolve accordingly over time. **Why it matters:** As companies rush to add AI to every product, Microsoft's experience points the other way. Cutting entry points raised usage per user, showing what keeps people coming back isn't convenience, but how much the AI can actually handle beneath the initial surface gains. **The Rundown:** Andreou says no single lab's models win at everything anymore, and that expecting workers to track which model suits which job has become a cost of its own. Copilot's answer is an Auto mode that picks for them while still offering the option to choose. **Cheung:** Does the model still matter anymore, or is it all about the product on top? **Andreou:** The model definitely matters. But having to behave as if the model really matters is a large tax to put on professionals and companies. **Andreou added:** For the first half of this year, you could take the full line-up from a single provider and get the best experience across everything. That's changed. What became clear is that certain models became really good at certain tasks. OpenAI's new class of models, starting with 5.6, were really smart, so in places like Excel they were really good. But Anthropic's models still had more of a native understanding of the visual consequences of the code they produce, so for drafting a PowerPoint, they still made sense. It's become so nuanced that the majority of people are just drawn to solutions that lead to great output. With Copilot, we still want to let you pick a specific model, but we want Auto to give you the best output, whatever you're doing. **Why it matters:** Performance now depends on the type of output rather than which model is currently on top. That's Andreou's case for a multi-model approach that routes each task to the model that fits best, while still letting people choose a specific model if they want. **The Rundown:** Andreou says AI is in an “overhang” moment, where the newest models lack the right products built around them to be useful to most people, and if this gap persists, AI’s value will centralize to a few companies. **Cheung:** What problem were you trying to solve with the new Copilot that the old approach couldn't? **Andreou:** Each generation of intelligence needs a product form factor for you to actually get value out of it. GPT-3 was generally under-appreciated until chat showed up and you could actually talk to the model for the first time. Opus 4.5 came alive via Claude Code and Cowork. Today, we have Astra from OpenAI and Fable from Anthropic, and it feels like we're missing the product form factor to get the magic out of these models. **Andreou added:** If we don't build products that translate raw intelligence into real value for real people, intelligence will centralize in the hands of a couple of companies, and value will centralize along those same lines. That’s what we’re trying to solve with Copilot. **Why it matters:** Microsoft doesn't make either model Andreou names, so this is also a description of its own position. Its vision is that the product around a model will matter more than the model, and that the app you work in will shape your results more than the lab behind it. **The Rundown:** The more freedom an AI agent has, the more it can get done, and the more things can go wrong. Andreou's rule of thumb: sort every action into one-way doors (irreversible) and two-way doors (reversible). **Cheung:** Autonomy makes agents useful, and also concerns IT teams. How should companies decide how much freedom to give an agent? **Andreou:** The tricky part about this is the same things that make those kinds of products amazing, their flexibility and their autonomy, are the same two things that make them scary to put to work in an enterprise. My first experience with OpenClaw was setting it up inside my home network and it helped me fix a bunch of things on my home network, but it didn't have access to any of those things. It found a way in, which was a bit terrifying. Obviously, in an enterprise context, that's not acceptable. **Andreou added:** If an agent is contacting another person, deleting a file, or making an irreversible decision, a human needs to be in the loop every time. For reversible work, it can operate independently inside clear boundaries and ask again if the task or risk changes. With Autopilot, we pre-compute what the browser session should look like when the task first starts, and that becomes the boundary. If it tries to solve the problem differently, it has to ask for permission again. Agents are persistent. If they get stuck, they'll try something else, and that's where that second ask comes in handy. **Why it matters:** Most talk about agent risk centers on what an agent can access. Andreou's home-network story is about what an agent does when its first plan fails. If you're testing agents at work, list the actions that can't be undone before you start, and ask how the tool behaves when it gets stuck. **The Rundown:** Andreou handles his inbox through Autopilot, and argues a great AI-native employee doesn’t stop at making tasks a little faster — they reimagine their whole workflow. **Cheung:** Based on what you've seen internally, how is Autopilot actually being used? **Andreou:** The biggest surprise was that our top adopter was the sales team. They’re using it for everything from ongoing pipeline management to prepping for client calls to making sure they follow up at the right times. Personally, I use it as my primary interface to email. I don't really open my Outlook inbox. When I wake up, it has a triage brief ready. When I want to dive into a thread, I just talk to Autopilot and it catches me up while knowing when to escalate. If it's an email from Satya that I haven't responded to, it'll escalate it to reach me. **Cheung:** What does a great 'AI-native' employee do that others don't? **Andreou:** They don't just use AI to make tasks a little faster. They rethink the workflow: what should I do, what should I delegate, and where does human judgment matter most. **Andreou added:** One of our user-research leaders, who isn't a software engineer, used Code to build a shared app that continuously pulls together competitive comparisons and product research from across the organization. What started as an individual workflow is now something the broader team relies on every week. **Why it matters:** Being AI-native still comes down to human judgment and decision-making. The research leader at Microsoft didn't need to know how to code, but did need the expertise to decide what was worth building. Discover how Copilot's new capabilities help you build, customize, and scale AI at work. **Home:** Your starting point in Copilot, with chat, Cowork, and full Office capabilities in one place. **Code:** Build apps, dashboards, and workflows in a safe environment by describing them in plain language, no coding experience needed. **Autopilot:** An always-on digital teammate with its own identity, memory, and workspace that keeps working even when you're not. See you soon, *Rowan, Zach, Shubham, Jennifer, and Nate — the humans behind The Rundown*