Microsoft 365 Kept Running Through Every Stage of Your Office Move

The most common changes required during an office relocation: Named Locations in Entra ID need the new office IP range added before move day; conditional access policies that reference those Named Locations need to be updated so users are not blocked or hit with unexpected MFA challenges at the new site; Intune Wi-Fi configuration profiles need to reference the correct SSID and credentials for the new network; Teams Rooms need to be decommissioned from the old rooms and recommissioned in the new ones; and if the phone system is changing, Exchange Online and Teams Direct Routing configuration may need updating. Where Defender for Endpoint uses network boundary definitions, those need reviewing too.

If your conditional access policies use Named Locations for IP-based trust and you do not update them before the move, users connecting from the new office IP will not match any trusted location. Depending on how the policies are configured, they may be blocked entirely, forced through additional MFA steps that were not required at the old office, or denied access to specific applications. In a compliant device policy with strict location requirements, this can prevent access to Microsoft 365 services from the new site until the Named Location is updated.

The sequence matters. Teams Rooms devices need to be signed out and decommissioned from the old room resource accounts before they are physically moved. At the new site, they get recommissioned against the correct room accounts, reconfigured for the new display layout and peripheral setup, and tested end to end — audio, video, calendar integration, and room finder visibility in Teams. Where the room configuration changes (different screen count, new touch panel, different codec), we update the Teams Rooms configuration profile to match. We also test from an external meeting participant's perspective, not just the room console.

Intune is cloud-hosted, so the platform itself is unaffected. But the configuration profiles it pushes down to devices often are affected. Wi-Fi configuration profiles that reference the old SSID will push the wrong credentials to devices at the new site. Compliance policies that check for trusted network conditions may evaluate differently from the new IP range. Device configuration profiles sometimes reference location-specific settings. IronSights reviews all Intune policies for location-dependent settings before the move and prepares the updated profiles so they are ready to push when the cutover happens.

Yes. Where a relocation involves a phone system change — a new SIP trunk provider, a new number range, or a migration from an on-premises PBX to Teams calling — IronSights manages the Exchange Online and Teams configuration alongside the physical move. That includes Direct Routing configuration, calling plan setup, emergency location registration, and number porting coordination where required.