- About LogicMonitor
- Cloud Monitoring
- Dashboards and Widgets
- Getting Started
- LM Service Insight
- Backup and Recovery Systems
- Cloud Resources
- Networking & Firewalls
- Cisco VoIP Monitoring
- Cisco UCS Monitoring
- Brocade Application Delivery Controllers
- Checkpoint Firewalls
- Cisco APIC Monitoring
- Cisco ASA/ASR
- Cisco Device SNMP and NTP Configuration
- Cisco Firepower Chassis Manager Monitoring
- Cisco IP SLA Monitoring
- Citrix NetScalers
- Dell Switch Monitoring
- F5 BIG-IP Monitoring
- Fortinet Fortigate Firewalls
- Infoblox Monitoring
- Interface Status alerting and Bandwidth Utilization
- Juniper SRX
- Kemp LoadMaster Load Balancers
- Meraki Cloud Access Controllers
- NetFlow Monitoring
- Palo Alto Firewalls
- pfSense Firewalls
- Sonicwall Firewalls
- Operating Systems & Virtualization
- VMware Horizon Monitoring
- Citrix XenServer Monitoring
- Citrix XenApp/XenDesktop Monitoring
- ESXi Servers and vCenter/vSphere Monitoring
- Linux Disk Performance
- Linux File Systems reporting more than 100% usage
- Linux Inodes
- Linux Interface Bandwidth Utilization
- Linux NFS Server
- Monitoring a Domain Controller (DC)
- Monitoring Remote Linux Files
- NTP Configuration
- NTP Monitoring
- Nutanix HyperConverged Infrastructure
- SNMP v1/v2 Configuration
- SNMPv3 Configuration
- Solaris Monitoring
- Troubleshooting Perfmon Access
- Troubleshooting SNMP
- Troubleshooting WMI
- VMware vCenter Server Appliance (VCSA) Monitoring
- Windows Cluster Monitoring
- Windows Firewall Issues
- Windows Server 2000
- Windows XP
- Applications & Databases
- Microsoft Office 365 Monitoring
- OpenMetrics Monitoring
- Zoom Monitoring
- Apache Monitoring
- Cassandra Monitoring
- ConnectWise Monitoring
- Email Service Monitoring
- Java Applications
- Lighttpd Monitoring
- Microsoft Exchange Monitoring
- Microsoft SQL Server Monitoring
- MongoDB Monitoring
- MySQL Monitoring
- Nginx Monitoring
- Oracle Monitoring
- Pick & D3
- Postfix Monitoring
- PostgreSQL Monitoring
- RabbitMQ Monitoring
- Redis Monitoring
- Twilio Monitoring
- Varnish HTTP Accelerator
- Server & Operations Hardware
- Storage Systems
- Cisco HyperFlex Monitoring
- Apache Hadoop Monitoring
- EMC ECS
- EMC Isilon Monitoring
- EMC Unity Monitoring
- EMC VMAX
- EMC VNX/Clariion SAN
- EMC VNXe
- EMC VPLEX
- EMC XtremIO
- HPE 3PAR Storage
- HP MSA / StorageWorks / P2000
- HP P4000/Lefthand SANs
- NetApp E/EF-Series Monitoring
- NetApp Monitoring
- Nimble Storage
- Panzura Cloud Storage
- Quantum Small Tape Libraries
- VMware vSAN Monitoring
- Rest API Developers Guide
- RPC API Developers Guide - Deprecated
- Servicenow CMDB Integration
- Terminology and Syntax
Microsoft Office 365 is a line of cloud-based software offered by Microsoft as part of the Microsoft Office product line. LogicMonitor offers out-of-the-box monitoring for Office 365. With LogicMonitor’s Office 365 package, you can monitor the state of your Microsoft Office 365 deployment and the underlying services and license usage, allowing you to quickly identify faults and manage performance and license utilization accordingly.
Note: LogicMonitor also offers monitoring for the Microsoft Exchange server. See Microsoft Exchange Monitoring for more information.
Add Resource Into Monitoring
Add your Microsoft Office 365 host into monitoring. As cloud-based software, there is no physical resource to add into monitoring so simply create a new resource with “outlook.office.com” as the IP address/DNS name. Be sure to assign a Windows-based Collector or Collector group to the resource. For more information on manually adding resources into monitoring, see Adding Devices.
Create Credentials for Office 365
LogicMonitor must provide the appropriate credentials in order to successfully access Office 365. These credentials must belong to an Office 365 user account with global admin access (the account does not require any licenses). The following roles are required:
- Reports reader
- Message Center reader
- Message Center Privacy reader
For more information on adding users, see Microsoft’s Office 365 documentation.
Once the user account is created, log into Microsoft’s Exchange Admin Center and add the new user to the “View-Only Organization Management” Exchange role.
Additionally, enter the username and password associated with the new account as properties on the Microsoft Office 365 resource you created within LogicMonitor. As discussed in the Assign Properties to Resource section of this support article, the properties that carry these values are office365.user and office365.pass.
LogicMonitor initiates remote PowerShell sessions to retrieve data from Office 365. There are two PowerShell modules that need to be installed on the Windows Collector host (or hosts if you are monitoring using an Auto-Balanced Collector Group or have a backup Collector) that is associated with your Office 365 resource in LogicMonitor:
- MSOnline PowerShell Module
Install-Module -Name MSOnline
- MSOnline SharePoint PowerShell Module
Install-Module -Name Microsoft.Online.SharePoint.PowerShell
Note: The PowerShell cmdlet Install-Module requires Windows Management Framework (WMF) 5.1.
Ensure that your Collector(s) can run PowerShell scripts by setting the execution policy to RemoteSigned on the Collector host(s):
Set Up Microsoft Graph API
LogicMonitor uses the reports API in Microsoft Graph to collect Office 365 usage data. For more information on Microsoft Graph, see Microsoft Graph documentation.
Follow these steps to register and authorize a new application to call the reports API:
- Log into the Azure portal using an administrator account.
- Navigate to Enterprise Applications under Azure Active Directory. Click + New Application.
- From the Add an application dialog, select “Application you’re developing”.
- From the App registrations dialog, click + New registration.
- Provide a meaningful name for the application.
- Leave all other settings as they are and click Register.
- On the Overview page for the new application, locate the following:
- Application (client) ID. Create a property on the LogicMonitor host named office365.clientid and enter this ID as the property value. (For more information on assigning properties, see the Assign Properties to Resource section of this support article.)
- Directory (tenant) ID. Create a property on the LogicMonitor host named office365.tenantid and enter this ID as the property value.
- Open the Open the Authentication page for the new application and perform the following steps:
- Click + Add a platform to allow access tokens for a web application.
- From the Configure platforms dialog that displays, select “Web”.
- On the following Configure Web dialog, enter your LogicMonitor portal URL as the redirect URI.
- Check the Access tokens option.
- Open the Certificates & secrets page for the new application and perform the following steps:
- Click + New client secret and provide a description.
- Immediately copy your new client secret value (you will not be able to view it again).
- Create a property on the LogicMonitor host named office365.clientsecret.pass and enter the client secret as the property value.
- Open the API permissions page for the new application and perform the following steps:
- Click + Add a permission.
- When the drawer from the right appears, select “Microsoft Graph” and then “Application Permissions”.
- Under the Reports heading, check the Reports.Read.All option.
- Click Grant admin consent for <domain>.
- When finished, two green checkmarks will display confirming that consent has been granted.
Assign Properties to Resource
The following custom properties must be set on the Microsoft Office 365 resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.
Note: If you’ve performed the setup requirements in the previous sections, several of these properties will already be present.
From the LogicMonitor repository, import all Microsoft Office 365 LogicModules, which are listed in the LogicModules in Package section of this support article. If these LogicModules are already present, ensure you have the most recent version.
Once the LogicModules are imported (assuming all previous setup requirements have been met), the PropertySources will automatically detect the host and assign the appropriate values to the system.categories property. This, in turn, will automatically associate the DataSources (and ConfigSources if supported by your LogicMonitor account) and data monitoring will begin.
LogicModules in Package
LogicMonitor’s package for Microsoft Office 365 consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.
Note: The package includes ConfigSources (configuration file monitoring), which are only available to customers that are using the LM Config add-on feature. For more information on ConfigSources, see Creating ConfigSources.
When setting static datapoint thresholds on the various metrics tracked by this package’s DataSources, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.
In this Article: