20,000 users, 50 countries, 4 weeks to Microsoft Teams with Chul-Young, Collaboration Product Manager at Parexel

Who should listen: Microsoft 365 service owners, collaboration product managers and UC leads in large enterprises who need to justify lean admin teams, set Teams governance and lifecycle policy, or build the business case for Teams Phone and retiring legacy meeting platforms.

Guest: Chul-Young — Product Manager, Collaboration Platforms & Services, Parexel

Chul-Young is IT Product Manager for Microsoft 365 and collaboration platforms at Parexel, a clinical research organisation with more than 20,000 staff across 50+ countries. He describes compressing an eight-month Teams deployment plan into four weeks at the start of the pandemic, the governance decisions behind self-service team creation, and cutting phone numbers from 20,000 to 3,000 during the move to Teams Phone.

Key insights

• A large consultancy proposed a 12-month Teams rollout; a second, independent consultant helped negotiate it down to eight months. Covid then compressed it further — the plan was blessed in February 2020, and Teams went live to 20,000 users across 50+ countries by early April. ▶ 2:50
• The entire Microsoft 365 platform for 20,000 users is administered by a two-person admin team, which forced a deliberate philosophy: roll out only what scales, avoiding customisations that generate maintenance load a year later. ▶ 5:44
• Standardisation extended to language — despite operating in 50+ countries with staff in Germany and elsewhere, everything was deployed in English only, because Parexel is US-headquartered and English-speaking. No German or French variants were built. ▶ 6:42
• Teams app management was simplified conceptually rather than technically: because every app-to-user permutation needs its own app policy, apps that pass third-party security review are enabled tenant-wide, with the business units funding and managing the underlying licences. ▶ 6:42
• Self-service team creation was granted to all users from day one — the argument being that an IT-managed request process would immediately need automation and customisation. Team numbers grew exponentially at first, then plateaued; a group expiration policy auto-deletes inactive teams, with sensitivity labelling still on the roadmap. ▶ 8:09
• On data ownership, the line used internally is a car manufacturer analogy: IT builds and hands over the car, the business decides what it carries and obeys the rules of the road. Teams content is business data, not IT data. ▶ 11:27
• Moving to Teams Phone was paired with cutting telephone numbers from 20,000 to 3,000 (the initial ambition was 1,500), which made the business case attractive. Pushback was limited — senior stakeholders volunteered to give up numbers they had not used in two years. ▶ 12:20
• The bigger ROI came from meetings, not voice: the legacy external meeting platform was decommissioned just three months after the April 2020 Teams rollout because adoption was already complete. ▶ 14:13
• With no change management team, adoption relies on a small SharePoint site with Parexel-specific detail that links out to Microsoft's own documentation, plus business-side champions who build and maintain their own materials — a deliberate divide-and-conquer approach for a one-person product function. ▶ 18:10
• Ownership is split: the two M365 admins cover the platform and accounts (not Azure), IT security owns security and compliance, and a separate unified communications group runs Teams Rooms and voice day to day. ▶ 22:42

Insights summarised by AI from the episode transcript, reviewed by the Empowering.Cloud team.

Listen: Apple Podcasts · Spotify · Other platforms