Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
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.
Note: You may want to create a new App registration in the Azure portal before you start so that you have these IDs and Secret Key available for setting up permissions.
Add your Office 365 account into monitor from Exchange > Cloud Integrations.
Note: If you do not have access to Cloud Integrations, you can manually add your Microsoft Office 365 host into monitoring by creating a new resource with “outlook.office.com” as the IP address or 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.
Under the Name settings, you will define how the connected Office 365 account should appear in your LogicMonitor environment.
Under the Permissions settings, you will enter the Tenant ID, User ID, and Secret Key. You can find this information in your Microsoft Azure portal, in the registration page for your app.
After you click “Add Service”, you should be able to view resources and dashboards from your Office 365 application.
LogicMonitor must provide the appropriate credentials to access Office 365. These credentials must belong to an Office 365 user account with the “Global reader” role assigned. The following roles are required:
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 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:
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.
Important: Because this is a cloud resource that relies heavily on the presence of properties for LogicModule association, care should be taken to set this property at the resource level only. Avoid setting these properties at the group or root level to ensure Microsoft Office 365 LogicModules aren’t incorrectly applied to other resources.
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.
A few customers have encountered scenarios where DataSources fail if data is behind a proxy. Although we have not been able to definitively verify proxies to be an issue in all cases, we are mentioning it as a possibility to help aid in troubleshooting if proxies are potentially a factor in your environment.
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: This package includes ConfigSources (configuration file monitoring LogicModules). If the ability to monitor and alert on configuration files is not currently available in your LogicMonitor platform and you would like to learn more, reach out to your customer success manager. 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.
Next, we’ve highlighted a sample dashboard and some sample monitoring scenarios that could be accomplished with the Office 365 LogicModule package.
The SharePoint DataSources will monitor multiple SharePoint site instances usage, traffic, storage, and file count, providing granular flexibility when monitoring SharePoint. With the information gleaned, you can decide whether to delete or combine sites that don’t get a lot of traffic but use up a considerable amount of storage.
Track the availability of certain services including Exchange sign in, voice mail, email, calendar, Microsoft portal, and billing page. Along with service availability monitoring, the Office365_Reports_ServicesUserActivity DataSource provides the total number of users that are utilizing the applications. The pairing of this information can be useful when prioritizing issues.
The Office365_Account_License DataSource alerts users when licenses are about to expire and also counts the surplus licenses available at any given time. When combined with our forecasting feature, this DataSource can help license capacity planning by indicating when it’s time to increase your license allocation. In the same spirit, the OneDrive DataSources, which track file counts and storage usage, can also provide essential capacity planning information.
Using user activity historical data collected across multiple services, such as call volume, meeting attendance, message counts, and so on, you can look into repurposing the licenses of the least active users if you are running low on licenses, or you might find that some licensed users are not in the organization anymore.
There is also device usage breakdown, allowing you to track which devices (Windows, Macs, iPhones, Androids) are most popular within your organization. This data can be useful when testing internal applications to prioritize testing on those operating systems that are most heavily used within the organization.
With the slew of Exchange ConfigSources, you can closely monitor all Exchange activity happening in your environment, from the addition of new users to changes made to Exchange organization config files. This insight can alert you to any suspicious activity.
In This Article