MC1456610 High
(Updated) Microsoft 365 Copilot Chat: Updated commercial Copilot endpoint for Microsoft Edge
Summary AI-generated
Microsoft 365 Copilot Chat in Edge will use a new endpoint; orgs managing allowlists/blocklists need to update configs to avoid service disruption.
Suggested actions AI-generated
- Review and update network allowlists and blocklists before rollout begins
- Review network configurations controlling access to Copilot Chat in Edge
- Add new endpoint: cr.m365copilotapp.svc.cloud.microsoft
- Validate continued user access to Copilot Chat in Edge after rollout
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1462915 (Updated) Allow connections to copilot.cloud.microsoft before the Copilot URL redirect
- MC1484007 Updated Copilot in Microsoft Edge Experience
- MC1286300 Microsoft 365 Copilot transition to the cloud.microsoft domain
- MC1250274 (Updated) Microsoft Edge: Copilot new tab page
- MC1440972 (Updated) Microsoft Edge: Upgraded Copilot new tab page
- MC1454108 (Updated) Microsoft 365 Copilot app update: Simpler Copilot access
Original post from Microsoft
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.microsoftinstead ofoutlook.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.
Additional details from Microsoft
- Summary
- Microsoft 365 Copilot Chat in Microsoft Edge will change its endpoint to cr.m365copilotapp.svc.cloud.microsoft by late September 2026. Organizations using network allowlists or blocklists must update configurations to ensure continued access; no impact if no endpoint restrictions exist. Review and update network settings accordingly.