All work
Case study

New Teams migration for education tenants

Moving 70 million students and educators from classic Teams to a rebuilt client during the school year, with the first 40 million on the new client by January 3, 2024.

Period
2023 to 2024
Organization
Microsoft Education Engineering, Customer Engagement team
My role
Program manager (vendor)

Context

Microsoft rebuilt the Teams client from the ground up. Education tenants had to move from classic Teams to the new client in the middle of an active school year. I worked on the Microsoft Education Engineering side as a program manager on the Customer Engagement team.

The problem

The first critical batch, 40 million students and educators, had to be on the new client by January 3, 2024. The remaining users followed later, 70 million in total. Education tenants behave differently from commercial ones: people search is scoped, address book policies are common, supervised chat is in play, and class teams exist at a scale few commercial tenants reach. Issues surfaced that commercial testing did not catch, and every one of them risked the trust schools had placed in Teams since 2020.

What I did

  • Identified and escalated the education-specific blockers: people search, address book policy configurations, and tenant behaviours unique to schools.
  • Ran the daily analysis of customer feedback and presented it to leadership as concrete priorities, so decisions were made on evidence from real tenants.
  • Partnered with engineering teams to validate fixes with pilot customers before wide release.
  • Communicated timelines, compatibility, risks and expectations to education customers, clearly and early.
  • Over roughly three months, identified and drove resolution of more than 100 blocking bugs across multiple Microsoft engineering teams.

What the team and the product did

The migration was a cross-organization effort spanning Teams core engineering, Education Engineering and support. Engineering fixed the bugs and the product teams shipped the client. My part was the education customer feedback loop and the escalation path from customers to the people who could act.

Scale and outcome

  • 40 million students and educators on the new client by January 3, 2024; 70 million in total when the migration completed.
  • Migration completed on schedule with no major customer trust incident.
  • Leadership acted on daily customer evidence, which is what let the teams ship with both speed and quality.

What it means for a district

When a platform your schools depend on is rebuilt, ask three questions early: which tenant-specific configurations (people search, address book policies, supervised chat) have been tested on tenants like yours, who your escalation path is, and how your feedback reaches the product team before wide release. The districts that did best in this migration had those answers before the deadline, not after.

Evidence

Last reviewed October 27, 2026.