---
title: "Microsoft Exchange Test"
slug: "microsoft-exchange-scout"
updated: 2026-02-23T19:18:17Z
published: 2026-02-23T19:18:17Z
canonical: "support.controlup.com/microsoft-exchange-scout"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.controlup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Exchange Scout

The Microsoft Exchange Scout tests the connectivity to Microsoft's web-based Exchange server.

The following connectivity tests are preconfigured for the Exchange Scout:

- **smtp.office365.com** over TCP port **25** and **587**
- **outlook.office365.com** over TCP ports **993** and **995**
- **autodiscover-s.outlook.com**
- **attachments.office.com**

## Create a Microsoft Exchange Scout

1. In the Synthetic Monitoring top bar, click **Create Scout** to open the **Add New Scout** window.
2. From the **Applications** tab, select **Microsoft Exchange Online** as the Scout **Type**.
3. Select the locations (**Hives**) from which you want to test the Exchange server.
4. Enter a **Name** for the Scout.
5. Select how often you want to test the resource using the **Run Every** slider. You can choose any interval from 5 to 60 minutes, in increments of 5 minutes (5, 10, 15, 20, and so on).
6. Optionally, add **Tags** to your Scout. Tags are key-value pairs which can be used to organize your Scouts. To learn more about tags, visit [Centralized Tags Management](/v1/docs/centralized-tags-management).
7. Click **Next: Alert Policy** to set up alerts and notifications on the Scout before saving it. For more information, visit [Alert Policies](/tim-reorg/docs/alert-policies).

#### Use Case

To learn how to use Microsoft Exchange Scouts to troubleshoot network latency, **use our interactive use cases guide**:

[![startcourse.png](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/startcourse.png)](https://cuacademy.controlup.com/use_case/troubleshooting-network-latency/)

## Run the First Tests

After configuring the Scout, wait for the first test results. In the Scout overview, the following five widgets for each test are displayed: ![Five scout widgets](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/5%20scout%20widgets.png)

Status **Success** indicates a successful test. As you can see, we received responses to all four pings with an average response time of 2.38 milliseconds.

![](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/ScoutTestResultsDetails.png)

Status **Failure** indicates a failed test. Our last ping attempt timed out. If only one of the pings runs into a timeout, the entire test is considered a failure.

![](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/ScoutTestResultDetailsFailure.png)