Admin, security & compliance Rolling out #153

Allow *.cloud.microsoft for the Copilot URL redirect

Copilot URL redirect requires network access checks

Microsoft scheduled the redirect from m365.cloud.microsoft to copilot.cloud.microsoft for early September 2026 where access was already available, and early November 2026 for remaining users. Completion of these phases is not confirmed.

Key points

  • Blocking URLs within *.cloud.microsoft may prevent Copilot access in the web app, desktop app, and Microsoft Edge experience.
  • Microsoft requires allowing the entire *.cloud.microsoft domain, not selected Microsoft 365 application URLs.
  • Organizations following the recommended network configurations for Microsoft 365 Copilot need no additional network changes.
  • The redirect retains the domain’s security, compliance, and enterprise allow-listing properties.
  • TenantRestrictions can restrict personal Microsoft account authentication while allowing access to the Copilot service URL.

What to do

Validate *.cloud.microsoft access with the Microsoft 365 Connectivity Test tool. Coordinate with network and security teams to review filtering, proxy, firewall, Conditional Access, and app control policies. Allow the entire domain if blocked. If configuration cannot be completed before your redirect, contact your Microsoft account representative. Tell users that the web app will redirect automatically.

Timeline

  1. 27 August 2026 Published
  2. September 2026 Rollout start (planned, not confirmed) Scheduled initial redirect where the destination is accessible.
  3. November 2026 Rollout end (planned) Scheduled redirect for remaining users; completion is unconfirmed.
Speaker notes

This is a network-readiness change, not a new Copilot capability. The scheduled September start has passed, so the status is rolling-out, but the source does not confirm completion. The detailed schedule places remaining users in early November 2026, although the introductory text still mentions October. Blocking the domain can affect the desktop app and Microsoft Edge experience as well as the web app. Organizations already following the recommended network configurations need no additional changes. Where personal account sign-ins are the concern, explain TenantRestrictions as a targeted alternative to blocking the service URL. The source also gives September 10, 2026 as the deadline for contacting a Microsoft account representative if the domain is blocked; that deadline has passed.

Sources and links

Related cards

Area, status, change type, licence and flags are indicative. Always open the source before you act on a card.