Microsoft cloud
SharePoint Online
SharePoint Online is Microsoft's cloud-based collaboration and document management platform, delivered as part of Microsoft 365. It provides team sites, document libraries with version history and co-authoring, list-based data storage, and an intranet and portal-building capability through modern SharePoint pages and hub sites.
Why SharePoint Online matters in a Microsoft estate
SharePoint Online matters because Microsoft 365, Azure, Windows 365, Teams, and related services are usually managed as one estate. The term connects to planning, cost, configuration, security, and day-two operational decisions across that estate.
How SharePoint Online shows up in practice
It also functions as the storage and content-management layer underneath several other Microsoft 365 services, rather than only as a standalone destination users deliberately navigate to. Every Microsoft Teams team has a connected SharePoint site backing its Files tab, and every Microsoft 365 group that gets created, whether directly or through Teams or Planner, provisions a SharePoint site alongside it. OneDrive for Business itself runs on the same underlying SharePoint storage infrastructure, as a personal site per user. This means SharePoint governance decisions, such as site creation policies, storage quotas, and external sharing defaults, ripple directly into Teams and OneDrive behaviour, even for administrators who think of those as separate services.
Site sprawl is the most common long-term SharePoint governance issue in mature tenants, arising from the same root cause as Teams sprawl. A SharePoint site is provisioned automatically every time a Microsoft 365 group, Team, or Yammer community is created, and there is no default automatic cleanup. As a result, organisations accumulate large numbers of sites tied to finished projects, disbanded teams, or one-off initiatives, each one still consuming storage against the tenant's pooled quota and still representing a permissions surface that needs reviewing in any access audit.
External sharing is configured at both the tenant level, in the SharePoint admin center, and per-site, and the interaction between these two layers is a frequent source of confusion. A restrictive tenant-wide default does not retroactively lock down a site that was configured more permissively before the policy changed. A permissive tenant default allows any individual site owner to share as broadly as "anyone with the link" unless a site-level restriction overrides it. A genuine external sharing audit therefore has to check both levels, rather than assuming the tenant setting tells the whole story. Retention and compliance features, including retention labels, sensitivity labels from Microsoft Purview, and legal hold, apply at the SharePoint site and document level.
These are frequently the actual mechanism enforcing a broader Microsoft 365 compliance policy that appears, from a policy summary, to be a single organisation-wide rule, but is technically implemented as potentially many separate site-level configurations that each need to be correctly applied and periodically verified. Storage itself is pooled across the tenant rather than fixed per site, calculated from a baseline plus a per-licensed-user increment. This means unexpectedly high SharePoint storage consumption is usually diagnosable back to a small number of specific large sites or document libraries, rather than being an evenly distributed problem across the estate.