Professional Services: global Microsoft 365 Copilot rollout with platform consolidation

An international professional services firm with more than 350,000 employees across more than 130 countries was running into the limits of its own scale: outdated, fragmented platforms per country made it hard to move as one organization, while every country carried its own configuration and compliance requirements. The firm wanted to modernize how people worked together without maintaining custom code per country.

The organization rolled out Microsoft 365 with Copilot across the entire firm, migrating more than 15 petabytes of data and hundreds of thousands of mailboxes onto the new platform. Country-specific needs were met through configuration rather than custom code, which made management and compliance simpler. The migration ran in waves of at most a few tens of thousands of users at a time, executed over weekends so employees found a working environment on Monday. Copilot is embedded in the daily workflow: summaries and answers build on existing files and calendars. The firm also built its own agents in Copilot Studio for recurring work such as research, HR, and IT support, within the same security and compliance boundaries as the rest of the Microsoft 365 environment.

Country-specific custom code would require fresh maintenance with every legal change or local requirement, across a hundred-plus countries at once. Solving local differences through configuration instead of code kept a single platform manageable while still meeting local obligations.

A phased rollout per region with its own tooling per market could have started faster at the local level, but would have entrenched the fragmentation rather than resolved it. Sticking with the existing platforms and running separate AI pilots per department did not solve the underlying scale problem and would have led to inconsistent security across departments.

• One global platform simplifies management, but requires a large, coordinated migration effort before the benefits become visible.
• Country-specific configuration instead of custom code is easier to maintain, but limits how far a country can deviate from the shared model.
• Custom Copilot Studio agents speed up recurring work, but need a deliberate ecosystem around compliance and security so teams do not have to think about that separately themselves.

Microsoft 365 Enterprise, Microsoft 365 Copilot, Microsoft Copilot Studio.

• Solve country-specific requirements through configuration, not custom code that needs separate maintenance with every legal change.
• Migrate in manageable waves with a fixed maximum number of users per period, so support volume stays predictable.
• Build custom Copilot Studio agents within the existing security and compliance environment, instead of standing up a separate environment per agent.

The biggest sign of a successful rollout turned out not to be the absence of tickets, but the type of tickets: the large majority were "how do I do this" rather than "this is broken." That signaled the underlying migration was stable and that the remaining effort was mostly about user adoption, not technical problems.