1. Home
  2. Sensors
  3. Deploy Microsoft Office 365 Sensors

Deploy Microsoft Office 365 Sensors

The following article will walk you through the steps to deploy Microsoft Office 365 Sensors. These Sensors will monitor the availability and performance of the specific applications and help you identify if issues are occurring at the internal network level, across the web or in the Microsoft Office cloud. We offer both browser based and API based sensors.

Browser Based Sensors

  • Office 365 Portal Web
  • Teams Message
  • Teams A/V Conferencing*
  • Outlook Web App*
  • SharePoint
  • OneDrive
  • Yammer

* These sensors have additional requirements during configuration.

API Based Sensors

  • AzureAD
  • Email Graph
  • Exchange Online
  • Exchange ActiveSync
  • Exchange FreeBusy
  • SharePoint API
  • OneDrive API

Choosing your Sites

A majority of the Office 365 sensors can be deployed to both Private Sites and Public Sites. To monitor the true performance and end-user-experience we recommend running the sensors at Private Sites. Doing so will provide you with insight into how the application is running in your own environment as oppose to Public Sites which are hosted by us in the cloud.

To deploy a Private Site, Click Here.

Deploy an Office 365 Sensor

If deploying to a Private Site, you will need to first download the Exoprise Management Client. If you are deploying to a Public Site, you can do so from your browser. The steps will be nearly identical.

Download the Exoprise Management Client


Account and Credentials

  • Acquire test accounts for Office 365 that will be used for Exoprise CloudReady synthetics. We fully support both Federated and “Managed” accounts and recommend trying them both.
  • We recommend utilizing one test account per site. When deploying to multiple sites, you should plan on acquiring multiple testing accounts. This will provide you with better coverage of your O365 Tenant.
  • The Add Sensor page describes the Sensor requirements, including things like authorization for each Sensor. Make sure you read through each of the tabs to fully understand the capabilities and requirements of the sensor.
  • MFA / 2FA is supported for all browser based sensors.
  • OAuth is required for all API sensors, and as part of configurations for certain other sensors like OWA and Teams AV Conference.
  • OWA uses API to handle mailbox housekeeping.
  • Teams AV requires a one time administrative OAuth to communicate with the bot.

Choosing a Sensor

Upon logging into Exoprise via the Exoprise Management Client or browser, navigate to Sensors and then Add Sensors on the left hand menu.

Add Sensor

Once there, you can choose either a Private Site or Public Site in the top left as well as the Office 365 Category and select the sensor for the application you want to monitor.

Deploy To

After you have selected the sensor you want to deploy, you will be taken to the Introduction page.



Please Note

We are using the Office 365 Portal Sensor in the following screenshots.

This page will give you a summary of what the sensor will be monitoring, the requirements and an explanation of the credentials that will be required.

Upon clicking Next, if deploying through the Exoprise Management Client you will be brought to the Prerequisites Page. This will verify that the machine has the Prerequisites installed to allow the sensor to deploy and run. If deploying to a Public Site via browser this step will be skipped. Once it has complete, click next.



Depending on which sensor you are deploying, the next screen will prompt you for information such as your SharePoint or OneDrive URLs or EMail Address depending on what type of sensor you are deploying. It will also prompt for credentials, TOTP key if using MFA, and OAuth credentials if applicable.



Multi Factor Authentication

Multi Factor Authentication

If the account that will be used for the sensor is configured with MFA, Click Here for instructions on getting your TOTP Key.



Once you have gotten to the Validation screen, the Exoprise Management Client will download the sensor to the site and validate that it is able to run properly. If there are any issues with the information input, it will generate an error along with a screenshot of what the sensor saw while attempting to run. Once Validation is complete, click Next to be taken to the Alarm Setup.

Alarm Setup

Alarm Setup

The Alarm Setup page will allow you to select how the Out of Box Alarms will be configured for this sensor. Alarms can be configured in a multitude of ways, read more here. Once you have configured your initial Alarm settings, click Next to get to the deployment screen.



In the Deploy section, you will be able to specify how frequently the sensor should run. For a Private Site sensor, you can select the Site you want to deploy to. We highly recommend manually going through this process for each site due to the validation that is done by the Management Client during the deployment process as not all environments are the same.








Related Articles