Monitoring Benefit
MAPI/HTTP is the protocol modern Outlook uses to talk to a mailbox. This test confirms that a client can establish that connection and reach the mailbox — which is, for most organisations, the definition of "Outlook is working".
This is the same test as Exchange Online - Outlook MAPI/HTTP Status, run from a remote probe rather than from the ENow web server.
Why the probe version matters
MAPI/HTTP is a long-lived, chatty connection, which makes it more sensitive to the quality of the network path than a single request/response test. A site whose link is merely mediocre can pass a simple connectivity check and still give users an Outlook experience that stalls and reconnects.
Running the test from the site itself is what surfaces that. Comparing across contexts localises it:
| Pattern | What it points at |
|---|---|
| Fails everywhere, including the ENow server | Exchange, the namespace, or the test mailbox. |
| Fails from one probe only | That site's path — proxy, firewall, or a device that does not handle long-lived connections well. |
| Passes but slowly from one site | Users there will describe Outlook as sluggish even though monitoring is green. This is the case the probe exists to find. |
How do we verify the monitoring test results?
- Run the Microsoft Remote Connectivity Analyzer from that site — testconnectivity.microsoft.com, Outlook connectivity test.
- Check Autodiscover first if both are failing. MAPI/HTTP depends on Autodiscover to locate the endpoint, so an Autodiscover failure will present here too. See Exchange Remote Probe - Outlook - Autodiscover Status.
- Open Outlook's own connection status on a client at that site (Ctrl + right-click the Outlook icon in the notification area, then Connection Status) to see the protocol actually in use and the connection count.
- Confirm the probe is reporting — see Remote Probe - Connectivity Status.
Where the settings are
Probe test accounts are set under Server > Tuning Policy > Settings > Probe Configuration > Configure Probes…. Probe thresholds, including latency, are separate from the server-side values and live under Server > Monitoring Policy > Thresholds in the Remote Probes section.
Where this is shown in the console
This check appears under Exchange Remote Probes > Outlook, which you can open directly:
https://<ENow web server>:20080/MailscapeWeb/Exchange/ExchangeOutlookRemoteProbe.aspx?server=<PROBE>The probe name in the query string carries a suffix — for example LONDON-EXCHANGE rather than LONDON. You can also reach the page by selecting the probe's row under Exchange Remote Probes on the dashboard at /MailscapeWeb/Default.aspx.
Common warning or error results, and potential solutions
| Result | Potential solution |
|---|---|
| Fails alongside Autodiscover | Fix Autodiscover first. MAPI/HTTP cannot locate the endpoint without it, so this failure is usually a symptom. |
| Connects then drops | Something in the path is timing out or terminating idle connections. Check proxy and firewall idle timeouts at that site — MAPI/HTTP holds connections open far longer than a web request. |
| Passes with high latency | Compare against other probes. If one site is consistently slower, that is a link or proxy issue and users there will be complaining regardless of the green indicator. |
| Certificate errors from one site | TLS inspection. Exempt the Exchange namespace or trust the appliance certificate on the probe. |
| Fails after a client access or namespace change | Confirm the namespace the probe is testing is the one now in use, and that Autodiscover returns the new endpoint. |
Reference: MAPI over HTTP | Microsoft Learn
Comments
0 comments
Article is closed for comments.