Introduction to SharePoint: Enhancing Collaboration and Content Management

SharePoint is Microsoft’s web-based platform for document management, collaboration, and building intranets — one tool covering what used to take several separate systems.

In this post: What it actually covers · Online vs on-premises · How it relates to Teams and OneDrive · Licensing: what’s included · The architecture underneath · Accessing it from a phone · When would you actually use this? · Related reading

What it actually covers

Document management: version control, check-in/check-out, and approval workflows — not just file storage.
Team collaboration: team sites, discussion boards, task lists, shared libraries.
Intranets and portals: customizable sites for company news, policies, and resources.
Workflow automation: a workflow engine (plus Power Automate) for approvals, reviews, and publishing.
Enterprise search: full-text and metadata-driven search across the org, not just one site.
Business intelligence: Power BI and Excel Services integration for dashboards and reports.

Online vs on-premises

Most new deployments are SharePoint Online — part of Microsoft 365, Microsoft-hosted and updated continuously, no server to maintain. SharePoint Server (on-premises) still exists for organizations that need to keep data on their own infrastructure, usually for regulatory or data-residency reasons, but it’s a separate product with its own release cycle, missing some of the newer Online-only features. If you’re starting from scratch today with no specific on-prem requirement, Online is the default, not a choice you need to deliberate over.

How it relates to Teams and OneDrive

This is the most common point of confusion for anyone new to Microsoft 365. Short version: OneDrive is personal storage — files that belong to one person until they’re explicitly shared. SharePoint is shared, team/org-level storage with real document management on top (versioning, metadata, permissions structure). Microsoft Teams doesn’t have its own file storage at all — every “Files” tab inside a Team channel is a SharePoint document library, just displayed through the Teams interface. Upload a file in a Teams channel and it’s sitting in that team’s SharePoint site whether you ever open SharePoint directly or not. See SharePoint and OneDrive: Everything You Need to Know for the deeper version of this distinction.

Licensing: what’s actually included

For most organizations, SharePoint isn’t something you buy separately — it’s bundled into Microsoft 365 Business and Enterprise plans alongside Teams, Exchange, and the Office apps. Standalone SharePoint Online Plan 1 and Plan 2 licenses do still exist for the rare case of needing SharePoint without the rest of the suite, but Microsoft has confirmed these standalone plans are being phased out — new sales stop during 2026, with service continuing for existing subscribers until 2029. If you’re licensing SharePoint today, buying it as part of a Microsoft 365 suite is both the simpler and the more future-proof path.

The architecture underneath

Worth understanding the shape of it before you start creating sites, because retrofitting structure later is real work. A tenant contains many site collections, and each site collection can contain subsites — but Microsoft’s own guidance has pushed away from deep subsite hierarchies for years now, in favor of flat, independent sites connected by hub sites: a hub gives a set of related sites shared navigation, branding, and cross-site search without nesting them inside one another. If you’re planning a departmental structure, design it as a hub with member sites, not a tree of subsites three levels deep.

The part that surprises people who’ve only used SharePoint casually: it’s not just a place documents happen to live, it’s the content layer several other Microsoft 365 features are built directly on top of. Viva Connections dashboards and Viva Engage are built from SharePoint pages and content underneath their own branding. And Microsoft 365 Copilot grounds its answers by retrieving from Microsoft Graph and Microsoft’s Semantic Index — which means the permission structure you set on a SharePoint site directly determines what Copilot can and can’t surface to a given user. Copilot doesn’t get special access; it only ever returns what the person prompting it could already see by clicking into the site themselves. Getting SharePoint permissions right isn’t just an access-control exercise anymore — it’s also what keeps AI-generated answers scoped correctly.

Practically, this means a few decisions are worth making deliberately rather than by default: who holds Site Collection Administrator on each site collection (broader than a site Owner — it’s the role that can approve hub associations and manage storage), whether a new site should join an existing hub or start its own, and whether content that shouldn’t be AI-surfaced (draft financials, unreleased plans) is actually locked down or just informally “not linked from anywhere.” Informal obscurity doesn’t stop Copilot the way an actual permission boundary does. Storage is pooled at the tenant level and shared across every site collection rather than allocated per-site by default, which matters once you’re planning capacity for more than a handful of sites — see Manage Site Storage Limits in SharePoint for how that pool actually works.

SharePoint consolidates document management, collaboration, and workflow automation into one platform, at the cost of some depth compared to a best-of-breed tool for any single piece.

Accessing it from a phone

Worth knowing this exists as its own dedicated app, not just a mobile browser tab: the SharePoint mobile app (iOS and Android) gives access to sites, news, and files, with offline access to files a user has specifically pinned for that purpose. It’s a genuinely different experience from OneDrive’s mobile app — OneDrive’s app is scoped to personal and synced files, while the SharePoint app is built around site navigation and the same news/announcements experience as the desktop site. For anyone whose day-to-day SharePoint use is mostly “check this one site for updates,” the dedicated app is worth installing over relying on a bookmarked browser tab, since it also supports push notifications for site activity that a browser tab can’t.

When would you actually use this?

You’re managing documents across a team via shared drives and email attachments, and version conflicts keep happening — SharePoint’s version control and check-in/out fixes exactly this.
You need a company intranet for news, policies, and resources that isn’t a static page nobody visits — SharePoint’s Communication Sites are built for this specifically.
You’re stitching together separate tools for storage, discussion, tasks, and workflow approvals — SharePoint consolidates most of that into one platform, at the cost of some depth compared to a dedicated best-of-breed tool for any one piece.

Choosing the right SharePoint Online site type — worth reading before creating your first site.
SharePoint Permissions: A Comprehensive Guide — read this before inviting anyone into it.
Understanding SharePoint List Types — once you’re ready to store structured data.

Good to go. Comment if anything doesn’t line up.