Originally reported by Petri.com. Original post date: August 7, 2020.
Overview: What Changed and Why It Matters
In August 2020, Microsoft executed a notable internal reorganization that reshuffled responsibilities across its Windows + Devices and Azure business units. Unlike the smaller round of layoffs the company made earlier that summer, this restructuring was not primarily a headcount reduction—it was a strategic realignment of teams, leadership roles, and product ownership.
The headline move: Microsoft brought parts of its Azure organization, specifically the COSINE team, into the Experiences and Devices (E+D) organization led by Panos Panay. The goal was to help Windows and Surface teams build more cohesive, end-to-end user experiences and to give the Surface hardware team stronger software and services alignment.
Key Leadership Changes in Windows + Devices
The most significant individual change was Michael Fortin joining Panos Panay’s Experiences and Devices organization. His expanded role combines services teams from COSINE and 365 Experiences and Services into a single new team.
Several COSINE team leads also moved into Panay’s org, including:
- Kevin Gallo
- Mark Alcazar
- Kristian Andaker
This move is particularly notable for developers: because Kevin Gallo was closely associated with Project Reunion (now known as the Windows App SDK), his transfer to the Windows org likely means Project Reunion moved under Windows leadership—widely considered a more natural home for the initiative than Azure.
Additional Windows + Devices org changes included:
- Jeff Johnson leading a newly formed Windows, Developer, and Experiences engineering team.
- Linda Averett joining Windows + Devices to lead a new Windows, Developers, and Experiences PM team.
Leadership positions that remained stable:
- Ralf Groene continuing to lead the Design Team.
- Stevie Bathiche continuing to lead the Applied Sciences Group.
- Robin Seiler now leading the Devices Portfolio and Operations (DPO) team.
Key Changes on the Azure Side
The reorganization was not limited to Windows. Azure also saw structural changes designed to consolidate infrastructure services and prepare for emerging markets.
New Azure Core Team
A new Azure Core team was formed by consolidating Compute, Networking, and Storage services under a single umbrella, spanning both PM and engineering. Girish Bablani was tapped to lead this team.
Azure Edge + Platform
The legacy COSINE team was reorganized by merging services from ASME, PIE, and the remaining COSINE components to create a new team: Azure Edge + Platform. Henry Sanders was appointed to a newly created role of CTO of Azure Edge + Platform.
Azure for Operators: 5G and Virtual Networking
A new Azure for Operators organization was established to pursue opportunities in 5G and virtual networking. This team brought together leadership from two recent Microsoft acquisitions:
- Anand Krishnamurthy, CEO of Affirmed Networks.
- Martin Lund, CEO of Metaswitch.
The formation of Azure for Operators signals Microsoft’s intention to compete in the carrier and telecommunications infrastructure market, an area where cloud vendors see significant growth potential.
Strategic Pillars for Windows + Devices
To understand the thinking behind the Windows + Devices reorganization, Microsoft articulated three strategic pillars guiding the org’s product decisions:
- Deliver iconic experiences across Microsoft, enabling both modern work and personal use cases.
- Grow the Windows and Surface business by delivering the best of Microsoft and creating end-user demand.
- Lead the industry through innovation and technology, enabling the partner ecosystem to thrive.
Context: Surface Business Momentum
The restructuring came on the heels of strong Surface hardware sales in Microsoft’s fiscal year 2020. One significant shift noted at the time: while Microsoft had historically maintained roughly a 50/50 split between consumer and commercial Surface sales, the end of FY20 saw that balance tilt heavily toward commercial customers—likely driven by enterprise remote-work purchasing during the COVID-19 pandemic.
The new organizational structure was designed to build on that commercial momentum by better integrating cloud services with the hardware and software experience.
What This Means for DevOps and Developer Teams
For engineering and DevOps teams that build on Microsoft’s platform, a few implications are worth watching:
- Project Reunion / Windows App SDK ownership moving to Windows leadership could accelerate delivery of a unified Windows development model, reducing fragmentation between Win32 and UWP application models.
- Azure Core consolidation of Compute, Networking, and Storage under a single leadership team may eventually improve cross-service consistency and integration for infrastructure teams.
- Azure for Operators signals a serious push into 5G and edge networking infrastructure, which is relevant to teams building latency-sensitive or distributed applications.
- New organizational boundaries always create transition periods—expect some turbulence in roadmap communication and team contacts while the new structure stabilizes.
All changes described above were reported as effective immediately as of the original publication date in August 2020. Given how quickly Microsoft’s organizational structure evolves, current team names and leadership assignments should be verified against up-to-date Microsoft sources.