Q: What is the metric data resolution and delay?
A: Data is collected from Microsoft portal every 5 minutes. Typical delays for data available through Microsoft APIs are in 15-30 minutes range. However, some metrics are available in 1-day resolution only and always reflect yesterday's status:
- license consumption and activations
- mailbox counts, including which mailboxes are active and inactive, and which are in specific quota categories
- storage, including storage for mail, OneDrive, SharePoint
Q: Why email activity count is flat over the day and delayed for a day?
A: The email activity metric is a tricky one; we are looking for ways to provide near-real-time email activity summaries. Any advice in this regard is welcomed. Please use the Community thread to provide feedback.
Q: What does the metric "office365.tenant.service.health" represent?
A: The metric "office365.tenant.service.health" represents the current health of the different M365 services. The specific service recorded by a metric line can be determined by looking at the "service" dimension. The value of the "Service Health Status" metric is calculated using a mapping between the possible status of each service to a numerical value:
serviceOperational -> 0,
falsePositive -> 1,
serviceRestored -> 2,
postIncidentReviewPublished -> 3,
verifyingService -> 4,
restoringService -> 5,
extendedRecovery -> 6,
investigating -> 7,
investigationSuspended -> 8,
serviceDegradation -> 9,
serviceInterruption -> 10,
These values increase as the corresponding service status becomes worse. Three tiers of service status can be used, values 0-4 are a healthy status, values 5-7 are in a warning state, and values 8 and above are considered an error status. These tiers are used in the default dashboard.
Q: What are the API's used by the extension?
A: The extension collects data from the Microsoft Graph API and the Office 365 Management API. Microsoft's authentication endpoint is also used to retrieve authorization tokens. The specific API endpoint that gets used depends on the type of Office 365 tenant that is being monitored. The extension currently supports the Enterprise tenant.
Enterprise Tenant:
Q: Does this extension monitor Azure AD or Active Directory on-prem?
A: This extension does not monitor Azure AD or Active Directory on-prem. This extension provides only two metrics related to O365 user interactions with AD: number of logons and number of failed logons.
Use Active Directory monitoring extensions to monitor Active Directory on-prem. Note that these extensions don't support Azure AD.
Q: What is the DDU Consumption of this extension?
A: The formula for DDU consumption of the extension is:
40 * 525.6 DDUs/year per monitored M365 tenant
Typically, there's one tenant monitored - your enterprise M365 tenant. However, the extension allows for monitoring of multiple tenants.
DDU cost above does not include any possible Log events or Custom events triggered by the extension. For more information on this, please visit the DDU log event cost and DDU custom event cost pages.