MC1456610: Microsoft 365 Copilot Chat in Edge Shifts from Outlook Endpoint to New m365copilotapp Endpoint

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
14
0 25 50 75 100
LOW IMPACT • MONITOR ONLY
Recommended Action:
No immediate action needed. Keep this on your radar.
What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsTenant AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
Microsoft has cancelled this message as the update is now consolidated under another communication. No technical change or configuration action is required beyond awareness and adjusting any tracking or communications. There is no direct user impact, and only minimal effort is needed for admins to disregard this notice.
20
🛡️ Admin Impact
0
👥 User Impact
15
Urgency
10
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Microsoft 365 Copilot Chat in Edge is moving to a new network endpoint. Organisations using allowlists or blocklists should review settings to avoid access issues.
👥

END USERS

Users may lose access to Copilot Chat in Edge if the new endpoint is blocked.
🛡️

IT ADMINS

Update network allowlists or blocklists to include cr.m365copilotapp.svc.cloud.microsoft before rollout.
📅

ROLLOUT TIMELINE

Upcoming:
Late September 2026

📢 Official Microsoft Message Center Announcement


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

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.

Source: Microsoft Message Center • Analysed by MWPro

<<< [MC1456610] Archive
Tooltip: View earlier revisions of this post

Share This Update