GCC → Commercial Migration Context
Items marked with ⚡ carry elevated significance in this migration scenario — these touch data residency, compliance obligations, or feature/licensing differences between cloud environments. Flag these for deeper discussion during the session.
Microsoft 365 Services in Use
— / —
0%
▼
⚡Confirm which services are licensed and actively used in GCC today — some features (e.g. certain Purview capabilities, Copilot) differ between GCC and Commercial. This shapes the migration scope and any feature-gap remediation plan.
Service
Response / Status
Owner
Notes
Identity
— / —
0%
▼
⚡Identity is the highest-risk workstream in any T2T migration. UPN/domain changes, MFA re-enrollment, conditional access re-creation, and ADFS/hybrid auth cutover all require careful planning — especially when moving out of GCC where government-specific identity configurations may exist.
Question
Response
Owner
Notes
Exchange / Exchange Online
— / —
0%
▼
⚡Mail data is typically the highest-volume workstream. Legal hold, journaling, and archive data require special handling — understand compliance obligations before defining the migration approach and tooling (BitTitan, Quest, native IMAP, etc.).
Question
Response
Owner
Notes
Microsoft Teams
— / —
0%
▼
⚡Teams chat history migration between tenants requires third-party tooling (Quest ODM, AvePoint). Teams voice deployments with PSTN configurations — Direct Routing, calling plans, and SBC compatibility all need verification against the target tenant state.
Question
Response
Owner
Notes
OneDrive for Business
— / —
0%
▼
Question
Response
Owner
Notes
Power Platform
— / —
0%
▼
⚡Power Platform environments and solutions are tenant-bound. Apps, flows, and custom connectors need to be re-created or exported/imported to the target tenant. Validate connector availability and DLP policy differences before migration planning.
Question
Response
Owner
Notes
Infrastructure
— / —
0%
▼
⚡Data sovereignty requirements are the primary driver for restricted cloud use — moving tenants means those obligations are changing. Confirm with legal/compliance whether the move is approved and document any residual data handling requirements before scoping.
Question
Response
Owner
Notes
SSO Integrated Applications
— / —
0%
▼
⚡All Entra ID enterprise app registrations, SAML/OIDC configurations, and service principal trust relationships will need to be re-created in the target tenant. This is frequently underestimated — get a comprehensive app inventory early.
Application (Vendor / Product / Version)
Auth Type
Owner
Notes
Devices
— / —
0%
▼
⚡Hybrid Entra ID joined devices require re-joining to the target tenant — this is often the most disruptive end-user experience in a T2T migration. Intune/JAMF MDM profiles must be re-enrolled. Autopilot profiles are tenant-specific and need to be re-created or transferred.
Question
Response
Owner
Notes
Office 365 Security & Compliance
— / —
0%
▼
⚡Sensitivity labels, DLP policies, eDiscovery holds, and retention policies are all tenant-specific — they will NOT automatically transfer. If the customer has active legal holds or regulatory compliance requirements, this section needs special attention before any migration wave begins.
Question
Response
Owner
Notes
Discovery Session Summary
0
Questions Answered
0
Total Questions
0%
Coverage
Use Print / Save as PDF to capture this session for follow-up. All responses are retained in the page as long as it remains open.