Short answer: for most organizations, SharePoint Online is the default and SharePoint Server is the exception you have to justify. The cloud service is per user, per month, with Microsoft running the platform; the server licence only wins when a specific constraint demands it — data residency in a jurisdiction the cloud service does not cover, full-trust custom code, air-gapped environments, or a datacentre refresh that is already budgeted. That is SharePoint Server vs SharePoint Online licensing in a line: one model asks you to buy server licences plus access rights up front, the other charges a predictable monthly fee and hands the infrastructure work to Microsoft. Before you commit, model the total cost over a five-year term the way you would for any custom software investment — licences, infrastructure, admin time, upgrades and exit costs included. If you would rather not build that comparison alone, send your user counts and compliance constraints to the team at software4 and we can work through both options with you.
The Core Licensing Difference in Plain English
Before you can compare costs, you need to understand what you are actually buying. At its heart, SharePoint Server vs SharePoint Online licensing is a choice between owning infrastructure and renting a service.
SharePoint Server (on-premises or self-hosted on IaaS) uses the classic Microsoft "server + CAL" model. SharePoint Server licensing means you buy a licence for each server instance running SharePoint, then a SharePoint client access licence (CAL) for every user or device that connects. Enterprise features sit behind an additional Enterprise CAL. Running it also requires Windows Server, SQL Server, hardware or cloud VMs, backups, patching and the people who keep it all alive. Licences are perpetual — you own that version for the long term — but support and upgrades are a separate conversation, and SharePoint Subscription Edition now moves even on-prem customers toward a recurring arrangement.
SharePoint Online is bought per user, per month, either standalone or bundled inside Microsoft 365. SharePoint Online pricing includes storage for your files, uptime, security patching and feature updates. There is no CAL maths, no SQL Server bill and no lengthy in-house upgrade project. The trade-off is less control over configuration, limits on server-side code, and costs that scale linearly with headcount.
What Other Software Licensing Models Teach Us About SharePoint
It helps to recognise that SharePoint's choice mirrors patterns you already know from everyday tools:
- Freemium with a paid tier. utorrent software and mx player software give away a capable free version and monetise through ads or a pro upgrade. SharePoint Online's entry plans behave similarly — generous on basics, gated on advanced compliance and analytics.
- Free for personal, paid for business. irfanview software is the classic example, and much free editing software follows the same rule: "free" licences rarely survive an audit in a commercial environment, which is exactly why shadow file-sharing tools are risky next to a properly licensed SharePoint tenant.
- Per-employee subscriptions. Payroll and hcm software platforms such as patriot software charge per employee per month — the same logic as a SharePoint per-user subscription, and beautifully predictable until your headcount doubles.
- Seasonal and per-transaction licensing. drake software and similar tax packages price around filing volume and seasons. If your SharePoint usage is highly seasonal (bid seasons, audit windows), paying per user for twelve months of a three-month peak can look expensive.
- Per-device and regulated licensing. mdm software is licensed per device, emr software per clinician or practice, and both carry heavy compliance obligations. That is a useful parallel for the device-based SharePoint CAL, and for organizations that choose SharePoint Server precisely because regulators require data in a specific place.
- Event and sector-specific models. tournament software is licensed per event or club, while aztec software in education is licensed per learner cohort. SharePoint Server fits this pattern when a single internal workload — not the whole organisation — needs the platform.
- Perpetual licences going subscription. quicken software shifted from a one-off purchase to annual subscriptions, and acquisitive groups like constellation software show how vertical products converge on recurring revenue. SharePoint Subscription Edition tells the same story: perpetual ownership is fading in many product lines.
And a word of warning about the opposite extreme. The internet's favourite software gore screenshots — overlapping dialogs, broken layouts, nonsensical errors — usually come from systems bolted together without a clear licensing or integration plan. Mismatched versions, unlicensed third-party web parts and half-migrated document libraries produce exactly that kind of mess.
Cost Modelling: CapEx vs OpEx
This is a financial decision as much as a technical one, so run a five-year comparison rather than a one-year one.
For SharePoint Server, add: server licences, user or device CALs, Windows and SQL Server licences, hardware refresh or cloud VM costs, storage and backup, disaster recovery, SSL and load balancers, patching labour, and at least one major version upgrade in that window. Small teams are often surprised that the infrastructure costs dwarf the SharePoint Server licensing itself.
For SharePoint Online, add: per-user subscriptions across five years with realistic headcount growth, extra storage packs, add-on compliance or e-discovery SKUs, the cost of migrating existing files, and any third-party backup tool your auditors insist on. Then account for bundle value — if you already pay for Microsoft 365, a large chunk of your SharePoint Online pricing may already sit in your invoice.
This is the same discipline you would apply to an ERP business case: compare total cost of ownership and the cost of change, not sticker prices.
Compliance, Control and Customisation
Choose SharePoint Server when you need data residency the cloud service does not offer, deep integration with legacy line-of-business systems on a private network, full-trust server-side solutions, or air-gapped environments. Choose SharePoint Online when you want continuous feature delivery, Microsoft-managed security, mobile and external sharing out of the box, and integrations with Teams, Power Automate and Copilot-style AI features that are cloud-only.
One practical point: productivity add-ons your staff already like — time blocking software, task boards, note tools — typically integrate with the online version first. On-prem integrations tend to lag, and some never arrive.
Hybrid: The Pragmatic Middle Ground
Hybrid lets you keep sensitive document libraries on-premises while moving collaboration, search and personal sites to the cloud. SharePoint hybrid licensing means paying for both models simultaneously, so it is the most expensive option on paper — but often the most workable route for regulated businesses that still want modern tooling. Treat hybrid as a transition state with a defined end date, not a permanent architecture.
A Quick Decision Checklist
- Fewer than 300 staff, no special data residency rules → SharePoint Online, almost always.
- Strict on-shore data rules, heavy custom code, existing datacentre → SharePoint Server or hybrid.
- Rapid headcount growth, remote-first teams → SharePoint Online.
- Flat headcount, long hardware refresh cycle already budgeted → model both carefully; the server case can still win.
- No dedicated SharePoint admin → SharePoint Online.
Conclusion
With SharePoint Server vs SharePoint Online licensing, the default is the cloud and the exception is the server — and the exception has to be justified by a real compliance, integration or financial constraint. Document your user counts, regulatory requirements and integrations, then price both options over five years, including the move to SharePoint Subscription Edition if you stay on-premises. If the numbers are close, lean toward the option that needs fewer specialists to keep running. To turn that comparison into a migration or consolidation roadmap, talk to the team at software4 about your current environment and the outcome you want next.