Microsoft 365 and Active Directory Consolidation Readiness
A fixed-scope, 1-2 week review that tells you exactly how to merge tenants and domains: approach, sequence, risks, and cutover plan.
- Timeline
- 1-2 weeks
- Format
- Remote
- Fee
- Fixed fee, agreed before we start
- Best for
- Organizations running two or more Microsoft 365 tenants or Active Directory forests after an acquisition or reorganization
Two tenants, two domains, and users who can't find each other's calendars. Merging Microsoft 365 and Active Directory is routine until it isn't: mailbox moves, SharePoint permissions, conditional access, and line-of-business apps tied to old identities. This review tells you how to do it before anyone touches production.
What you get
- Current-state inventory: tenants, forests, domains, trusts, licensing, mailboxes, SharePoint and Teams sites, and apps that depend on each identity.
- Target design: one tenant and one identity model, including Entra ID, conditional access, and device management.
- Migration approach: tenant-to-tenant method and tooling options, with the trade-offs for your size and timeline.
- Cutover plan: sequence, pilot groups, rollback points, and what users will see on the day.
- Risk list: the specific items most likely to cause downtime or support tickets in your environment, with mitigations.
How it works
- Kickoff: scope and read-only admin access.
- Assessment (week 1): configuration review and interviews with your IT team.
- Plan (week 2): target design, cutover plan, and a readout with your team.
The plan is yours to run in-house, or we can lead the migration as a separate engagement.