Microsoft 365 Integration-Level Monitoring

Introduction

When Enable Optimized Monitoring Mode (Recommended) is enabled for an Office 365 integration, the platform uses integration-level monitoring to collect service health and incident metrics. Instead of issuing separate API requests for each monitored service, the platform uses bulk Microsoft Graph API calls to retrieve health and incident information for all discovered services in a single monitoring cycle.

This monitoring mode is recommended for Office 365 integrations, particularly in environments with multiple services enabled, as it improves collection efficiency and reduces API consumption.

Benefits

Benefit	Description
Reduced API calls	Uses only two bulk API calls per monitoring cycle, regardless of the number of enabled services.
Reduced throttling risk	Minimizes Microsoft Graph API rate-limiting by reducing the number of requests.
Faster metric collection	Retrieves service health and incident data for all discovered services in a single operation.
Flexible monitoring frequency	Supports monitoring intervals of 5, 10, 15, 30, 60, 120, and 1440 minutes.

How Integration-Level Monitoring Works

When optimized monitoring mode is enabled, the platform executes the following Microsoft Graph API calls at the configured monitoring interval:

API Endpoint	Purpose	Data Collected
`/admin/serviceAnnouncement/healthOverviews`	Retrieves health status for all Office 365 services	ServiceStatus
`/admin/serviceAnnouncement/issues?$select=service,isResolved,startDateTime`	Retrieves current and historical service incidents	IncidentCount and ServiceOutageInHours

Monitoring Behavior

Metrics are collected only for services that are discovered in the tenant and returned by the healthOverviews API.
Integration-level metrics such as ServiceStatus, IncidentCount, and ServiceOutageInHours are collected at the provider level through bulk API calls.
Resource-level usage metrics continue to be collected independently using the standard monitoring mechanism and schedule.

Integration-Level Metrics

The following metrics are collected for each discovered Office 365 service using bulk Microsoft Graph API calls.

Metric Pattern	Unit	Source API	Description
`office365_{service}_ServiceStatus`	None	`healthOverviews`	Current service health status. Values range from 0–16.
`office365_{service}_IncidentCount`	Count	`issues`	Number of incidents associated with the service, including pending and resolved incidents.
`office365_{service}_ServiceOutageInHours`	Hours	`issues`	Time elapsed since the earliest unresolved incident for the service.

Resource-Level Metrics

Enabling optimized monitoring mode does not change the collection of resource-level usage metrics. These metrics continue to be collected using the standard monitoring schedule and are available only for services that provide usage report data.

Exchange Online

Metric	Unit
`office365_exchange_ActiveOrTotalMailboxCount`	Count
`office365_exchange_AppUsage`	Count
`office365_exchange_MailboxQuotaLimitCount`	Count
`office365_exchange_MailboxSizeTotal`	Bytes
`office365_exchange_MessagesTotalSentReadReceived`	Count

SharePoint Online

Metric	Unit
`office365_sharepoint_UniqueUserCount`	Count
`office365_sharepoint_ActiveUserCount`	Count
`office365_sharepoint_PageVisitCount`	Count
`office365_sharepoint_ActiveFileCount`	Count
`office365_sharepoint_TotalFileCount`	Count
`office365_sharepoint_Storage`	Bytes
`office365_sharepoint_TotalPageVisitCount`	Count

OneDrive for Business

Metric	Unit
`office365_onedrive_ActiveUserCount`	Count
`office365_onedrive_UniqueUserCount`	Count
`office365_onedrive_ActiveSiteCount`	Count
`office365_onedrive_TotalFileCount`	Count
`office365_onedrive_Storage`	Bytes

Microsoft Teams

Metric	Unit
`office365_microsoftteams_DailyActivitiesByActivityType`	Count
`office365_microsoftteams_DailyUniqueUsersByActivityType`	Count
`office365_microsoftteams_DailyUniqueUsersByDeviceType`	Count

Microsoft 365 Suite

Metric	Unit
`office365_osdpplatform_ActiveUserCount`	Count
`office365_osdpplatform_ActiveInactiveUserInServicesCount`	Count
`office365_osdpplatform_GroupActivityCount`	Count
`office365_osdpplatform_ActiveGroupCount`	Count
`office365_osdpplatform_Storage`	Bytes
`office365_osdpplatform_FileCount`	Count

### Yammer Enterprise

Metric	Unit
`office365_yammer_InteractionWithMessagesCount`	Count
`office365_yammer_UniqueUserCountInteractingWithMessages`	Count
`office365_yammer_UserCountByDeviceType`	Count
`office365_yammer_DailyUserCountByDeviceType`	Count
`office365_yammer_GroupCount`	Count
`office365_yammer_InteractionInGroupsCount`	Count

Note

Some Office 365 services, such as Microsoft Copilot, Microsoft Forms, and Power BI, do not provide usage-report metrics. For these services, only integration-level metrics (ServiceStatus, IncidentCount, and ServiceOutageInHours) are collected when optimized monitoring mode is enabled.
Resource-level usage metrics are not affected by the Enable Optimized Monitoring Mode setting. These metrics continue to use the standard resource-level monitoring process and schedule.
Alert generation for integration-level metrics uses the thresholds and configuration defined in the applicable resource-level monitoring templates.