Microsoft is changing the destination addresses for two of its most popular cloud services, and the shift affects the Teams and Copilot addresses that your network currently allows. Starting this month, Microsoft will redirect Microsoft 365 web users to copilot.cloud.microsoft and Teams web users to teams.cloud.microsoft, according to two Microsoft MessageCenter posts. IT admins need to update their firewalls, proxies, and secure web gateways before the switch disrupts web access.
The Teams change is already underway, and Microsoft has now added Microsoft 365 to the mix. Companies relying on these services should review their network controls to make sure the new addresses are permitted.
What’s changing with the Teams and Copilot addresses
Microsoft confirmed the redirect in two MessageCenter announcements, numbered MC1465764 and MC1462915. The first covers the Teams web address change, while the second covers the Microsoft 365 web redirect.
In practice, this means that when you open the Microsoft 365 web app or sign into Teams through a browser, the page will now point you to a new domain instead of the familiar office.com or teams.microsoft.com endpoints. The Teams redirect has already begun rolling out, and the Microsoft 365 portion is being layered on top of it.
Microsoft says all redirects should be finished by early October. Organizations that can’t meet that deadline can reach out to their account representative for help, and limited exceptions to the Teams redirect remain possible until December 31, 2026 — but no further delays will be allowed after that date.
Why Microsoft is making the change
Microsoft hasn’t spelled out a single headline reason for the move, but the new domains line up with its broader push to centralize Copilot and productivity services under a unified cloud identity. Routing Microsoft 365 web traffic to copilot.cloud.microsoft ties the productivity suite more closely to the Copilot experience the company has been promoting across its enterprise products.
The Teams redirect to teams.cloud.microsoft follows a similar pattern of consolidating services under purpose-built cloud domains. From an infrastructure standpoint, these addresses let Microsoft manage updates, security, and scaling more centrally without forcing customers to chase new endpoints with every release.
What you need to do
Microsoft is advising organizations to update their systems and documentation to ensure continued access. Specifically, admins should review configurations on client devices, proxies, firewalls, secure web gateways, and other enterprise network controls to confirm users can reach the new addresses.
If your environment is having trouble connecting, Microsoft says you should make sure it aligns with the recommended network requirements for Microsoft 365 Copilot. That document lays out the specific domains and ports that need to be open, so it’s worth pulling up before the October deadline.
There’s also a wrinkle for companies that were blocking the new Copilot address. Some enterprises had been blocking copilot.cloud.microsoft to stop employees from reaching their personal Microsoft accounts. Microsoft says those organizations can use its TenantRestrictions control to achieve the same goal without relying on a block, so you don’t need to keep a blunt block in place just to keep consumer accounts out.
What this means for you
For most home users, this change will be invisible — you’ll just be sent to a new-looking URL when you open Microsoft 365 or Teams in your browser, and it will work the same way. The catch is for businesses and schools that use network controls.
If your organization blocks traffic by domain name rather than by content, the old addresses will keep working while the new ones get cut off. That can leave users unable to open the web versions of Teams or Microsoft 365 until someone updates the allowlists. It’s the kind of change that quietly breaks productivity for a whole company if nobody’s watching the MessageCenter.
How to get ahead of the change
The good news is there’s nothing for you to install or upgrade. Microsoft is handling the redirect on its side, so your job is purely to make sure your network controls permit the new domains.
Check your MessageCenter posts for MC1465764 and MC1462915, add copilot.cloud.microsoft and teams.cloud.microsoft to your allowlists, and update any internal documentation or runbooks that list the old endpoints. If you’re unsure whether your setup will hold up, contact your Microsoft account representative before early October — and note that Teams exceptions expire entirely on December 31, 2026.
Why the deadline matters
Microsoft has drawn a hard line on the Teams redirect: limited exceptions are possible only until December 31, 2026, after which no further delays will be granted. That gives organizations a clear window to get their network controls in order, but it also means the Teams portion of the change can’t be pushed off indefinitely.
The Microsoft 365 redirect, meanwhile, is expected to be fully complete by early October. Companies that anticipate problems meeting that timeline should flag them to their account representative now rather than waiting until the deadline passes.
Source: Computerworld
Over to you: Has your organization already added copilot.cloud.microsoft and teams.cloud.microsoft to your firewall allowlists, or are you waiting until closer to the October deadline?
