Network teams have a short window to catch up with two Microsoft redirects, or users will start losing access to Copilot and Teams in the browser.
M365 web users are headed to copilot.cloud.microsoft. Teams web users go to teams.cloud.microsoft. Both changes were announced in Message Center posts MC1465764 and MC1462915.
The Teams shift is already running, and M365 has now joined it. Administrators should walk through client device settings, proxies, firewalls, secure web gateways, and other network controls to confirm users can still reach the new destinations. Microsoft points failing connections to its recommended network requirements for Microsoft 365 Copilot.
Every redirect is meant to land by early October, and Microsoft’s advice for anyone who misses that window is to reach out to their account team. Exceptions apply to the Teams move, but only until December 31, 2026. Past that point, no more slippage.
Anyone who deliberately blocked the new Copilot address to keep staff out of personal Microsoft accounts has a cleaner option. Microsoft points to its TenantRestrictions control, which reaches the same outcome without a blanket block.
Treat it as a change window. Add the new domains to allowlists, test from a managed endpoint, and pull the old exceptions only after traffic has moved rather than blocking one side too early.
