Purview Integration during Merger and Acquisitions

arunsekaran​ Before deciding on a unified labelling approach, the first question is what the target tenant looks like:

• Are you consolidating into an existing tenant, or
• Migrating all organisations into a new tenant?

Sensitivity labels are tenant‑scoped, so labels that look identical across tenants are not the same technically.

I’d strongly recommend starting with an impact assessment, covering questions such as:

• Do any labels apply encryption, and if so, what are the encryption rules?
• Are labels applied manually, automatically, or both?
• What label policies exist (default labels, mandatory labelling, role‑specific policies)?
• Are container sensitivity labels used for Microsoft 365 Groups, Teams, or SharePoint sites?
• Are labels referenced in auto‑labelling, DLP, Insider Risk, retention, or other Purview controls?
• Are there custom SITs, scripts, or tools that depend on specific label GUIDs?
• Are labels enforced outside Microsoft 365 (for example via third‑party integrations)?

In an ideal scenario, you define the target labelling framework upfront, then map each source tenant’s labels to that target. If your migration tools support it, relabelling content during migration is the cleanest approach, particularly where one tenant already has large volumes of labelled data.

If content is migrated without relabelling, files may retain their original tenant’s label metadata, but users in the target tenant typically won’t be able to see or manage those labels, and label‑based policies won’t apply consistently.