Applications Systems

Troubleshoot Microsoft Office 365 application monitor template issues in SAM

This article provides troubleshooting tips for SAM's Microsoft Office 365 application monitor templates.

First published date

11/14/2018 3:26 AM

Last published date

2/21/2025 10:35 PM

Overview

As described in the Using Microsoft Office 365 templates article, SAM includes out-of-the-box application monitor templates that you can use to gather metrics for your Office 365 subscription services. This article provides troubleshooting tips for Office 365 templates released before SAM 6.9 that do not integrate with Microsoft Graph.
 

Note: For templates released in SAM 6.9 that integrate with Microsoft Graph, see the following links:

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 

Product section

Server Application Monitor

Resolution

Here are some troubleshooting tips for Office 365 templates: 

  • The apiversion=v1.0 parameter is required in PowerShell scripts for the Microsoft Office 365 Teams and Microsoft Office 365 OneDrive application monitor templates, including related application monitors. Otherwise, scripts return [ERROR] The remote server returned an error: (404) Not Found. messages. Alternatively, use one of the Microsoft 365 API poller templates.
  • Make sure you have appropriate account credentials. The templates rely on Windows PowerShell scripts that support an Office 365 account with Global Administrator privileges but an alternative account with an admin role can be used if it has the necessary privileges. See Microsoft Office 365 template requirements
  • Check your Office 365 credential format. Use UPN format — username@domain, not domain\usernameformat. 
  • Verify installed components. See Microsoft Office 365 template requirements.
  • Use an Office 365 service account. A service account for Exchange Web Services is recommended to avoid issues with authentication when passwords change.
  • If nodes stop responding, check the node configuration. If you configure a node to use ICMP and enable the Dynamic IP Address option, SAM can ping the node to report if it is up or down, and then adjust automatically if the IP address changes. See Microsoft Office 365 template FAQs for details
  • Reduce throttling. Try setting the frequency to 1200 (20 minutes) rather than the default of 300 (5 minutes). To learn more, see Avoid getting throttled or blocked in SharePoint Online (© 2018 Microsoft Corp., available at https://docs.microsoft.com, obtained on November 29, 2018). The article is about SharePoint but the concept is the same for Office 365.
  • Verify template settings. Office 365 polling jobs only run on the x64 architecture platform. To check settings, navigate to the Manage Templates page, select a template, click Edit, and click Advanced.

  • If templates do not return data, ensure a value is defined for the maximum number of mailboxes — the default setting is 5000. If you receive a System.OutOfMemoryException, the total memory on the system may exceed the allowable size for ICMP or SNMP; try changing the polling method on the node to an agentless method, such as WMI. Also, make sure you're running PowerShell scripts locally on the Orion server to avoid WinRM issues for remote locations. 

 

For additional details about Office 365 templates, see: