Microsoft Entra ID
Validate the cloud identity target before changing the source.
Document tenant ownership, admin consent, target identity rules, mappings, synchronization assumptions, and rollback responsibilities before approving a hybrid move.
Current boundaryEntra connection setup and identity planning are supported within configured engagements. B2B guest, app registration, service principal, and Intune migration are Planned.
Readiness
Resolve identity ownership and consent first.
Cloud migration outcomes depend on target object preparation, domain and UPN decisions, synchronization architecture, API permissions, and licensing outside the migration tool itself.
- Target tenant, app registration, and consent validation
- Source-to-target identity mapping rules
- UPN, alias, collision, and naming decisions
- Hybrid synchronization ownership and sequencing
- Role and privileged-access operating model
- Dry-run assumptions and target validation
- Audit trail for operator and role changes
- Explicit planned-feature exclusions
Supported
Connection and planning
Configured Entra connection, identity mappings, target validation, and audit-backed planning.
Planned
Expansion workloads
B2B guests, service principals, app registrations, and Intune device/policy migration.
Controlled pilot
Execution boundary
Directory migration behavior is validated against topology, release, success criteria, and rollback plan.