SAM Microsoft Office 365 application monitor template requirements

11/14/2018 3:43 AM

11/29/2022 1:10 PM

As described in Using Microsoft Office 365 templates, SAM includes out-of-the-box application monitor 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
• Install and configure software on the Orion server
• Configure target servers

Note: This article applies to Office 365 templates introduced in SAM 6.5. For templates released in SAM 6.9 and later that integrate with Microsoft Graph, see the following links for requirements:

• Microsoft Office 365 OneDrive
• Microsoft Office 365 SharePoint Online
• Microsoft Office 365 Skype
• Microsoft Office 365 Skype for Business
• Microsoft Office 365 Teams

Note: The following templates were deprecated in SAM 2020.2 due to Microsoft end-of-support for Basic Authentication in Exchange Online APIs. Consider using API poller templates instead. 

• Microsoft Office 365 Exchange Online
• Microsoft Office 365 Mobile Device Management
• Microsoft Office 365 Portal
• Microsoft Office 365 Subscription 

Server Application Monitor

n/a

Verify accounts and rights 

To use Office 365 templates, you'll need:

• An Orion account with SAM administrator rights. Use UPN format to enter Office 365 credentials; for example, user@domain.onmicrosoft.com. Do not use domain\username format.
• Administrator-level rights for target servers.
• An Office 365 account with Global Administrator rights. Alternatively, use an account with an admin role that has adequate rights to subscriptions, management groups, monitored mailboxes, and Office 365 API access.  

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

Disclaimer: SolarWinds Technical Support cannot assist with the creation of user accounts for third-party systems such as Office 365 or Exchange, nor the assignment of permissions to such a user accounts. For assistance configuring Microsoft account permissions, please refer to Microsoft documentation and Microsoft Technical Support (© 2019 Microsoft, available at www.microsoft.com, obtained on June 25, 2020).

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. See  About Windows Remote Management (©  2018 Microsoft, available at https://www.microsoft.com/, obtained on November 20, 2018).
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. (©  2018 Microsoft, available at https://www.microsoft.com/, obtained on November 20, 2018).
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 RTW. (©  2018 Microsoft, available at https://www.microsoft.com/, obtained on November 20, 2018).
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 
\MSOnline\Microsoft.Online.Administration.Automation.PSModule.dll)
.VersionInfo.FileVersion

6. If you need to install the Azure AD module, run the Install-Module MSOnline command in PowerShell. See Connect to Office 365 PowerShell (©  2018 Microsoft, available at https://www.microsoft.com/, obtained on November 20, 2018) for details. 
7. To allow PowerShell scripts to return results from external Office 365 APIs, run the Set-ExecutionPolicy RemoteSigned command in PowerShell.
8. To connect to Azure AD with your Office 365 subscription, run these commands in PowerShell:

$UserCredential = Get-Credential
Connect-MsolService -Credential $UserCredential

9. 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.

PowerShell 2.0 and later requires .NET Framework 3.5.x. If PowerShell 2.0 or later and .NET Framework are not yet installed, use Server Manager's Add Roles and Features wizard to add them. See also Use PowerShell in SAM.