> Markdown version of [/jobs/ext/4444400-m365-collaboration-architect](https://www.wearedevelopers.com/jobs/ext/4444400-m365-collaboration-architect). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# M365 Collaboration Architect

- **Company:** Randstad
- **Location:** Plano, TX, United States (Remote available)
- **Experience:** Experienced
- **Salary:** $156,000 - $208,000
- **Contract:** Contract
- **Skills:** Amazon Web Services, Microsoft Azure, Business Software, Identity and Access Management, Routing, Windows PowerShell, Microsoft SharePoint, Systems Integration, Microsoft Sharegate, Multi-Cloud
- **Published:** October 31, 2026
- **Apply:** https://www.dice.com/job-detail/905dcc2c-ae3f-484b-a76e-014149dab6ca

## About the Role

Our customer has an immediate need for a top-notch M365 Messaging/Collaboration Architect with excellent soft skills and consulting experience. This role will be client facing with some travel.

Remote with 15-25% travel within US. Must be able to work in US without sponsorship., 10+ years of M365 messaging & collaboration experience

2+ years of recent experience as an Architect, Technical Lead, SME, and/or Lead Consultant

Experience with design ownership on cross-tenant migrations into a large production tenant

Advanced to expert level technical skills with Quest On Demand Migration, PowerShell/Graph automation, Exchange hybrid and mail routing

Preferred Skills:

M&A integration experience

Purview

Multi Cloud or Azure to AWS migration experience

Teams telephony migration

ShareGate/BitTitan/AvePoint

Enterprise Administrator Expertise

Energy or heavy manufacturing/industrial experience

Consulting experience

Experience with SOX and other relevant compliance standards

skills:

AWS,Azure,ShareGate,Multi Cloud,routing,integration experience,PowerShell,soft skills,Collaboration,automation,consulting experience,heavy manufacturing,compliance standards,M&A,SOX

## Description

* 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.
 * 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,configuration & scripting to cutover execution
 * Lead a team of Engineers to deliver integrate IAM technologies and processes as part of complex acquisition integrations, often joining medium sized (typically private) companies into a publicly held enterprise environment (Fortune 200)
 * Typically leading 1 acquisition integration at a time, although that may vary based on size and scope
 * Own architecture through hands-on migration and cutover execution
 * Own the domain end to end, including discovery, architecture, planning, risk, team leadership and execution
 * Perform cutovers that may occur nights/weekends
 * 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 the program architects and the other domain leads
 * Planning and risk: estimate effort, set the sequence and the dependencies other domains rely on, and define rollback and go/no-go criteria
 * Leadership: direct a small team, coach the acquired company's IT staff, and work across security, compliance and application owners
 * Repeatability: turn each deal into reference designs and runbooks so the next integration starts from the last one, and re-plan integrations that are already underway