SharePoint

SharePoint is a web-based platform for document management, team collaboration, and corporate intranets. At its core, it provides document libraries with version control and co-authoring, team sites for project collaboration, communication sites for company-wide news, and lists for structured data management. It integrates with Power Automate for workflow automation and Power Apps for building simple custom applications on top of SharePoint data.

Within the Microsoft 365 ecosystem, SharePoint is the underlying storage layer for much of the platform. OneDrive for Business runs on SharePoint, and Microsoft Teams stores its files in SharePoint document libraries. This means many organisations are already using SharePoint without realising it. The platform targets a broad market, from small businesses needing basic document storage to large enterprises running complex intranets and business processes.

There is no free tier. Microsoft offers a 30-day trial of Microsoft 365 Business Standard which includes SharePoint. Standalone SharePoint Plan 1 starts at $5 per user per month. Most businesses access SharePoint through Microsoft 365 bundles, starting at $6 per user per month for Business Basic (which includes SharePoint alongside Teams, OneDrive, and web versions of Office apps). Mid-range plans like Business Standard run around $12.50 per user per month. Enterprise plans (E3 at roughly $36, E5 at roughly $57 per user per month) unlock advanced compliance features like eDiscovery, data loss prevention, and retention policies.

Watch out for storage costs. Base plans include limited SharePoint storage (typically 1 TB plus 10 GB per user), and extra storage costs $0.20 per GB per month. That adds up quickly if your team works with large files. Microsoft is also retiring standalone SharePoint plans, pushing customers toward full Microsoft 365 suites, and has announced roughly 13% price increases taking effect in mid-2026.

Vendor lock-in with SharePoint is a mixed picture. Your raw documents and files are fully portable since they are stored in their original formats. You can download them at any time. However, everything you build around those documents is deeply tied to the Microsoft ecosystem: permission structures, metadata taxonomies, content types, Power Automate workflows, Power Apps, and custom web parts.

Moving away from SharePoint is a significant project, not an afternoon's work. Third-party migration tools exist (ShareGate, AvePoint), which reflects both the demand for migration and the complexity involved. Microsoft's broader strategy of tightly integrating SharePoint with Teams, OneDrive, Copilot, and the rest of the Microsoft 365 suite makes the switching costs higher over time, not lower. If you are going to commit to SharePoint, treat it as a long-term platform decision.

Microsoft launched SharePoint in 2001, making it one of the longest-running collaboration platforms on the market. Microsoft itself is publicly traded (NASDAQ: MSFT) with roughly 228,000 employees and a market capitalisation around $2.9 trillion USD. SharePoint has over 200 million users and is used by roughly 80% of Fortune 500 companies, though it also has significant adoption among smaller organisations, with around 30% of SharePoint Online customers being businesses with fewer than 50 employees.

Microsoft is actively investing in SharePoint with AI capabilities through Copilot, and it remains a cornerstone of the Microsoft 365 suite. The on-premises version (SharePoint Server) is being wound down, with extended support ending for older versions in mid-2026, while SharePoint Online receives the bulk of new features and investment. There is essentially zero risk of Microsoft discontinuing SharePoint. It is foundational infrastructure for their cloud business.

SharePoint has a mature but fragmented API surface. Microsoft Graph is the recommended API for new integrations and works well for standard document operations, but it does not yet cover all SharePoint functionality. For anything involving complex permissions, site management, or specialised SharePoint features, you will need to fall back to the older SharePoint REST API or the legacy .NET SDK. This means integrators often end up working with multiple APIs in the same project, each with different authentication patterns and quirks.

Rate limiting uses an opaque "resource unit" system rather than simple request counts. For a typical small business tenant, the limits are adequate for normal operations, but if you are syncing large volumes of data or running bulk processes, you will hit throttling. The limits tightened in late 2025, and developers report hitting walls sooner than expected. Throttled requests still count against your quota, so aggressive retries make things worse. Microsoft reserves the right to change limits at any time, and load testing against SharePoint Online is explicitly prohibited.

Authentication requires setting up an application in Microsoft Entra ID (formerly Azure Active Directory), which involves navigating multiple Microsoft portals and understanding a complex permission model. It is not a quick setup. The older authentication method (Azure ACS) is being retired in April 2026, forcing many existing integrations to migrate.

SharePoint webhooks notify you when items in lists or document libraries change, but they have significant reliability limitations. Notifications can be permanently dropped if your endpoint does not respond within 5 seconds, and Microsoft themselves recommend running a backup polling process alongside webhooks to catch missed events. Webhook payloads do not include the actual change data, only a signal that something changed, so your application must then query SharePoint to find out what happened, which itself is subject to rate limiting.

Getting your documents out of SharePoint is straightforward. Files are stored in their original formats, so if you put Word documents and PDFs in, you get Word documents and PDFs out. You can download files through the browser, sync them with the OneDrive client, or pull them programmatically via the API.

The difficulty comes with everything else. List structures, metadata taxonomies, permissions hierarchies, version histories, and workflow definitions are deeply SharePoint-specific and do not migrate easily. Microsoft's own migration tool is primarily designed for moving data into SharePoint, not out of it. Third-party migration tools like ShareGate exist, but they reflect the real complexity of the task. Large-scale exports are also subject to throttling, which makes bulk operations slow. The 5,000-item list view threshold, which Microsoft has never lifted despite years of complaints, adds another layer of difficulty when working with substantial data sets.

Documentation on Microsoft Learn is extensive but can be confusing. The three overlapping API surfaces (Graph, REST, legacy SDK) mean you frequently encounter outdated guidance mixed in with current recommendations. Microsoft has open-sourced the developer documentation on GitHub, which helps with community corrections, but navigating the sheer volume of information takes patience.

For testing, Microsoft offers a free developer tenant through the Microsoft 365 Developer Program, which is genuinely useful. The SharePoint Framework (SPFx) supports a local workbench for testing custom web parts. However, the developer experience overall is widely regarded as below average compared to modern SaaS platforms. Debugging involves transpiled JavaScript with unreliable source maps, error messages are often unhelpful, and the tooling is in the middle of a transition from an older build system. A developer used to working with well-designed modern APIs will find SharePoint frustrating.