Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Microsoft Office 365 template requirements

Microsoft Office 365 template requirements

Updated July 31, 2018


As described in the Microsoft Office 365 templates overview, SAM includes out-of-the-box templates that you can use to monitor and gather metrics for your Office 365 subscription services. This article describes what you'll need to do before using the templates, including:

Verify accounts and rights

To use Office 365 templates, you'll need:

  • An Orion account with SAM administrator rights.
  • Administrator-level rights for target servers.
  • An Office 365 account with global administrator rights. 
    • The account must be a member of an Office 365 admin role.
    • The account should be an inclusive account to support the monitoring of all mailboxes.

Use UPN format to enter Office 365 credentials; for example, Do not use domain\username format.

SolarWinds recommends that you create a service account for Exchange Web Services (EWS) to avoid authentication issues when passwords are updated. 

Install and configure software on the Orion server

Here is an overview of setting up the Orion server to support Office 365 templates:

Complete these steps on the Orion server (not target servers) in the order listed.

  1. In the Microsoft Windows Services console, ensure that the Windows Remote Management (WinRM) service is running and the Startup Type is set to Automatic.
  2. PowerShell requires .NET Framework 3.5.x. but SAM 6.5 — 6.6.1 use .NET Framework 4.6.2. Use Server Manager's Add Roles and Features wizard to add .NET Framework 3.5. If you encounter issues, see this Microsoft KB article.
  3. PowerShell 2.0 or later is usually installed with Microsoft Server. If necessary, install it via Server Manager. 
  4. Download and install Microsoft Online Services Sign-in Assistant for IT Professionals Release to Web (RTW).
  5. Determine if Microsoft Azure Active Directory (AD) module for Windows PowerShell v.1.0.8070.2 or later is already installed by opening an elevated PowerShell prompt and running this command:
(Get-Item C:\Windows\System32\WindowsPowerShell\v1.0\Modules 
  1. If you need to install the Azure AD module, run the Install-Module MSOnline command in PowerShell. See Connect to Office 365 PowerShell for details. 
  2. To allow PowerShell scripts to return results from external Office 365 APIs, run the Set-ExecutionPolicy RemoteSigned command in PowerShell.
  3. To connect to Azure AD with your Office 365 subscription, run these commands in PowerShell:
$UserCredential = Get-Credential
Connect-MsolService -Credential $UserCredential
  1. As prompted, provide your Office 365 user name in UPN format (username@domain) and password, then click OK.

Configure target servers

Target servers should be managed nodes in SAM that are configured to accept remote PowerShell commands sent by the Orion server. One way to achieve this is to configure AppInsight for IIS on each node.

Before proceeding, review AppInsight for IIS requirements and permissions.

There are several ways to configure target servers as AppInsight for IIS nodes in the Orion Web Console:

You can also configure AppInsight for IIS via the Node Details page:

  1. Navigate to the Node Details page for the node.
  2. In the Management widget, click List Resources.
  3. Select the Microsoft IIS check box and click Submit to add AppInsight for IIS to the node.
  4. Navigate to the All Application widget and click the AppInsight for IIS application.

If the Microsoft IIS option does not appear, review AppInsight for IIS requirements and permissions on the target server.

  1. Navigate to the All Applications widget on the Application Summary page to verify that the node was added for Microsoft IIS. 
  2. Click the newly added AppInsight for IIS application to access the Application Details page.
  3. Click Edit Application Monitor to access the Edit Application page.
  4. Enter server credentials in the Configure IIS Server for Monitoring dialog box.
  5. Click Configure Server, as highlighted below.

A "Configuration completed successfully" message appears when the process is complete.               



PowerShell 2.0 and later requires .NET Framework 3.5.x. If that version is not yet installed on target servers, use Server Manager's Add Roles and Features wizard to add it. See also Use PowerShell in SAM.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Microsoft links were obtained on July 26, 2018, © Microsoft Corp.

Last modified