MC1456610
Plan for changeUpdated messageUser impactAdmin impact
Microsoft 365 Copilot Chat: Updated commercial Copilot endpoint for Microsoft Edge
Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Action date
24 Sep 2026
32d ago
Act by , as Microsoft's metadata states
What the notice says
Microsoft’s text, with source markup removedUpdated 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 Microsoft 365 Copilot Chat - Allow list for Microsoft Edge endpoints | Microsoft Edge | Microsoft Learn Compliance considerations No compliance considerations identified. Review as appropriate for your organization.
What changed
Between archive captures, newest first- Tags
User impact, Admin impact→ Updated message, User impact, Admin impact
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 …
- Tags
- · first version seen
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Notices it cites
Other posts named in this one- MC1462915 · (Updated) Allow connections to copilot.cloud.microsoft before the Copilot URL redirectPlan for change · changed 8 Oct 2026Returned by 2 reference tenants · Corroborated by Microsoft 365 Message Center Archive by Merill Fernando
Related public evidence
- Public source · 8 Oct 2026MC1462915: (Updated) Allow connections to copilot.cloud.microsoft before the Copilot URL redirect Microsoft 365 Message Center Archive by Merill Fernando
- Public source · 30 Sep 2026MC1484007: Updated Copilot in Microsoft Edge Experience Microsoft 365 Message Center Archive by Merill Fernando
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.