kennysarmy Posted January 13 Posted January 13 We've had random users reporting that emails take minutes to login to and that once the folder tree appears that clicking on emails does not display them immediately, they have to wait several seconds for them to display. We've logged quite a few calls with Microsoft but of course every time they want to remote in the affected user appears to be fine. Is there anyway I can gather more information about this issue? When it happens we've confirmed it happens on multiple browsers and that when the email is just sat waiting to load that other websites (such as the BBC) are working quick as expected. If I run Internet Speed tests at the time of the issue we are seeing results over 700Mbps Attached is what the emails look like as we wait for them to render! Any thoughts?
robintech Posted January 13 Posted January 13 does the browser Developer console show anything, or disabling QUIC make any difference
NegativeKillDeath Posted January 13 Posted January 13 Try running this and see if it brings up anything obvious M365 NetworkTest Also check Microsoft 365 URLs and IP address ranges - Microsoft 365 Enterprise | Microsoft Learn and make sure any of the optimize URLs aren't being restricted by filter/firewall.
kennysarmy Posted January 13 Author Posted January 13 1 hour ago, NegativeKillDeath said: Try running this and see if it brings up anything obvious M365 NetworkTest Also check Microsoft 365 URLs and IP address ranges - Microsoft 365 Enterprise | Microsoft Learn and make sure any of the optimize URLs aren't being restricted by filter/firewall. The Network test is failing
kennysarmy Posted January 13 Author Posted January 13 Just checking on these! What is required to run the advanced test client? The advanced test client requires .NET 6.0 Runtime. If you run the advanced test client without that installed you'll be directed to the .NET 6.0 installer page. Be sure to install from the Run desktop apps column for Windows. Administrator permissions on the machine are required to install .NET 6.0 Runtime. The advanced test client uses SignalR to communicate to the web page. For this, you must ensure that TCP port 443 connectivity to connectivity.service.signalr.net is open. This URL isn't published in the https://aka.ms/o365ip because that connectivity isn't required for a Microsoft 365 client application user. If you're using an HTTP proxy for connection to FQDN connectivity.office.com and encounter the error SignalR proxy configuration is different than origin., ensure connection to FQDN connectivity.service.signalr.net is allowed through the proxy. If a PAC file is being used to push proxy configuration settings, ensure the PAC file will return the same proxy settings for FQDN's connectivity.office.com and connectivity.service.signalr.net.
kennysarmy Posted January 13 Author Posted January 13 Bypassed our Smoothwall and getting a bit further!
Joeloman Posted January 13 Posted January 13 They have been having issues, but should be better now. https://downdetector.co.uk/status/microsoft-365/ 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now