QuestionQ34

VerifiedConfigure and manage Microsoft 365 tenants and workloads

You have a Microsoft 365 subscription.

Your company has several branch offices, including one named Branch1. Users in Branch1 access Microsoft 365 through a corporate web proxy.

On the Network connectivity page in the Microsoft 365 admin center, Branch1 shows the following network insight: “We’re detecting WebSocket (WSS) connection failures to the domain: *.cloud.microsoft, which causes Copilot to not work correctly for your users.”

HTTPS access to Microsoft 365 apps from Branch1 is successful.

You need to resolve the insight without altering connectivity for the other branch offices.

What should you configure?

Explanation

Microsoft identifies this insight as a WebSocket (WSS) failure and directs administrators to ensure that network devices or the web-proxy infrastructure permit the WebSocket protocol to hosts in *.cloud.microsoft and its subdomains. Because ordinary HTTPS access already works, enabling HTTPS or changing DNS does not remediate the failed WebSocket upgrade. Applying the required protocol allowance to the Branch1 proxy policy scopes the change to that office.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!