MC1465764: Teams Web Client Redirects from teams.microsoft.com to teams.cloud.microsoft

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
52
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Tenant AdminsMicrosoft 365 AdminsTeams AdminsIT ManagersService OwnersDevelopers
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
Domain change for Teams web client introduces compatibility risks for custom apps, CSP and authentication settings. Admins must check network allowlists, update documentation and validate third-party or in-house web integrations before mandatory enforcement. User interruption is minimal as the redirect is automatic, but helpdesk readiness is advisable. Temporary admin control adds complexity and a remediation deadline, raising planning and effort requirements.
64
🛡️ Admin Impact
22
👥 User Impact
55
Urgency
58
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Teams web users will move from teams.microsoft.com to teams.cloud.microsoft. Features stay the same, but check for network and app compatibility before the redirect completes.
👥

END USERS

Users may notice the Teams web address changing to teams.cloud.microsoft.
🛡️

IT ADMINS

Verify *.cloud.microsoft is allowed, review app compatibility, update documentation, and brief support teams.
📅

ROLLOUT TIMELINE

Upcoming:
By Sept 2026

📢 Official Microsoft Message Center Announcement


Teams web client users will be redirected to teams.cloud.microsoft
Message ID: MC1465764

[What and why:]

Microsoft is continuing the transition of Microsoft 365 experiences to cloud.microsoft, a unified, trusted, and dedicated domain for Microsoft first-party authenticated products and services. As part of this transition, Microsoft Teams web client users in your organization will be automatically redirected from teams.microsoft.com to teams.cloud.microsoft.

This is a domain change only. Teams features and functionality are not changing, and no action is required from end users. Existing links and bookmarks that use teams.microsoft.com will continue to be supported.

The rollout that started per previous communication (MC116227) will continue in controlled stages through September 2026. By the end of September 2026, Microsoft plans to complete the redirect for the remaining tenants and remove the remaining rollout exception list. We continue to monitor signals across both domains to ensure continued reliability and performance.

Target timing

Customer-facing milestone

By September 30, 2026

Redirect all enterprise tenants – exception possible via admin control

Beginning January 1, 2027

Temporary tenant admin control is retired and the redirect can no longer be disabled

[Rollout schedule:]

Rollout will continue in controlled stages through September 2026, with plans to complete the redirect for the remaining tenants and remove the remaining rollout exception list by the end of September.

[Impact on your organization:]

How this will affect your organization

  • Users who open teams.microsoft.com will be redirected automatically to teams.cloud.microsoft.
  • Existing links and bookmarks remain supported and redirect appropriately.
  • Teams consumer experiences at teams.live.com are not affected by this change.
  • Users may notice that the new address ends in .microsoft rather than .com. This is expected; .microsoft is a top-level domain operated exclusively by Microsoft.
  • Organizations following standard Microsoft 365 network guidance should generally experience no impact.
  • Some Teams web apps may not render or launch correctly if they use an older Teams JavaScript SDK or restrictive domain, X-Frame-Options, Content Security Policy (CSP), authentication, or redirect settings.
  • The Teams desktop client can be used if an app has a web-specific domain compatibility issue.
  • Temporary tenant admin control – Available through December 31, 2026

    If your organization needs additional time to address an application compatibility issue, a Teams tenant administrator can temporarily disable the automatic OCDI redirect. When disabled, users will continue to be directed to teams.microsoft.com. This control is intended as a time-limited troubleshooting mechanism and will be retired after December 31, 2026. Beginning January 1, 2027, the redirect to teams.cloud.microsoft can no longer be disabled.

    Before using the control, identify the affected app and work with the app owner to update its domain configuration. Disabling the redirect should be temporary and should not replace the required application remediation

[Action required / Recommendations:]

  1. Ensure that connections to *.cloud.microsoft are not blocked by client devices, proxies, firewalls, secure web gateways, or other enterprise network controls.
  2. Update internal documentation and user education that explicitly references teams.microsoft.com. Existing links remain compatible, but updated material can reduce confusion.
  3. Inform help-desk/support that teams.cloud.microsoft is an expected Microsoft domain.
  4. If you use the temporary tenant admin control, complete the required app remediation and re-enable the redirect before December 31, 2026.

Application owners should validate the complete application experience under teams.cloud.microsoft. If an issue occurs, capture the tenant ID, affected app and app ID, user impact, timestamp, browser, affected URL, reproduction steps, and relevant network or browser-console details.

If the issue is specific to the Teams web domain, users can use the Teams desktop client while the application owner completes the required update. Contact Microsoft Support if you require assistance.

Developer readiness guidance: https://aka.ms/teams-newdomain-blog-devs

The cloud.microsoft domain has been part of standard Microsoft network guidance for Microsoft 365 domains and service endpoints since April 2023.

Source: Microsoft Message Center • Analysed by MWPro

Share This Update