Changes › MC1456610

(Updated) Microsoft 365 Copilot Chat: Updated commercial Copilot endpoint for Microsoft Edge

Microsoft 365 suite Plan for change
Published
17 Aug 2026
Last modified
09 Sep 2026 16:17 UTC
Act by
24 Sep 2026 (26 days ago)
Ends
10 Sep 2026
First archived
25 Aug 2026
Revisions
2
Tags
Updated messageUser impactAdmin impact

Full post

Updated September 9, 2026: We are removing this post as the feature described below is now being tracked in MC1462915. You can safely disregard this message.

[What and why]

Microsoft 365 Copilot Chat in Microsoft Edge is updating the endpoint used for the compliant Copilot Chat experience in the Edge sidebar. The endpoint is changing from outlook.office.com/hosted/semanticoverview/Users to cr.m365copilotapp.svc.cloud.microsoft.

This change aligns Microsoft 365 Copilot Chat in Edge with the current endpoint architecture and documented Microsoft Edge allowlist requirements. Organizations that manage network allowlists or blocklists may need to update their configurations to ensure continued access to Microsoft 365 Copilot Chat in Edge.

[Rollout schedule]

  • General Availability (Worldwide, GCC, GCC High, DoD): Beginning in late September 2026 and expected to complete by late September 2026

[Impact on your organization]

Who is affected

  • Organizations that use network allowlists or blocklists to manage access to Microsoft 365 Copilot Chat in Microsoft Edge
  • Microsoft 365 Copilot Chat users accessing Copilot Chat through the Microsoft Edge sidebar

Platforms and services

  • Microsoft Edge
  • Microsoft 365 Copilot Chat

What will happen

  • Microsoft 365 Copilot Chat in Edge will begin using the commercial Copilot endpoint cr.m365copilotapp.svc.cloud.microsoft instead of outlook.office.com/hosted/semanticoverview/Users.
  • Organizations that explicitly allow or block network endpoints for Microsoft 365 Copilot Chat in Edge may need to update their configurations.
  • If the new endpoint is blocked or not allowlisted, users may experience issues accessing Microsoft 365 Copilot Chat in Edge.
  • No changes are expected for organizations that do not manage endpoint allowlists or blocklists for this service.

[Action required and recommendations]

Action required: Review and, if necessary, update your organization's network allowlists and blocklists before rollout begins.

Recommended actions:

  • Review any network configurations that control access to Microsoft 365 Copilot Chat in Microsoft Edge.
  • Add the following endpoint where required: cr.m365copilotapp.svc.cloud.microsoft
  • Validate that users can continue to access Microsoft 365 Copilot Chat in Edge after the rollout.

Learn more

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Related messages

Discussion

No messages yet — start the thread.

Sign in with your email to join the discussion — we send a one-time link, no password.

© Microsoft — archived from the Microsoft 365 Message Center. Content notice

Revision history

  1. 25 Aug 2026 07:01 UTC — Microsoft's lastModified 17 Aug 2026 17:13 UTC
  2. 09 Sep 2026 18:00 UTC — Microsoft's lastModified 09 Sep 2026 16:17 UTC