Ryan Roslansky to Leave Microsoft: LinkedIn and Microsoft 365 Reporting Changes

Who reports to whom​

Nadella announced these arrangements:

• Sumit Chauhan and Lan Ye will report to Charles Lamanna.
• Jon Friedman will report to Jacob Andreou.
• Dan Shapero remains LinkedIn CEO, and Mohak Shroff retains his role; both report to Nadella.

Microsoft did not name a single successor covering Roslansky’s entire portfolio. Shapero’s continuation is not a new CEO appointment.

Roslansky’s explanation is personal: he believes the next phase requires his full-time presence in Redmond, while his family’s life remains in the Bay Area. That statement does not establish a company-wide attendance policy.

Why Microsoft 365 and Copilot readers should care​

Microsoft’s March 17, 2026, Copilot leadership announcement supplies important context. Nadella then assigned Roslansky, Perry Clarke, and Charles Lamanna to lead Microsoft 365 apps and the Copilot platform. Jacob Andreou was assigned the consumer and commercial Copilot experience, including design, product, growth, and engineering.

That earlier structure organized Microsoft’s unified Copilot effort around four connected areas: the user experience, platform, Microsoft 365 apps, and AI models. The October reporting changes therefore involve leaders already central to that integration effort—not an unrelated management shuffle. This is an interpretation of the two announcements, rather than a newly disclosed product roadmap.

Nadella describes the direction as a “new OS for work,” with Office and Copilot increasingly integrated. That is strategic language, not a Windows replacement announcement.

An organizational change, not an admin task​

The October announcement specifies no licensing changes, migration requirements, feature availability dates, or administrator actions. It also does not explain how Roslansky’s remaining responsibilities will be allocated.

For IT teams, the useful distinction is between leadership accountability and shipping commitments. Reporting lines help explain who is steering the work; they do not, by themselves, establish what a tenant will receive or when. Treat this as a leadership transition to follow—not a reason to alter a Microsoft 365 deployment.