Editorial illustration for Microsoft's Andreou: OpenAI Models Excel in Specific Tasks
Microsoft Shifts Copilot Strategy: Home, Code, Autopilot
Microsoft's Andreou: OpenAI Models Excel in Specific Tasks
Microsoft pulled Copilot out of several Windows apps earlier this year, a quiet admission that bolting a chatbot onto every menu bar doesn't automatically make it useful. The company is now betting on a different approach: one Copilot, built around three capabilities called Home, Code, and Autopilot, pitched as an "OS for work" where chatting, building apps, and running agents all happen in the same place.
Jacob Andreou, Microsoft's EVP of Copilot, sat down with The Rundown to talk through what that redesign is actually trying to fix. He's the one who greenlit the earlier rollout across Windows apps and watched the traffic numbers look good while actual usage didn't follow. That experience, he says, changed how he thinks about shipping AI products, and he expects the same pattern to show up again this fall as Microsoft pushes out more personal agents to consumers.
The conversation covers how much autonomy an agent should get before a human needs to step back in, why a smarter model alone doesn't solve the product problem, and what Andreou thinks AI-native work will actually look like once the current wave of features settles.
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 this matters
Andreou's comment is an admission Microsoft has mostly avoided making out loud: no single model wins everywhere, so Copilot's job is to pick the right one per task rather than bet on one lab. That's a real shift from the "our AI is best" marketing most vendors still run. For developers and founders, it's a signal to stop treating model choice as a one-time decision baked into a product.
If OpenAI's models handle Excel-style logic better and Anthropic's handle visual/code consequences better, the smart architecture is modular, with routing logic that swaps models by task rather than locking into one API. For researchers, it's confirmation that benchmark leaderboards are getting less useful as a proxy for real-world fit, since "best overall" increasingly means nothing once you get specific about the job. Microsoft has the resources to build that abstraction layer at scale through Copilot; smaller teams building AI products will need to decide whether to build similar routing themselves or just wait for platforms like this to do it for them.
Worth watching whether Microsoft ever names which tasks go to which model, or keeps that under the hood.
Common Questions Answered
Why did Microsoft remove Copilot from several Windows apps earlier this year?
Microsoft removed Copilot from multiple Windows apps because simply integrating a chatbot into every menu bar did not automatically make it useful for users. The company recognized that this blanket approach was ineffective and decided to pivot toward a more strategic implementation focused on delivering genuine value.
What are the three core capabilities that Microsoft's new Copilot strategy is built around?
Microsoft's redesigned Copilot is built around three main capabilities: Home, Code, and Autopilot. These capabilities are positioned as an integrated "OS for work" where users can chat, build applications, and run agents all within the same unified platform.
According to Jacob Andreou, why is it important that Copilot selects different models for different tasks?
Andreou emphasizes that no single AI model excels at every task, so Copilot's approach of selecting the right model per task prevents intelligence and value from centralizing in the hands of just a couple of companies. This strategy ensures that value is distributed more broadly rather than concentrated among a few dominant AI labs.
How does Microsoft's multi-model approach differ from typical AI vendor marketing?
Most AI vendors market their products by claiming their single model is the best across all use cases, but Microsoft's approach openly acknowledges that different models like OpenAI's and Anthropic's excel at different tasks. This represents a significant shift away from the traditional "our AI is best" marketing strategy that competitors still employ.
What signal does Copilot's design send to developers and founders about model selection?
Copilot's multi-model architecture signals to developers and founders that they should not treat model choice as a permanent, one-time decision baked into their product. Instead, they should remain flexible and willing to swap models based on which performs best for specific tasks within their applications.
Further Reading
- Microsoft Dials Back Copilot: Windows AI Gets Less Intrusive - WindowsForum
- Microsoft Trains Sales to Promote In-House AI Over OpenAI and Anthropic - LinkedIn
- Claude + GPT: Multi-model intelligence in Copilot - Microsoft Tech Community
- GPT-5.6 now available in Microsoft Foundry - Microsoft Azure
- Users Cheer as Microsoft Accidentally Removes Hated AI Copilot - Futurism