Forum Widgets
Latest Discussions
Network connectivity test TCP Connection results unreliable
My team has spent the last 2 business days trying to get the https://connectivity.office.com/ TCP connection test to complete successfully to appease the Microsoft Unified Support Team. They don't want to take our MS Teams crash diags until they see SSL Interception Detection and TCP connection tests passing successfully. We can't get TCP connection tests to pass, we get one of the following: Success Attempt #1 Success, Attempt #2 Failure Any number of errors to unblock URLs such as (but not limited to) ocsp.digicert.com,ocspx.digicert.com,ocsp.omniroot.com,su.symcb.com,sr.symcb.com,sd.symcb.com,s1.symcb.com,sa.symcb.com We figured it was something with the corporate network but that's not the case. Last night we had about 50 employees try this test from their home (personal) computers that have no connection to our corporation. The TCP Connection test fails on home (consumer) PCs. What's the story with this TCP Connection check?
My Feedback Portal account is bugged out.
I changed my Microsoft password a year ago, and it updated everywhere other than the Feedback Portal. As a result, I get an error when I try to login, or do anything on the page. Microsoft account support's suggestion was to login to the Feedback Portal which is insane given I'm having issues accessing it. How can I get this issue resolved? I've got three separate support tickets now and they keep asking me to wait 24 hours to get the issue resolved. Can someone from the Feedback Portal team please contact me to resolve this?" This is what Microsoft Support have said: "understand your frustration, and yes—this is an account‑related issue because the Feedback Portal is still tied to your old alias, which causes login conflicts and forces you out. Your Microsoft account itself signs in correctly, but the Feedback Portal is pulling outdated identity data that you cannot update on your own. Since you cannot access the Portal to submit feedback, directing you back there is not a workable solution. What you need is for Support to escalate this to the internal Identity/Feedback Platform engineering team so they can manually correct the outdated alias mapping on the backend. In this situation, the Feedback Portal and Tech Community teams are the ones who manage and maintain that specific platform. Because the issue appears on the Feedback Portal side—even though your Microsoft account is working normally—only their dedicated team can make the necessary corrections on their end. That’s why we are guiding you to connect with them through the links provided: https://techcommunity.microsoft.com/ or https://feedbackportal.microsoft.com/feedback. They will be able to review the portal‑specific account data and assist you further. I understand why this is frustrating. Since you’re unable to stay signed in to the Feedback Portal, I completely see why posting there isn’t possible for you. However, I do need to be transparent: I’m not able to escalate this issue directly to the Feedback Portal team, as they don’t provide internal escalation channels for us and only accept requests through their own platform. "
Office home and business Premium "service unavailable", product key activation
I purchased office home and business premium through a third-party service and have successfully redeemed the product key and manage to get through the first step of activating my lifetime subscription. However, when I am navigated to the 64g or 32g page, I select the appropriate gig for the product purchased, and once I initiate this download, I am brough to a page indicating that service is unavailable "we are having technical difficulties. I have deleted all previous versions of word on my device, and followed each step shown available. This is my second time purchasing this product due to having similar issues and am hope that this post will provide me the guidance necessary to finally activate this service to my current Microsoft account. Thank you in advance.Best Practices for Hybrid Cloud Deployments with Microsoft 365 & Azure
Hi everyone, I’m Jaxon Varr 👋 I’ve been working with Microsoft 365 and Azure for a while now, and I’m looking to refine our hybrid cloud deployment strategy. Right now we’re integrating Azure AD with on-prem identity services and expanding into Azure Virtual Desktop. Does anyone have recommendations for best practices around security, identity sync, and performance optimization when connecting Microsoft 365 services with Azure? I’d love to hear real-world insights or helpful resources. Thanks in advance!Microsoft 365 network connectivity test hanging on Running web browser tests
Hi community, I have this issue on different devices and from different locations. Whenever I visit https://connectivity.m365.cloud.microsoft/ and want to run the test, I select "Add location" instead of "Automatically detect location", because I'm on a laptop without GPS and don't wont to use the WiFi recognition. I start typing the town, select it from the list of choices, and click on "Run test". Nevertheless, a pop-up comes asking for access to location services, to which I select "Block" After that, the web application gets stuck on "Running web browser tests" and is not showing any results. I had this issue on Windows 10 and on Windows 11, and on Chrome and on Edge. Any idea how to solve this?Released the full version of M365 connectivity test tool (MCT) in GCC environment
I am pleased to announce that we have successfully released the full version of the M365 connectivity test tool (MCT) in the GCC environment today. This investment will ensure excellent network connectivity and user experience across all clouds, including around 5 millions users in GCC. You can find the updated public documentation at [here] and the table below shows the feature comparison across all clouds. Please let us know if you have questions, thanks
Websocket connections to critical Microsoft 365 domains
We continue to get warnings on our tenant regarding Websocket connectivity errors. Full message states: We've detected WebSocket Secure (WSS) failures to the following unified domains. I can't publish the wildcarded URLs here, but you'll know the ones I mean from your M365 admin networking connectivity insights page. I don't understand this as we effectively have those domains whitelisted/bypassing https inspection etc and everything seems to be working as normal. Nothing has been changed as far I'm aware. Anyone else seen this warning in their tenancy? Anything else we can check or try to sort the issue. Or is it just something to note?? We have a support ticket in - but on doing the initial check nothing is showing up. Our networking team have confirmed with me that the connection sends data to Microsoft uninspected. For that reason, it shouldn’t cause the websocket errors that are being reported.Optimizing Customer Network Connectivity for #Microsoft 365 Copilot
Network connectivity page in M365 admin center is the go-to place for tenant, network security administrators to review health and readiness of customer network connectivity setup essential for M365 applications. Problem statement Customers blocking WebSocket connections in their network infrastructure leads to broken experience for M365 Copilot users. Copilot uses WebSocket and tenant admins have no visibility into the failed WebSocket connections for their users, rendering the customer network setup not ready for Copilot roll out. Users with WebSocket connection failure will have a broken Copilot experience, here is a glimpse. We are pleased to announce the following new features in M365 admin center that are available to all customers. Admins can now view Service health notifications in Microsoft 365 admin center for Network insights detected for their tenant. They may also receive an email if opted-in to receive email notifications. The service health notification has a deep link that takes them directly to the detected network insight for their tenant, they will receive one notification per insight detected. Detected network insights include failed network connections for M365 Copilot, this public article documents the three network insights we detect Microsoft 365 Network Insights - Microsoft 365 Enterprise | Microsoft Learn Failed HTTPS connections for Unified domains *.cloud.microsoft, *.static.microsoft, *.usercontent.microsoft Failed WebSocket connections for *.cloud.microsoft Network Intermediation (TLS break and inspect) impacting performance I received a Service health notification for WebSocket or HTTPS connection failures, what should I do? Within the Service health notification there is a hyperlink that directly takes you to the Insights page in Network Connectivity. You can also go to the Insights page and click on the network insight, this shows the locations for which the insight has been detected, click on any location to review the location specific details and summary, the location summary provides you information like egress IP addresses (your source IPs from where we see connection failures) for this location. More information available in this video. 1. Visibility into failed network connections for M365 Copilot Tenant admins can now see in Microsoft 365 admin center (Microsoft 365 network connectivity - Microsoft 365 admin center) when their network impacts user connections to M365 apps, including WebSocket connections for M365 Copilot. The new report shows failure rate percentage, also known as the error rate percentage, for failed HTTPS and WebSocket connections to customer facing M365 Unified domains such as *.cloud.microsoft, *.static.microsoft, and *.usercontent.microsoft. A high error rate in this report indicates blocked network connections that impacts connectivity for various M365 applications and calls for immediate action from the tenant admin to allow blocked connections. 2. Visibility into user network latency for M365 Copilot Tenant admins can now view the network assessment points for Microsoft 365 Copilot, the assessment points are based on the network latency experienced by Copilot users. The lower the network latency, the higher the network assessment points for Microsoft 365 Copilot, providing a clear picture for tenant admins about the high network latency experienced by their users for M365 Copilot. In addition to the above, we recently announced M365 network connectivity test tool for individual users to test and validate if they successfully meet the network connectivity requirements for M365 Copilot. Additional reading references: Learn more about the connections blockers report Learn more about network assessments Learn more about M365 admin center network connectivity
