Microsoft merges enterprise and consumer Copilot teams for a unified platform

Microsoft is consolidating the teams developing consumer and enterprise Copilot. The company wants to remove internal boundaries between the two versions of the assistant, accelerate feature releases, and create a more cohesive product for users at home and at work.

Why Change the Structure

Until now, Copilot within Microsoft existed in several parallel streams: separate teams were responsible for consumer experience, enterprise scenarios, Microsoft 365 applications, and platform elements. This approach helped quickly roll out AI across the entire ecosystem, but over time it began creating fragmentation. The same brand covered different interfaces, different capabilities, and different logic—from Windows and web chat to Word, Excel, Outlook, and Teams.

Microsoft now wants to transform Copilot from a collection of related products into a unified system. Within the company, this is directly tied to a new phase of AI: assistants should not only answer questions but also execute multi-step tasks, coordinate actions across applications, and work as agents. For such a scenario, releasing features separately is no longer sufficient.

A common architecture, unified product priorities, and fewer internal gaps between work and personal scenarios are needed.

Who Is Now Responsible

Microsoft's unified Copilot is being built around four directions: Copilot user experience, Copilot platform, Microsoft 365 applications, and AI models. Jacob Andreuw, who received the role of executive vice president for Copilot and direct reporting to Satya Nadella, is now responsible for the overall experience for both consumer and enterprise users. Ryan Roslanski, Perry Clark, and Charles Lamanna will continue to oversee applications and the platform layer, and should connect Copilot with Microsoft 365 and the company's infrastructure.

"We are transitioning from a set of great products to a truly integrated system,"

Satya Nadella described the purpose of the restructuring in a message to employees.

In practice, this means Microsoft wants to eliminate situations where the same Copilot feels like several different products under one brand. Users should see a more unified interface, and the team should be able to more quickly transfer successful features from the enterprise stream to the consumer one and vice versa. For the Copilot brand, this is an important step: the company is betting not on a scattered set of separate AI entry points, but on one main assistant layer on top of its services.

Betting on Models and Agents

A separate part of the reorganization relates to Mustafa Suleyman. He is shifting focus from product operations to the model layer and Microsoft's long-term AI strategy. In a message to employees, Suleyman explained that over the next five years the company wants to spend on creating its own world-class models that will be better suited for enterprise tasks, form separate product lines for business scenarios, and simultaneously reduce the cost of maintaining large AI workloads. For Microsoft, this is critical if Copilot is to scale to millions of users and increasingly autonomous agents.

The reorganization comes immediately after a series of major announcements in March. Microsoft has already unveiled Wave 3 for Microsoft 365 Copilot, the Agent 365 service and Frontier Suite for enterprise customers, and is separately promoting Copilot Cowork and Work IQ. According to the company itself, paid Copilot seats have been growing at more than 160% year over year, daily usage has increased tenfold, and the product is already used by 90% of Fortune 500 companies. This is the moment when fragmented development begins to hinder scale.

• Wave 3 adds new agentic scenarios in Word, Excel, PowerPoint, and Outlook
• Agent 365 serves as a management, monitoring, and protection layer for AI agents in the company
• Copilot Cowork is designed for long multi-step tasks that are not completed in a single request
• Work IQ gives Copilot context from work data, documents, and relationships within the organization

All of these elements require closer integration between the interface, platform, applications, and the models themselves. Therefore, the consolidation of teams looks not like a cosmetic reshuffle, but an attempt to prepare Copilot for the next phase of competition—where what matters is not only AI demonstrations but actual usefulness, manageability, and price for mass adoption. For Microsoft, this is also a way to more quickly turn research AI ideas into products that are equally understandable to a company employee and an ordinary user.

What This Means

Microsoft is transitioning Copilot from a mode of disparate features to a unified AI platform for work and personal tasks. If the company truly consolidates the product into a single, coherent experience and simultaneously strengthens its own model layer, Copilot will have more chances to become not just embedded AI in the Microsoft ecosystem, but a central interface for everyday work—both at home and in the office.