Project - Full Tenant Migration - Cloud-First Tenant & Azure Rebuild

Synopsis: Project engineer execution plan for rebuilding the CLIENT Microsoft 365 and Azure environment under the new naming, migrating users and data, and moving endpoints to Entra ID and Intune.

Published: November 15th, 2026
Last Modified: November 15th, 2026

Intro: This will hopefully become an indepth outline for migrating from an existing O365 tenant, to a new domain. Should be a point of reference for migrating just some, or all users.





Quick Run Down

    1.) Confirm scope, access, licensing, ownership, and change-control process.
    2.) Inventory the source tenant, Azure, applications, SSO, files, printers, endpoints, DNS, and VPN.
    3.) Confirm architecture decisions and document rollback criteria.
    4.) Build the target Microsoft 365 tenant, Entra ID, Intune, and Azure foundation.
    5.) Rebuild identity, Conditional Access, Enterprise Applications, and SSO integrations.
    6.) Stage mail, collaboration data, Azure Files, permissions, printing, and VPN changes.
    7.) Pilot the complete user and device migration process.
    8.) Cut over the custom domain, mail flow, and site-to-site VPN.
    9.) Migrate the remaining 25 endpoints in controlled waves.
    10.) Validate, stabilize, document, obtain sign-off, and decommission the old environment.

Initiation & Prerequisites

  1. Access confirmations:
    • Source O365 Tenant
    • Source Azure Subscription
    • Domain Registrar / DNS provider
    • Network Inf
  2. Provisioning
    Confirm the CSP process and provision a new Azure subscription under the target tenant.
  3. Confirm Microsoft 365, Intune, Entra ID P1/P2, Universal Print, Azure, and migration-tool licensing for the overlap period.
  4. Identify client application owners, SSO vendor contacts, printer owners, CAD test users, and cutover decision-makers.
  5. Schedule discovery, pilot, domain cutover, VPN cutover, endpoint waves, hypercare, and decommissioning windows.

Source Discovery & Baseline

Microsoft 365 & Entra ID

  • Export all users, aliases, shared mailboxes, groups, contacts, licenses, authentication methods, Conditional Access policies, named locations, app registrations, Enterprise Applications, service principals, API permissions, and provisioning connectors.
  • Inventory Exchange accepted domains, connectors, transport rules, mail-flow dependencies, DKIM, SPF, DMARC, and third-party systems that relay mail.
  • Inventory SharePoint sites, OneDrive accounts, Teams, channel structures, external sharing, retention settings, and total data/file counts.
  • Search for the former legacy name in UPNs, proxy addresses, SMTP aliases, SharePoint URLs, groups, application names, scripts, and documentation.

Azure & Network

  • Export every Azure subscription, resource group, resource, region, SKU, dependency, role assignment, lock, policy, diagnostic setting, private endpoint, DNS link, route, public IP, and backup configuration.
  • Capture the existing VNet/subnet ranges, office WAN addresses, local network gateways, VPN settings, routes, pre-shared-key ownership, and firewall rules.
  • Baseline Azure Files capacity, file count, share layout, share-level roles, NTFS ACLs, IOPS, throughput, latency, backup retention, and current CAD/AutoCAD performance.
  • Confirm the disposable ItchTemp NIC/NSG and the unused secondary subscription before marking either for deletion.

Endpoints, Applications & Printing

  • Create the 25-device tracker from RMM, Intune, Entra ID, and security tooling. Include assigned user, model, Windows build, disk space, BitLocker state, profile path, applications, certificates, VPN client, and readiness.
  • Inventory every SaaS, line-of-business, CAD, server-hosted, service-account, SAML/OIDC, SCIM, API, certificate, and hard-coded domain dependency.
  • Inventory printers and plotters, including model, IP, driver, queue, trays, finishing, secure release, monthly volume, and Universal Print compatibility.

Architecture Decisions & Detailed Design

  1. Confirm the final naming standard for tenant objects, resource groups, VNet, gateway, storage, private endpoints, vaults, policies, and endpoint profiles.
  2. Confirm whether the existing VNet/subnet ranges will be reused. Reuse is preferred unless overlap or design defects require renumbering.
  3. Confirm that cloud-only Entra Kerberos with granular Azure Files ACL management is supported for the tenant and region. Document Entra Domain Services as the fallback.
  4. Confirm Premium Azure Files, SMB Multichannel, private endpoint, private DNS, retained site-to-site VPN, and backup design.
  5. Define the CAD benchmark: representative files, open/save/xref operations, test device, test user, current baseline, and acceptable target.
  6. Select mailbox, OneDrive, SharePoint, and Teams migration tooling. Document unsupported data, export-only items, throttling expectations, and license count.
  7. Decide whether VPN tunnels can run in parallel or require a hard switch to the new Azure gateway public IP.
  8. Choose Universal Print, direct-IP printing for plotters, and any connector host. Record any need for PrinterLogic, Tricerat, or a print-server VM as a scope decision.
  9. Produce the identity map, group map, ACL map, resource disposition list, DNS cutover plan, endpoint wave plan, rollback plan, and validation matrix.

Build Target Tenant & Azure Foundation

Microsoft 365 / Entra / Intune

  1. Provision the new tenant and record the tenant ID, primary onmicrosoft.com domain, break-glass accounts, and administrative ownership.
  2. Apply approved branding, security defaults/baselines, privileged-role assignment, audit settings, and emergency-access controls.
  3. Add the custom domain in an uncut state and prepare DNS verification and cutover records without disrupting the source tenant.
  4. Configure Intune enrollment restrictions, compliance, Windows configuration, update rings, BitLocker, Defender/security settings, Windows Hello, OneDrive, Microsoft 365 Apps, cloud Kerberos ticket retrieval, and Universal Print policies.
  5. Create pilot and production groups for users, devices, applications, printers, file access, endpoint waves, and policy targeting.

Azure

  1. Create the approved resource groups and apply tags, RBAC, policy, diagnostics, budgets, and resource locks.
  2. Create CLIENT-VNet and subnets using the approved addressing; create the new VPN gateway, public IP, local network gateways, and connections.
  3. Create the Premium Azure Files storage account, file shares, private endpoint, private DNS zone/link, SMB settings, and diagnostic logging.
  4. Enable Entra Kerberos for Azure Files and create the approved share-level RBAC assignments. Exclude only the required storage application from MFA, with the exception narrowly scoped and documented.
  5. Create the Recovery Services vault or approved backup service, define policies, enable protection, and perform a test restore before production use.

Printing

  1. Build or designate the Universal Print connector host, install current printer drivers, register supported printers, share them, and assign access groups.
  2. Create Intune printer deployment policies. Keep plotters on the approved direct-IP or vendor-supported path.

Identity, Applications & Coexistence

  1. Create cloud-only target users and groups from the approved maps. Assign temporary UPNs until the custom domain moves.
  2. Assign licenses and validate service provisioning for Exchange Online, SharePoint, OneDrive, Teams, Intune, Universal Print, and required Entra features.
  3. Rebuild Conditional Access, named locations, authentication-strength requirements, MFA registration, break-glass exclusions, and session controls. Test policies in report-only or controlled pilot scope first.
  4. Recreate every Enterprise Application and app registration. Update SAML metadata, entity IDs, reply URLs, redirect URIs, certificates, secrets, API permissions, admin consent, and SCIM provisioning.
  5. Coordinate vendor-side SSO changes and record vendor ticket numbers, owners, completion dates, and test results.
  6. Configure cross-tenant mail coexistence, migration endpoints, identity mappings, free/busy if required, and source/target routing.
  7. Test pilot sign-in, MFA, license activation, mailbox access, collaboration, SSO, provisioning, and file-access authentication.

Data, Azure Files & VPN Staging

  1. Take pre-migration backups or exports required by the rollback plan.
  2. Pre-stage Exchange mailboxes, OneDrive, SharePoint, and supported Teams data. Record initial and delta migration statistics and all skipped/error items.
  3. Create the target Azure Files folder structure and Entra groups. Copy file data with AzCopy using logging, checksums where available, and repeatable delta commands.
  4. Translate source identities to target Entra groups. Prepare directory/file ACL assignments using the Azure portal or RestSetAcls; do not rely on copied old SIDs.
  5. Prepare on-premises DNS conditional forwarding/resolution for the Azure Files private endpoint.
  6. Build the new VPN configuration on Azure and stage the office firewall changes. Save current firewall configuration and a tested rollback procedure.
  7. Run pilot connectivity tests from the office for private DNS resolution, TCP 445, SMB authentication, share access, and effective permissions.
  8. Run repeated deltas until the remaining change volume fits the approved final-freeze window.

Pilot Migration

  1. Select 2-3 representative devices, including at least one CAD/AutoCAD user and one user requiring printing and SSO applications.
  2. Confirm each pilot device has a current backup, local administrator access, BitLocker key, available disk space, application inventory, and user-approved window.
  3. Remove old-tenant registration/MDM enrollment and disjoin the old domain where applicable.
  4. Join the device to the target Entra tenant and enroll it in target Intune.
  5. Remap the existing local profile to the new Entra account using ForensiT Profile Wizard or the approved profile migration method.
  6. Verify Intune policy receipt, compliance, BitLocker key escrow, Windows Hello, Microsoft 365 activation, OneDrive Known Folder Move, Teams, and browser SSO.
  7. Map the new Azure Files path and validate share RBAC plus granular folder permissions.
  8. Deploy Universal Print printers and direct-IP plotters as designed.
  9. Reauthenticate each application and test SSO, certificates, plug-ins, templates, mapped resources, and line-of-business functions.
  10. Run the defined CAD benchmark against the current baseline and document latency, open/save times, xref behavior, and user acceptance.
  11. Monitor the pilot through the agreed burn-in period and correct the runbook before authorizing broad migration.

Domain, Mail & VPN Cutover

  1. Start the change bridge, record baseline health, confirm approvals, and initiate the content freeze.
  2. Run final mailbox, OneDrive, SharePoint, Teams, and Azure Files deltas. Save completion and exception reports.
  3. Remove all dependencies preventing the custom domain from being released by the source tenant.
  4. Remove the custom domain from the source tenant, verify/add it to the target tenant, and update target UPNs and primary SMTP addresses.
  5. Update MX, Autodiscover, SPF, DKIM, DMARC, verification, and any relay/application DNS records according to the approved sheet.
  6. Validate inbound, outbound, internal, external, mobile, shared-mailbox, distribution-list, and application-generated mail.
  7. Apply the office firewall configuration for the new Azure VPN gateway and pre-shared key. Validate tunnel status, routes, private DNS, Azure Files reachability, and failback criteria.
  8. Run the cutover validation matrix. If a critical success check fails and cannot be resolved within the agreed threshold, execute the documented rollback.
  9. Communicate cutover status and release the endpoint migration waves only after go-live approval.

Endpoint Migration Waves

    Migrating workstations should be the final implementation. Data & Printers need to be migrated prior as device based authentication will no longer work across SMB.

    Authentication can be setup using Cloud Kerebos. This is new to me personally, but I plan to add some internal notes here if Entra AD devices will required SMB access.

ACL Finalization, Validation & Stabilization

  1. Apply final directory/file ACLs to Azure Files against target Entra groups by using the Azure portal or RestSetAcls.
  2. Validate effective access with representative read-only, contributor, elevated, restricted, and denied users.
  3. Run a complete validation pass for mail, OneDrive, SharePoint, Teams, SSO, SCIM, applications, Azure Files, CAD performance, printers, plotters, Intune, BitLocker, backups, VPN, DNS, monitoring, and alerting.
  4. Reconcile source and target item counts, migration reports, skipped items, and client-accepted exceptions.
  5. Monitor storage capacity/performance, VPN health, authentication failures, mail queues, Intune compliance, and Service Desk volume through the stabilization period.
  6. Rotate temporary passwords, migration credentials, app secrets, certificates, storage service-principal credentials, and pre-shared keys where required.
  7. Prepare as-built diagrams, credential/ownership records, operating procedures, asset lists, backup/restore instructions, and known-issue documentation.

Decommissioning

  1. Confirm the stabilization period is complete and obtain written decommission approval.
  2. Export any required audit, configuration, billing, legal, or retention records from the source tenant and Azure subscriptions.
  3. Disable and then remove old mail routing, coexistence, migration endpoints, connectors, applications, and stale identities according to the approved sequence.
  4. Retire the old VPN gateway and obsolete firewall configuration only after the new tunnel is proven stable.
  5. Retire the old print-server role after all supported printers are confirmed on Universal Print or their approved alternative.
  6. Demote and decommission the old domain controller. Remove dependencies, DNS references, monitoring, backup jobs, and associated NIC/public IP resources.
  7. Remove old Azure resources and the unused secondary subscription. Retain the old backup vault until its required retention window expires.
  8. Confirm no legacy-named resources remain within the agreed scope. Record any unavoidable historical references or excluded systems.
  9. Close changes, hand off documentation, capture final sign-off, and complete the project closure notes.

Engineer Validation Checklist

  • New user UPN and primary SMTP address work.
  • Inbound/outbound mail, shared mailboxes, aliases, lists, relay, SPF, DKIM, and DMARC pass.
  • OneDrive, SharePoint, Teams, and approved migrated content are accessible.
  • Conditional Access and MFA work without blocking break-glass or required service flows.
  • All Enterprise Applications, app registrations, SAML/OIDC, SCIM, certificates, secrets, and consent are tested.
  • Site-to-site VPN, routing, private DNS, TCP 445, and Azure Files access are stable.
  • Share-level Azure RBAC and folder-level ACLs produce the intended effective access.
  • CAD/AutoCAD benchmark is accepted; fallback decision is documented if performance is not acceptable.
  • Universal Print works for supported printers; plotters use the approved alternative.
  • All devices are target Entra-joined, Intune-compliant, and have target BitLocker keys.
  • Backups are running and a target-side restore has been tested.
  • Monitoring, alerting, documentation, operational ownership, and client sign-off are complete.

Troubleshooting Tips

  • None. You're on your own, Fellow AI Person.

Newest Post