1. Home
  2. Getting Started
  3. The SaaS Monitoring Deployment Checklist

The SaaS Monitoring Deployment Checklist

Want to know all the steps for getting your Office 365 and SaaS monitoring started? You came to the right place. On this page we capture all of the critical steps about how to get started with Exoprise.

Sign In, Start a Trial

    • First, Sign Up at https://secure.exoprise.com/signup or just Sign In if you’ve already created an account
    • When you Sign In for the first time and haven’t deployed anything yet, you’ll land on a ‘Getting Started’ page within the product.

      It should look something like this and guides you through the steps:
      Getting Started Landing Page

Start Deploying

There are 3 different types of monitoring. Two of them are Synthetic Monitoring (we call them Sensors) for proactively detecting issues and one of them is Real User Monitoring (RUM) for solving remote or individual problems.

You can read about Synthetic Monitoring or Service Watch (RUM) on our website. We also have a great article that covers the pros and cons of each methodology.

  1. Private Sensors

    Private sensors run on your computers to simulate a user accessing a cloud service like Exchange Online, SharePoint, OneDrive or Microsoft Teams. First, you deploy what we call a Private Site to any Windows OS (its a Windows service). Then you deploy sensors to start monitoring your cloud apps. The analysis and alerting happens on Exoprise servers that run in the cloud.

  2. Public Sensors

    Public Sensors are similar to Private Sensors but they run on our computers in the cloud. They’re great for comparing cloud-to-cloud performance to the performance of an enterprise network, but they don’t tell you about the performance of users within your own environment. 
  3. Real User Monitoring

    Exoprise Service Watch is real user monitor for SaaS / Office apps. It securely runs from a browser extension and captures the performance of specific URLs / Domains that you configure it to watch. It’s great for monitoring applications you don’t own.

How’s the Trial Work?

During a 15 day trial, you can deploy up to 3 sensors to as many different locations that are needed. The purpose of an Exoprise trial is to understand the architecture and how easily the platform is deployed. Additional trial details:

  • The free trial for 15 days doesn’t start until you’ve successfully deployed your first sensor
  • Deploy as many Private Sites as needed – there’s no limit to the number of locations in a trial. 
  • During a trial, only one sensor can be deployed to an Exoprise owned Public Site.  There are some restrictions on which sensors can be run from a Public Site, that are mostly to do with licensing.
  • Only one Service Watch sensor can be deployed during a trial but a Service Watch sensor supports up to 25 users. Invite your coworkers and figure out how your SaaS services perform. 
  • We recommend setting up and tearing down sensors during the trial to test more than 3 different types of sensors. Most sensor pages look and feel similar, its the unique data elements and operations of each sensor that are different.

What Happens When the Trial Ends?

When the trial is finished you won’t get access to the data or sensors anymore. But you will have an opportunity to become a customer. We offer pay-as-you-go, cancel anytime, credit card subscriptions right from within your trial and you can purchase a single sensor.

At some point after your trial expiration, your sites and sensors will be groomed away and the data will be lost. We recommend that you export your data before the trial expires to keep it.

Can We Run A Second Trial?

No, that’s not possible. We have systems in place to detect such a thing and this violates our MSA. Definitely take advantage of your trial, ask us questions and let us know what we can help you with.

Can We Get a Trial Extension?

Contact us before your trial expires to check and see if a trial can be extended. You may have a unique environment that demands a longer trial or other circumstances. Send us a note and we’ll get back to you.

Invite Members of the Team

Inviting colleagues to help evaluate Exoprise during the trial period is easy. Just navigate to Admin > Users and generate an invite. Ensure the people you invite sign up with the link provided in the email otherwise they may not sign up for the same tenant.

Office 365 Monitoring Recommendations

For testing the Office 365 Monitoring capabilities during a trial we recommend starting with the following 3 sensors to properly evaluate Exoprise synthetics:

  • Exchange Online 
    Exchange Online sensors fully test the health and availability of Exchange Online, message queuing and your SPAM / mail-flow environment. You can configure Exchange Online sensors with real credentials or with OAuth (modern authentication)

    This sensor sends messages to an Exoprise auto-responder, so it important is that the
    exomail@exotester.com address isn’t blocked by your spam filters. 

  • SharePoint Online
    SharePoint online can be monitored using a headless browser or via the Microsoft Graph API using OAuth. Recently, Exoprise added support for testing and using accounts that utilize Multi-factor Authentication (MFA).

    The SharePoint API sensor leverages OAuth (modern authentication) and can support any account.
    The SharePoint sensor (browser-based) can fully tests Single Sign-On, MFA, Uploads, Downloads and a complete SharePoint Site.

  • MS Teams
    The Teams Message sensor and the more fully capable Teams AV Conferencing sensor both provide a full end-to-end test of the Microsoft Teams infrastructure. The Teams sensors utilize a rich headless browser to fully emulate a user signing into Teams through Single Sign-on solutions while fully exercising presence, messaging, channels, Video, Audio and more.

Account and Credential Notes

  • Acquire test accounts for Office 365 that will be used for Exoprise Sensor activity. We fully support both Federated and “Managed” accounts and recommend trying them both to see their differences.
  • OAuth is supported for many of the API sensors and where possible for parts of a complete test (like OWA).
  • MFA / 2FA is supported for many sensors and any SaaS property that is using Azure AD as your SSO / SAML solution. Read more about our MFA support.
  • The Add Sensor page describes the Sensor requirements, including things like authorization for each Sensor. Click through to the introduction on each sensor for more details about what each sensor tests.

Office 365 Service Communications and Status Messages

To retrieve Office 365 Service Communications and status messages for your tenant, go to the Admin > OAuth Authorizations page. You will need tenant administrative credentials, just once, to enable Exoprise to read the status and informational messages. Read more.

Proxy Considerations for Corporate Environments

Many enterprise customers come to Exoprise to test the performance of cloud and SaaS services from behind proxies. Proxies do slow down cloud service access and IT administrators want to measure the affects. 

Exoprise fully supports synthetic transactions through proxies of all kinds and configurations. Additionally, Service Watch can be used through proxies. Here are helpful notes about proxied environments:

  • The Exoprise Management Client fully supports reading and utilizing the same proxy that your desktop is configured to use (Internet Explorer Options). It can also utilize Proxy PAC or WPAD options.
  • An Exoprise Private Site and all of its sensors can utilize and test web services through proxies.
  • To properly utilize Proxy PAC or WPAD proxy configurations for a private site setup, you must install the Private Site as a service account. Read more about proxy setup and requirements.
  • By default, when setting up a Private Site as a Local System, the setup wizard will configure a fixed proxy. Utilize a Service Account for the Private Site if you want to use Proxy PAC or WPAD.

Related Articles