SharePoint Online
In plain English
Plain definition
A concise definition of SharePoint Online, Microsoft's cloud-based collaboration and document management platform, covering its technical model, operational relevance and common misunderstandings.
Technical Definition
SharePoint Online is a multi-tenant software-as-a-service (SaaS) platform built on the SharePoint application model. Each Microsoft 365 tenant is provisioned with one or more SharePoint site collections, which host sites, document libraries, lists and pages. Content is organised using content types, metadata columns and a permission-inheritance hierarchy, and the service is administered centrally through the SharePoint admin centre and the Microsoft 365 admin centre. Identity and access are governed by Microsoft Entra ID, and programmatic access is exposed primarily through Microsoft Graph and the SharePoint REST API.
Operational Relevance
In day-to-day operations, SharePoint Online underpins document management, team and departmental intranets, and structured workflows built with Power Automate. It is also the storage layer behind Microsoft Teams file sharing and OneDrive for Business, so a change to SharePoint sharing, retention or sensitivity-label policy can have effects that reach beyond SharePoint’s own interface. Because permissions can be inherited or broken at the site, library, folder or item level, permission sprawl and unintended external sharing are common operational risks that require periodic review rather than a one-off configuration.
- Confirm current sharing and retention settings in a pilot or non-production site collection before changing tenant-wide defaults.
- Confirm the administrator’s assigned role and the tenant’s licence tier before attempting a change, since available controls vary by plan.
Architecture Relationship
SharePoint Online sits inside the wider Microsoft 365 architecture rather than operating in isolation. Microsoft Entra ID supplies identity and conditional access; Exchange Online provides the mail-enabled groups that many SharePoint site memberships depend on; Microsoft Teams uses a SharePoint document library as the file-storage backend for each team channel; and OneDrive for Business is implemented as an individually owned SharePoint site collection. Power Platform services connect to SharePoint lists and libraries as a data source.
- Microsoft Entra ID: identity and access control for SharePoint sites.
- Microsoft Teams: uses SharePoint libraries for channel file storage.
- OneDrive for Business: a personal SharePoint site collection.
- Power Automate: automates actions against SharePoint lists and libraries.
This coupling means a change made in one service, such as an Entra ID conditional access policy or the deletion of an Exchange-based group, can materially affect SharePoint availability or permissions even though the change was not made in SharePoint itself.
Example
A project team creates a SharePoint site with a document library for design files. The library owner enables version history and check-out, sets a permission level that allows team members to edit but not delete, and applies a retention label so that approved final documents cannot be altered after sign-off. A Power Automate flow then notifies the team whenever a new file is uploaded to the library.
Common Misunderstanding
A frequent misunderstanding is treating SharePoint Online permissions as if they were simple folder permissions on a file server. In practice, permissions are inherited through a hierarchy of site, library, folder and item, and can be broken at any level to grant unique access. Without periodic review, this flexibility tends to produce accumulated, hard-to-audit access grants rather than a small number of clearly scoped exceptions. A second common misunderstanding is conflating SharePoint Online with OneDrive for Business: OneDrive uses the same underlying platform but is provisioned as a separate, individually owned site collection intended for personal file storage rather than shared team content.
Related Terms
- OneDrive for Business
- Microsoft Teams
- Microsoft 365
- Microsoft Entra ID
- Power Automate
- Exchange Online
- SharePoint admin centre
Further Reading
Before relying on this entry for a change ticket, validate the current tenant configuration directly in the SharePoint admin centre rather than assuming defaults, and record the prior configuration so that any sharing or retention change can be reversed. Specific licensing tiers, storage quotas and administrative-interface names are version-sensitive and were not independently re-verified against a dated primary Microsoft source for this entry; confirm them against current official Microsoft documentation before publication. For general context on how authoritative technical specifications are published and maintained, the RFC Editor’s RFC Series remains a useful independent reference point.