Microsoft is reshaping how it organizes its workplace software, and the latest move puts Ryan Roslansky—best known as the CEO of LinkedIn—closer to the center of Microsoft’s productivity stack. According to reporting from The Verge, the Microsoft Teams organization is moving to report to Roslansky as part of a broader internal leadership reshuffle. The change also comes with a new mandate: Roslansky will lead a newly formed “Work Experiences Group” at Microsoft, consolidating responsibility for key parts of the company’s work and collaboration ecosystem.
At first glance, this may sound like another corporate reorg. But when you look at what Microsoft is trying to build—Office, Teams, Microsoft 365, and Copilot as a unified “work” platform—the reporting line shift is more than administrative. It signals that Microsoft wants fewer seams between products that customers already experience as one integrated system. And it suggests that the company is actively designing its org chart around the way people actually work: in documents, meetings, chats, shared files, and AI-assisted workflows that span multiple apps rather than living neatly inside one product boundary.
To understand why this matters, it helps to trace the roles involved.
Roslansky’s expanded remit: from Office to the broader work layer
Roslansky took on an expanded role at Microsoft last year, after serving as LinkedIn’s CEO. He was named head of Office, which placed him in charge of one of Microsoft’s most important franchises: Word, Excel, PowerPoint, Outlook, and the broader Office experience that underpins Microsoft 365. That appointment was notable because it brought a leader associated with professional networks and enterprise identity into the heart of Microsoft’s productivity suite.
Now, the next step appears to be extending that influence beyond Office itself. The Verge reports that the Microsoft Teams organization is moving to report to Roslansky. In practical terms, that means Teams—Microsoft’s flagship collaboration and meeting platform—would sit under the same executive umbrella as Office. For customers, this is significant because Teams and Office are already deeply intertwined. Meetings generate recordings and transcripts that feed into shared knowledge. Chat and channels connect to files stored in SharePoint and OneDrive. Work happens across apps, and Microsoft has been pushing toward experiences where the “context” of a conversation can flow into documents and vice versa.
When those products are managed by different leaders, the incentives can drift. Each team optimizes for its own roadmap, its own metrics, and its own definition of success. When they’re aligned under one leader, the company can more aggressively pursue cross-product integration—especially integration that depends on consistent product strategy, shared design principles, and coordinated rollout timing.
A new “Work Experiences Group”: the organizational bet
The reporting also says Roslansky will lead a new “Work Experiences Group.” The name is telling. Microsoft has long used groupings like “experiences and devices,” but “work experiences” is narrower and more specific. It implies a focus on the day-to-day tools people use to do their jobs—tools that combine communication, content creation, collaboration, and increasingly, AI assistance.
This is where the reorg becomes more than a reshuffle of titles. Microsoft’s workplace strategy has been evolving toward a model where Copilot isn’t just an add-on feature inside one app. Instead, Copilot is meant to become a layer that understands the user’s work context—emails, documents, meetings, chats, and tasks—and then helps them act. That kind of cross-app intelligence requires coordination across the teams that build the underlying experiences.
If Roslansky is now leading a group explicitly framed around “work experiences,” it suggests Microsoft is trying to treat Office and Teams not as separate products competing for attention, but as components of a single work platform. That platform needs consistent UX patterns, shared data and permissions models, and a coherent approach to AI features—especially those that rely on understanding organizational context.
The catalyst: Rajesh Jha’s retirement and the reshuffle ripple effect
This change is part of a broader reshuffle triggered by Rajesh Jha’s retirement. Jha, an executive vice president in Microsoft’s experiences and devices group, had responsibilities spanning multiple major areas: Windows, Office, Copilot, and Microsoft 365. In other words, he wasn’t just overseeing one product line—he was effectively managing a large portion of the company’s “work and productivity” surface area, plus the operating system foundation that many enterprise workflows depend on.
When a leader with that breadth exits, Microsoft has to decide what to do with the responsibilities. Sometimes companies split them across multiple executives; sometimes they consolidate them to reduce friction. In this case, the reporting indicates that Microsoft is consolidating parts of the work experience layer under Roslansky, while the rest of the experiences and devices portfolio is being reorganized around the retirement.
That matters because it frames the Teams reporting change as a deliberate response to a leadership gap—not merely a random adjustment. Microsoft is likely trying to preserve continuity in the roadmap for Office and Microsoft 365 while also ensuring that Teams is tightly aligned with the same strategic direction.
Why Teams reporting to Office leadership is a big deal (even if it sounds small)
Teams is often described as a communications tool, but in Microsoft’s ecosystem it functions as a hub for work. It’s where meetings happen, where teams coordinate, where decisions get documented, and where knowledge accumulates through recordings, transcripts, and shared artifacts. Office is where the output of that work becomes tangible: drafts, spreadsheets, presentations, and final documents.
Microsoft’s long-term challenge has been to make the transition between “talking” and “doing” feel seamless. People don’t want to copy-paste notes into documents. They want the meeting context to carry forward into the work product. They want the action items to become tasks. They want the decisions to become structured outputs. They want AI to help them summarize, draft, and refine without forcing them to switch mental modes every time they move from Teams to Office.
Those goals require product alignment. If Teams and Office are led separately, integration can still happen—but it tends to be incremental and sometimes uneven. A reorg that places Teams under the same leader as Office increases the odds that Microsoft will treat integration as a first-class priority rather than a series of cross-team compromises.
There’s also a competitive angle. Microsoft’s workplace suite competes not only with other enterprise software vendors, but with the reality that many organizations already use multiple tools for collaboration and productivity. The more Microsoft can make Teams and Office feel like one coherent environment, the harder it becomes for customers to justify switching away from the Microsoft stack.
The unique take: Microsoft is reorganizing around “workflow gravity”
One way to interpret this reshuffle is through the concept of “workflow gravity.” In modern work environments, the tools that attract the most activity become the gravitational center for everything else. In Microsoft’s case, Teams is often that center for communication and coordination, while Office is the center for creation and formal documentation.
By aligning leadership, Microsoft is likely trying to reduce the friction between these centers. Instead of treating Teams as a place where conversations happen and Office as a place where documents happen, Microsoft wants a model where the workflow moves naturally between them. That’s especially important as AI features become more capable. AI doesn’t just answer questions—it can draft content, summarize discussions, extract action items, and propose next steps. Those actions need to land in the right place: a document, a spreadsheet, a task list, or a shared plan.
If Microsoft is serious about making Copilot a consistent assistant across the workday, then the organizational structure should reflect that. A “Work Experiences Group” led by someone responsible for Office and now overseeing Teams is a structural move toward that consistency.
What could change for customers and enterprises?
It’s important to be careful here: a reporting line change doesn’t automatically alter product features overnight. But it can influence how quickly certain initiatives move, how resources are allocated, and how priorities are set.
Here are the most plausible areas where customers could feel the impact over time:
1) More coherent AI experiences across Teams and Office
Copilot features often depend on context—what was discussed, what documents are relevant, what the user is trying to accomplish. When Teams and Office are under one leadership umbrella, Microsoft can more aggressively unify the AI experience so that users don’t feel like they’re using separate assistants in separate apps.
2) Faster integration of meeting outputs into documents and plans
Teams meetings generate artifacts: transcripts, summaries, recordings, and notes. Office is where those artifacts become deliverables. With tighter leadership alignment, Microsoft may push more automation that turns meeting context into drafts, action item lists, and structured documents.
3) Consistent governance and permissions behavior
Enterprise customers care deeply about compliance, data boundaries, and permissions. When multiple products share the same underlying data and security model, inconsistent behavior can create friction. Consolidated leadership can help standardize how features behave across the suite, particularly for AI-driven capabilities that touch sensitive information.
4) A clearer product narrative for Microsoft 365
Microsoft 365 is already marketed as a unified suite, but internally it has historically been built by teams with distinct product cultures. A “Work Experiences Group” can help sharpen the narrative and reduce internal competition for roadmap ownership.
The broader reshuffle: what it signals about Microsoft’s priorities
The retirement of Rajesh Jha is a reminder that Microsoft’s leadership structure is still evolving as the company navigates the post-2020 era of workplace software. The company has been transitioning from a world where productivity apps were primarily productivity tools to a world where they are also AI platforms.
Windows, Office, Copilot, and Microsoft 365 are all part of that transition. Even though this particular report focuses on Teams and Office leadership, it’s happening in the context of a larger reorganization across experiences and devices. That suggests Microsoft is trying to align the entire stack—from the OS layer to the productivity layer to the AI layer—under a more coherent strategy.
In other words, this isn