Microsoft is continuing the transition of Microsoft 365 experiences to cloud.microsoft, the unified, dedicated domain for Microsoft first-party products and services. As part of this transition, all Teams web client users will be redirected automatically from teams.microsoft.com to teams.cloud.microsoft.
This domain change applies only to Teams for organizations. Teams for consumers at teams.live.com is not updated.
Timeline
- By 30 September 2026: Automatic redirect for all organizational tenants is implemented unless a Teams administrator postpones it.
- By 31 December 2026: If a Teams administrator postpones it. Application developers and the network team can remediate application/network compatibility issues.
- From 1 January 2027: Organizations can no longer postpone the redirect to teams.cloud.microsoft at the tenant level.
How does this affect your users?
Users who open teams.microsoft.com are redirected automatically to teams.cloud.microsoft. No action is required from end users.
.microsoft is a top-level domain operated exclusively by Microsoft. Read more at What is cloud.microsoft?
- Existing links and bookmarks for teams.microsoft.com redirect appropriately.
- The visible change is limited to the address bar, where the domain now ends with .microsoft rather than .com.
- Sometimes I also see users who type teams.cloud.microsoft.com, which doesn’t work and isn’t covered yet.
Organizations that already follow standard Microsoft 365 network guidance should generally see no effect, since cloud.microsoft has been part of that guidance since April 2023. A network team should ensure connections to *.cloud.microsoft are not blocked by client devices, proxies, firewalls, secure web gateways, or other enterprise network controls.
The main risk is for Teams web apps using an older Teams JavaScript SDK or relying on restrictive domain, X-Frame-Options, Content Security Policy, authentication, or redirect settings that specifically reference the old teams.microsoft.com hostname. Such apps may not render or launch correctly under the new domain. Application developers should follow the March 2024 guidance. The Teams desktop client remains available as a workaround while developers resolve the web-specific compatibility issues.
Temporary administrator control to postpone the redirect:
A temporary control lets a Teams administrator disable the automatic redirect until 31 December 2026, so affected users can continue to reach teams.microsoft.com while developers or the network team remediate the application/network compatibility issues.
A Teams administrator can find the UseUnifiedDomain setting in the Teams client configuration settings (via PowerShell).
UseUnifiedDomain
This setting controls whether users are redirected from teams.microsoft.com to the unified domain teams.cloud.microsoft.
Possible values are:
- MicrosoftDefault, Microsoft will manage redirection behavior. If no explicit admin configuration is set, users may be redirected automatically.
- Disabled, Users will remain on teams.microsoft.com. Use this if your organization’s apps are incompatible with the unified domain.
# Check the current setting
Get-CsTeamsClientConfiguration | select Identity,UseUnifiedDomain | fl
Update the current setting.
Set-CsTeamsClientConfiguration -Identity Global -UseUnifiedDomain <MicrosoftDefault | Disabled>