M365 Collaboration Architect

M365 Collaboration Architect (Domain Lead)
Job Description · M&A Integration Program
Role Summary
Designs and delivers the move of each acquired company's email, Teams, SharePoint and OneDrive into a
large, established parent tenant in staged waves, while users split across two tenants keep collaborating.
Domain Responsibilities
• Discover the collaboration estate: mail routing, tenant policies, Teams/SharePoint/OneDrive footprint, file
shares and data volumes.
• Design mail routing, coexistence and the migration wave strategy.
• Identify where parent policies (retention, DLP, eDiscovery) change the user experience, and plan for it.
• Assess the impact on line-of-business applications, shared mailboxes, and dependencies on identity and
network.
• Stand up coexistence (B2B, cross-tenant sync, free/busy, Teams federation) before the first wave.
• Hands-on: Quest On Demand Migration, PowerShell/Graph automation, cutover execution.
Leadership & Delivery Responsibilities
• Own architecture: assess an environment that is usually poorly documented, design the target state against
the parent company's standards, and defend it in review with program architects and other domain leads.
• Own planning and risk: estimate effort, set the sequence and the dependencies other domains rely on, and
define rollback and go/no-go criteria.
• Lead: direct a small team, coach the acquired company's IT staff, and work across security, compliance and
application owners.
• Build repeatability: turn each deal into reference designs and runbooks so the next integration starts from the
last one, and re-plan integrations already underway.
Must Have
• 8+ years of M365, with design ownership on cross-tenant migrations into a large production tenant
• Exchange hybrid and mail routing
• Hands-on Quest On Demand Migration
• Purview
• PowerShell and Graph
Nice to Have
• Teams telephony migration
• ShareGate / BitTitan / AvePoint
• Enterprise Administrator Expert
Confidential - Not for Public Consumption or Distribution Page 3
Strong Plus
Prior M&A integration experience and work in field-heavy industries (construction, energy, utilities).
Confidential - Not for Public Consumption or Distribution Page 4
Engagement 12 months, integration work only (no ongoing operations)
Location Remote in the US (US persons only)
Schedule Cutovers often at night and on weekends
Reports to Integration Lead for the acquisition
Team Directs on-site engineers and field technicians
Travel Required for cutovers and site work