Tenant merge / M&A
Two organisations, two licensing philosophies: CHAOS reconciles signals and SKU mix and produces defensible target scenarios with a rationale trail.
Problem
After a merger announcement you run two Entra / Microsoft 365 worlds: different bundle habits (E3/E5 vs Business), different add-on stacks (Defender, Purview, Power BI) and duplicate accounts with diverging mailbox and Teams profiles. Finance sees double cost, IT fears cutover risk, audit asks for a credible target ELP. Spreadsheet inventories diverge quickly; dynamic groups make manual mapping painful. Without a shared method, political fights erupt about who keeps which expensive bundle.
Approach with CHAOS
CHAOS connects both tenants (or source/target phases), normalises accounts, groups, assignments and usage signals. The rule engine compares multiple compliant target paths (downgrade, bundle change, add-on removal) and documents rejected alternatives in the Why-layer. Sensitive groups get test cases and approvals; evidence packs summarise KPIs for tax, legal and CIO. Technical migration stays in your runbook—CHAOS supplies the licensing truth and scenarios.
Outcome from CHAOS
You get consolidated before/after KPIs, an explainable target SKU mix, a prioritised list of quick wins vs structural changes, and exports that hold up in steering committees and with Microsoft. Decisions shorten because IT and finance see the same rules and simulations.
Insight
Merge projects rarely fail on tenant-move mechanics—they fail on missing shared licensing truth before cutover. Involve finance, privacy and HR early and validate rules on a test tenant to avoid expensive rework and true-up disputes.