SharePoint Server Subscription Edition: Licensing, Versions & Migration in 2026

SharePoint Server Subscription Edition (SPSE) is Microsoft’s current on-premises SharePoint branch. It is not “SharePoint 2022” or “SharePoint 2025”, and it is not a new perpetual edition that can be installed and forgotten. It combines local control of the farm with continuing licence entitlement, monthly cumulative updates and regular removal of obsolete dependencies.

The timing is important. Support for SharePoint Server 2019 ended on 14 July 2026. As at 28 July 2026, SPSE is on Version 26H1; the latest Public Update is KB5002882, released on 14 July 2026, build 16.0.19725.20434. Organisations still on 2019 therefore need a deliberate destination: a new SPSE farm, SharePoint Online, or a tightly controlled temporary legacy position whose lack of Microsoft support is explicitly accepted.

This guide separates three questions that are often mixed together: whether the organisation owns the necessary server and access rights, whether the installed build and dependencies are supported, and whether its workflows, forms, authentication and custom code are compatible. Technical ability to attach a database does not prove a licence entitlement, and valid licensing does not make an obsolete solution supportable.

What SharePoint Server Subscription Edition changes

SPSE remains recognisably SharePoint Server. The customer operates Windows Server, SQL Server, the farm topology, search, Distributed Cache, service applications, certificates, backups and disaster recovery. Data can remain in a customer-controlled data centre or suitable hosted environment. This makes SPSE relevant where sovereignty, network isolation, local integration or indispensable farm solutions rule out an immediate cloud move.

The strategic change is the servicing model. SPSE follows Microsoft’s Modern Lifecycle Policy and currently has no fixed retirement date. That does not grant indefinite support to an old build. Public Updates are monthly and cumulative, each PU has a one-year support window, and new feature sets are delivered twice yearly under the YYH1 and YYH2 naming convention.

Version 26H1 and the July 2026 update

Version 26H1 arrived through the June 2026 Public Update. Its documented features include the Modern People Card and Document Intelligence in the Standard release ring, while other capabilities can appear first in Early release. Feature Updates are not separate major-version installations: their code enters the monthly servicing channel and remains in later PUs.

On the cut-off date for this article, the newest PU is KB5002882 of 14 July 2026. It is cumulative, but administrators must still read the specific release notes. Microsoft documents prerequisites involving SharePoint Workflow Manager and a known issue requiring an action after PSConfig. Copying binaries through Windows Update does not necessarily complete the farm upgrade; the SharePoint Products Configuration Wizard or PSConfig stage must be planned, monitored and verified.

A sensible operating standard includes a representative test farm, monthly change review, database and configuration backups, tested recovery, build inventory, health checks before and after patching, and a named owner. “Modern Lifecycle” should be read as an operational commitment, not as freedom from lifecycle management. Microsoft’s SharePoint update history is the baseline, but the individual KB remains the change record for each maintenance window.

SPSE licensing: Server, CALs and an active entitlement

The basic model is Server/CAL. Each running server instance requires appropriate server licensing under the applicable Product Terms, and users or devices accessing SharePoint generally require a Standard CAL or equivalent access right. An Enterprise CAL is additive: it sits on top of the Standard CAL for defined advanced functionality rather than replacing the base CAL.

For SPSE, both the server side and applicable CALs require subscription rights or active Software Assurance. SharePoint Online Plan 1 or Plan 2 User SLs can provide base access rights in circumstances set out in the Product Terms, and Plan 2 can cover additive Enterprise functionality. That must be mapped to the actual agreement and user population; not every Microsoft 365 label should be assumed to confer identical on-premises rights.

Internet access can create confusion. Users accessing genuinely public, unrestricted web content may not require CALs, but an authenticated portal, partner extranet or restricted customer area is not public merely because it is reachable from the Internet. Count employees, contractors, guests, service identities and devices according to the real access model and the terms governing the customer.

What happens when Software Assurance ends?

Microsoft describes a perpetual right to run SharePoint Server 2019 when qualifying SPSE coverage ends or is bought out. It does not describe a perpetual right to continue running SPSE. The customer must stop running SPSE and may install 2019 under the resulting right. That fallback is commercially awkward in 2026 because SharePoint 2019 itself has been unsupported since 14 July.

This is why a perpetual second-hand SharePoint 2019 licence without active SA must never be presented as a route to SPSE. It may be transferable in a legally documented European scenario and useful for a narrowly defined legacy estate, but it does not by itself grant SPSE rights. Microsoft also places conditions on obtaining SA after a transfer. Procurement should verify origin, chain of title, prior divestment, edition, server quantities and CAL quantities, while licensing specialists validate the current Product Terms and agreement.

Technical requirements are a starting point, not an architecture

Microsoft supports SPSE on Windows Server 2019, 2022 or 2025 Standard or Datacenter, using Desktop Experience or Server Core. The database tier needs a supported SQL Server Standard or Enterprise release for Windows with database compatibility level 150, including SQL Server 2019 CU5 or later and SQL Server 2022. Azure SQL Managed Instance is supported only where the SharePoint farm is hosted in Azure; SQL Server Express and ordinary Azure SQL Database are not supported farm databases.

Base prerequisites include IIS, .NET Framework 4.8 and the appropriate Visual C++ redistributable; since 23H1, the Visual C++ 2015–2022 x64 package is required. Office 2013 is the minimum supported Office client, and Office must not be installed on a SharePoint server. Microsoft’s production multi-tier hardware minimum—64-bit, four cores, 16 GB RAM and suitable system/additional disks—is not a sizing recommendation.

Real design work covers SQL capacity and latency, search index and crawl load, Distributed Cache, MinRole placement, storage growth, antivirus exclusions, load balancing, certificates, outbound connectivity, monitoring, backup duration, recovery point and recovery time objectives. A small compliant server can still be an unfit production design. Record assumptions and test with representative content, permissions, search and concurrent usage.

SharePoint 2019, SPSE and SharePoint Online compared

SPSE fits when a documented requirement justifies local operation and the organisation is prepared to maintain the platform. SharePoint Online usually fits better when the priority is to reduce farm administration and use Microsoft 365 integration, governance and cloud innovation. Online is not a version upgrade: permissions, information architecture, workflows, forms, integrations and code can need redesign.

A temporary stay on SharePoint 2019 may buy migration time, but it should have an owner, risk acceptance, compensating security controls and a dated exit plan. “It still works” is not a support strategy. Unsupported web platforms accumulate exposure through Windows, SQL, browser, identity and integration changes even if no visible SharePoint feature fails.

Migration from SharePoint 2019 or 2016

From SharePoint Server 2019, Microsoft supports a database-attach upgrade. Build a new, patched SPSE farm; recreate farm configuration and service applications; install compatible solutions; restore copies of supported databases; and attach them so SharePoint performs the database upgrade. The configuration database is not moved. This separation is valuable because it forces old assumptions to be documented rather than silently inherited.

SharePoint Server 2016 content can also move directly to SPSE through database attach, without an obligatory stop at 2019. Source databases must meet the documented minimum build, at least 16.0.4351.1000. SharePoint 2013 and earlier do not have a direct supported path: they require intermediate stages, usually 2016, or a content migration to Microsoft 365 after evaluating functional transformation.

A practical migration sequence

1. Inventory: record farms, builds, databases, site collections, service applications, WSP and SPFx packages, web parts, workflows, forms, authentication, DNS, certificates, SQL and external systems.
2. Licence: reconcile server instances, Standard and Enterprise CAL needs, SA, subscriptions and cloud-equivalent access rights before production deployment.
3. Remove blockers: redesign unsupported forms, workflows and authentication; obtain supported versions of third-party products.
4. Build the destination: deploy a clean SPSE farm on supported Windows and SQL, apply the selected PU and establish backup and monitoring.
5. Rehearse database attach: work with copies, run Test-SPContentDatabase and resolve missing features or assemblies before the cutover.
6. Test services and business journeys: search, profiles, metadata, Secure Store, permissions, Office integration, sync, alerts, forms, workflows and line-of-business connections.
7. Cut over with control: plan content freeze or delta handling, DNS, communication, business sign-off, rollback and evidence collection.
8. Decommission and operate: retain required records, remove the old farm safely and start the monthly PU discipline immediately.

Legacy components that became blockers in 2026

From 14 July 2026, InfoPath Forms Services, SharePoint 2010 workflows, SharePoint Designer 2013 and Basic Authentication are no longer supported in SPSE. A component may still appear in a farm or function after that date, but presence is not support. Treat each dependency as a redesign programme with a business owner, replacement, data-retention decision and tested fallback.

Workflow deserves particular attention. SharePoint Workflow Manager has its own patch requirements, and some SPSE PUs depend on a suitable Workflow Manager update. Inventory both 2010 and 2013 workflow usage, custom activities, service accounts, certificates and endpoints. Do not assume that patching SharePoint alone leaves the workflow platform in a supported state.

Authentication changes can affect scanners, Office clients, integrations and scripted jobs. Moving away from Basic Authentication may require OIDC, modern client authentication, application redesign or updated middleware. Test non-interactive processes explicitly; human browser tests do not reveal every legacy credential flow.

How to make the destination decision

Start with constraints, not product preference. List legal or contractual data-location requirements, disconnected operation, latency, recovery objectives, local integrations, custom solutions, skills and available maintenance windows. Then challenge each claimed constraint. Some are genuine; others are inherited assumptions that a controlled cloud assessment can remove.

Compare a three-to-five-year operating model. For SPSE include Windows and SQL licensing, SharePoint entitlement, CALs, hardware or hosting, backup, monitoring, security, test environments, specialist labour and monthly maintenance. For SharePoint Online include user subscriptions, identity, network readiness, migration tooling, information governance, retention, redesign and adoption. Neither option is “free” because a line item disappears.

If second-hand perpetual software is considered for adjacent infrastructure or a bounded legacy need, use documented sourcing and keep the conclusion modest. Licendi’s server licensing category can help buyers compare available server products and evidence requirements. It is not a substitute for Microsoft’s SPSE subscription/SA entitlement, and an older SharePoint 2019 licence must not be described as granting SPSE rights.

Frequently asked questions

Is SharePoint Server Subscription Edition perpetual?

Not for continued operation of SPSE. The server and applicable CALs require active subscription rights or Software Assurance. The stated perpetual fallback is SharePoint Server 2019, not SPSE.

Is SharePoint Server 2019 still supported?

No. Extended support ended on 14 July 2026. A running 2019 farm is now an unsupported legacy environment.

What is the current SPSE version?

As at 28 July 2026, the current Feature Update is Version 26H1. The latest PU is KB5002882 of 14 July 2026, build 16.0.19725.20434.

How frequently is SPSE updated?

Public Updates are monthly and cumulative; Feature Updates arrive twice yearly. Each PU has a one-year support window.

Can SharePoint 2019 upgrade directly?

Yes, through a new SPSE farm and database-attach upgrade. It is not an in-place conversion of the existing farm.

Can SharePoint 2016 go directly to SPSE?

Yes, supported content databases at the required minimum build can be attached directly to SPSE without passing through 2019.

Do I need CALs?

Normally yes. Standard CAL is the base access right; Enterprise CAL is additive for advanced functionality. Equivalent subscription rights may apply under the Product Terms.

Are InfoPath and SharePoint Designer still supported?

No. Their SPSE support ended on 14 July 2026, together with SharePoint 2010 workflows and Basic Authentication.

Conclusion: supportability is a continuing process

SPSE gives organisations a supported on-premises SharePoint route, but only if entitlement, platform and solution compatibility remain aligned. The immediate 2026 priority is to move beyond SharePoint 2019’s 14 July support deadline without importing obsolete forms, workflows and authentication into a new farm.

Choose SPSE where local control has a defensible business reason and the organisation can sustain monthly servicing. Choose SharePoint Online where reducing farm operations and adopting Microsoft 365 outweigh the redesign effort. In either case, inventory first, test with real business journeys, document licensing separately from technical readiness, and make rollback and lifecycle ownership part of the project rather than an afterthought.