Partners frequently ask whether the Liongard Microsoft 365 Inspector can alert when SharePoint Online storage is approaching the tenant’s maximum capacity.

At this time, tenant-wide SharePoint storage capacity cannot be retrieved by the Inspector.

As a result, reliable alerting on total SharePoint storage utilization is not currently supported.

This limitation is caused by the data currently collected by the Inspector and by the way Microsoft exposes SharePoint storage data through supported APIs. It is not a metric configuration issue.

The Inspector collects SharePoint storage data using the Microsoft Graph API.

The Inspector currently uses Microsoft Graph drive endpoints for SharePoint storage-related data. Those drive endpoints expose quota information for individual drives or document libraries, not the tenant’s overall SharePoint storage pool.

Microsoft Graph does include SharePoint usage reporting endpoints, but they do not provide the same straightforward current tenant storage pool values that would be needed for reliable tenant-capacity alerting in this Inspector.

Using the storage data currently collected by the Inspector, it is not possible to reliably determine:

While Microsoft provides some SharePoint usage reporting, it does not map cleanly to a simple live tenant-capacity calculation within this Inspector.

The Inspector retrieves document library storage information using:

These endpoints return quota properties for individual drives (document libraries).

The drive.quota values returned by Microsoft Graph represent quota constraints on a specific drive resource, such as a SharePoint document library. These values should not be treated as the organization’s total SharePoint tenant storage capacity.

Common characteristics include:

Metrics that attempt to estimate tenant storage by summing drive quota values will produce inflated or misleading totals.

Multiple document libraries within a single site can report identical quota limits.

Site quotas define allowed growth per site, not available tenant storage.

Graph quota data does not include context about tenant-wide allocation or remaining capacity.

Because of these factors, aggregated results do not represent real SharePoint usage.

Understanding this distinction is critical.

Represents:

✔ Maximum allowed size for a specific site or library
✔ Administrative configuration
✖ Not tied to purchased tenant storage
✖ Not suitable for capacity monitoring

Actual SharePoint storage capacity is surfaced through Microsoft administrative tooling, such as the SharePoint Admin Center, which shows total and available storage for the organization. Microsoft also documents organization-level storage properties through SharePoint Online PowerShell cmdlets, such as Get-SPOTenant.

This tenant-level view includes:

✔ Total storage purchased for the organization
✔ Storage consumed across all sites
✔ Remaining available capacity
✔ Accurate capacity monitoring information

This is not a metric logic issue.

Even correctly written metrics cannot produce accurate tenant storage calculations because the underlying data does not represent tenant capacity.

No — not currently.

Because tenant-wide storage capacity cannot be retrieved, the Inspector cannot determine when SharePoint is approaching its maximum storage limit.

No reliable workaround exists within the Liongard platform at this time.

Until tenant storage data becomes accessible through supported APIs, organizations should monitor SharePoint capacity using Microsoft administrative tools, such as:

Accurate tenant-level monitoring would require a supported data source that exposes the organization’s SharePoint storage pool directly, such as SharePoint administrative tooling or a Microsoft-supported reporting source that can be reliably mapped to tenant-capacity thresholds. Those sources are not currently used by the Inspector for this purpose.

Contact Liongard Support if: