Microsoft is moving Teams and Microsoft 365 to new web addresses, here is what your IT team needs to do
Both services are redirecting to new cloud.microsoft domains by early October. Businesses need to update firewall and network settings now, or users could lose access.
Key points
- Microsoft 365 and Teams web apps are moving to new web addresses under the cloud.microsoft name, with full redirects due by early October 2026.
- The Teams move is already underway; Microsoft 365 was added to the rollout in July 2025.
- Businesses that block the new Copilot address for account-control reasons have a supported alternative: Microsoft's TenantRestrictions tool.
- Teams exceptions are available until 31 December 2026, after which Microsoft says no further delays will be granted.
- Organisations that can't meet the October deadline are advised to contact their Microsoft account representative.
Microsoft is changing the web addresses its customers use to reach two of its most widely used workplace tools. Teams is already moving to teams.cloud.microsoft. Microsoft 365, the suite covering Word, Excel, Outlook on the web and the rest, is heading to copilot.cloud.microsoft. Both changes were announced through Microsoft's internal customer notice system in posts MC1465764 and MC1462915.
For most employees, nothing will look different; the browser redirects them automatically. The headache is the IT department's.
Why does this matter to businesses?
Corporate networks often filter internet addresses through firewalls, proxies and secure web gateways. Think of these as digital bouncers: they check every destination a device tries to reach and block anything not on the approved list. If the new Microsoft addresses aren't on that list, staff will lose access to Teams or Microsoft 365 on the web.
Microsoft is asking IT teams to review those approved lists on every device and network gateway their organisation runs, then add the new addresses before the redirect completes.
| Service | Old address | New address | Redirect deadline |
|---|---|---|---|
| Microsoft Teams | teams.microsoft.com | teams.cloud.microsoft | Early October 2026 |
| Microsoft 365 | microsoft365.com | copilot.cloud.microsoft | Early October 2026 |
| Teams (exception window) | 31 December 2026 |
What if we were blocking the Copilot address on purpose?
Some organisations had already blocked copilot.cloud.microsoft to stop staff signing in with personal Microsoft accounts rather than company ones. Microsoft acknowledges the conflict. Its answer is TenantRestrictions, a setting that lets a company permit access to the address while limiting it to company-approved accounts only. The block-everything approach won't survive once Microsoft 365 moves there.
What should IT teams do right now?
Check your approved-address lists immediately. Microsoft's guidance is to confirm that corporate devices, proxies, firewalls and web gateways can all reach both new addresses. Organisations relying on a third-party web gateway should check with that vendor too.
If your network can't be updated before early October, contact your account representative. Limited flexibility exists for Teams until end of 2026. After that, Microsoft has been explicit: no extensions.
Should you worry about Teams reliability too?
The timing isn't ideal. We reported on 4 September that two separate Teams service issues were hitting Windows launch times and Mac call joins while Microsoft searched for a root cause. An access failure caused by an unupdated firewall will look identical to a Teams outage from the user's side. Make sure your IT team knows the difference before October arrives.
End users don't need to do anything. If IT handles the network changes, the redirect is invisible. If Teams or Microsoft 365 suddenly stops working in a browser, a gateway that hasn't been updated is the first thing to check.
