Tenant-to-tenant readiness
Plan the identity move before promising the content move.
BridgeAD can structure tenant readiness, identity mapping, delivery decisions, and audit evidence. Microsoft 365 content-transfer connectors are not currently generally available.
Current delivery boundaryExchange, SharePoint, OneDrive, and Teams are assessment/planning scope. Production item, file, and message transfer remains Planned.
Assessment focus
Make native prerequisites and third-party scope explicit.
The output documents what BridgeAD coordinates, what Microsoft-native tooling performs, what requires another validated connector, and what remains outside scope.
- Source and target tenant ownership and admin consent
- Identity source, synchronization, and target object preparation
- Domains, UPNs, aliases, and coexistence assumptions
- Mailbox, site, drive, team, and permission inventory
- Licensing and Microsoft workload prerequisites
- Protected API and tenant eligibility dependencies
- Cutover, rollback, support, and validation owners
- Explicit content-transfer tool and evidence boundary
| Workstream | BridgeAD status | How to position it now |
|---|---|---|
| Directory and identity discovery | Supported | Use for configured AD/Entra connection and identity planning scope. |
| Exchange orchestration framework | Limited | Assessment and planning only; not item-level mailbox transfer. |
| SharePoint and OneDrive framework | Limited | Discovery and planning only; not production content copy. |
| Teams structure planning | Limited | Tenant readiness planning; not message migration. |
| Production M365 content transfer | Planned | Exclude unless a separate, validated delivery tool and statement of work is agreed. |
Get an honest source-to-destination plan.
The assessment identifies tooling and ownership per workload instead of forcing one product claim across the program.