Compliance Center

The Microsoft 365 Compliance Center is the legacy name for what is now the Microsoft Purview portal (purview.microsoft.com). It's where administrators configure data governance and compliance features across Microsoft 365: sensitivity labels, retention policies, data loss prevention (DLP), eDiscovery cases, audit search, insider risk management, and communication compliance. The rebrand to Purview happened in 2022 as Microsoft consolidated its data-governance products under a single brand, but you'll still see "Compliance Center" in older docs and screenshots. The corresponding admin role is "Compliance Administrator," which gates access to most of the configuration in this portal.

Worked example

A compliance officer who learned the platform under its old name searches internal documentation for "how to create a retention policy in the Compliance Center" and finds a screenshot showing a navigation menu that no longer exists anywhere in the current tenant — the steps are still broadly correct, but every screenshot and menu label needs mentally translating to the current Purview portal layout. The underlying policy object being created (a retention policy, applied the same way) hasn't changed at all; only the portal wrapped around it has a new name and a refreshed navigation.

Common pitfalls

Assuming outdated internal runbooks and training material referencing "Compliance Center" are wrong or dangerous to follow is usually an overreaction — the concepts and policy objects underneath (retention, DLP, labels) are unchanged, and only the portal name and some navigation paths need updating, not the underlying logic. Searching for "Compliance Administrator" role documentation and finding results split across both old and new branding can make role-based access control look more complicated than it is — it's the same role, just described inconsistently across older and newer material. And forgetting that "Compliance Center" is still the term many long-tenured staff and even some third-party tools use in conversation is worth keeping in mind when writing internal documentation for a mixed audience of new and long-time admins.