Skip to content

Outlook client


The Outlook client test probes the connection to the Exchange online servers using HTTP. The Outlook app uses the same protocol and target to load the user's data (e.g. emails). Therefore, this test indicates whether users experience bad Outlook performance due to network related issues.


Parameter Value
Method HTTP(S)
Number of measurements 58
Warning threshold 500
Critical threshold 1000
Status percentage 10%


Locate the issue

There are many possible root causes for Outlook client issues. Therefore, narrow down where and when issues occur. Use the general troubleshooting guide and try to answer these questions:

  • Is it a client-specific, local or global issue?
    • Are there other clients with similar issues?
  • Are there other possibly related services with issues?
    • Are performance issue maybe caused by local connection issues or device performance issues?
    • Do other HTTP tests show similar patterns?
  • Are there performance changes over time?
    • Did the connection look better in the past? Are there any patterns?

If you find other services with issues also look at their test documentations.

Possible causes (status warning/critical):

TCP routing

The HTTP protocol uses TCP packets. If those packets are routed over many network hops (e.g. proxy server), the latency increases. Microsoft recommends to use a local breakout, a proxy bypass and no deep inspection for such packets.

  • Check if the packets are routed properly (according to Microsofts recommondations) and adjust the settings on the firewall, proxy, etc.
  • Check if the Bypass result on the system profile is true. If that is the case Outlook uses a configured HTTP proxy.

High bandwidth usage

If the bandwidth usage is high the HTTP tests notice it first. A high bandwidth usage impacts all services that use HTTP.

  • Check if other HTTP tests show similar high latencies.
  • Check if other clients at the same location have similar HTTP issues.
  • Check if the latency changes over the day.

Outlook congested

Although this is unlikely, it is still possible that the Exchange server in your region are congested.

  • Check if you have many clients (maybe even in different locations) with issues reaching Outlook to verify this.

Possible causes (status error):

Requests blocked

A proxy or firewall might block the requests from Rimscout to Outlook. To test the connection properly, consider unblocking those requests.

  • Check the proxy logs or the firewall for packets to and consider unblocking them.
  • Check if the Bypass result on the system profile is true. If that is the case Outlook uses a configured HTTP proxy.


If the operating system uses an HTTP proxy, the packets of this test use this proxy as well.

Outlook service outtage

In case only Outlook client is unreachable (and is not blocked) then there is likely an outtage of the service.

  • Ensure that only this test has issues to verify that there is an outtage and no local issues. Also at least all clients in a location should be blocked.