Native SharePoint, an extension or a standalone platform: which path for your public sector intranet?
Public sector organizations share the same constraints. Staff are spread across several entities, short contracts are common, and many employees in public works or schools have no computer. These constraints shape the choice of a technical path.
The technical path is no substitute for a sponsor or contributors, but it determines who pays, where data is stored and what you can require. It must also last: Microsoft gives at least twelve months' notice before ending a service with no successor (Microsoft, 2024). This guide describes the conditions under which each path is the right one, without grading anyone.
What's inside this guide:
- Three paths on Microsoft 365: what native SharePoint with Viva Connections covers in 2026, what an extension added to your Microsoft 365 environment brings and what a platform hosted by its vendor implies.
- Twelve criteria for three paths: five criteria specific to the public sector and seven standard criteria, with a method to weight each one from 1 to 3 before any demo.
- Procurement and data: why the value over the whole contract term sets the procedure, five reversibility points to write into the RFP and what the regulations say on data residency, personal data and accessibility.
- Employees without a computer and the five-year cost: what Microsoft 365 F1, F3 and E plans allow for the intranet, the sign-in test to run in the demo and the cost lines that quotes often leave out.
- Decide, then stand by it: four questions asked in order to point to your path before you go to tender.
- The scoring grid and the cost grid: one grid per path to score the 12 criteria on evidence and cost eight lines in a low and a high scenario.
- 25 requirements for your RFP: five blocks (procurement and contract, data and security, accessibility and inclusion, functional and contribution, durability and support), each requirement with the evidence to request.
Why download it:
A grid that grades nobody. The matrix shows under which conditions each path scores, and the weighting remains your committee's decision.
Verifiable requirements. Each of the 25 requirements comes with the evidence to request, and all of them also apply to native SharePoint alone.
A cost presented as a range. The five-year grid excludes the Microsoft 365 licenses you already own and presents each path in a low and a high scenario, rather than as a single figure.
Obligations cited with their sources. Data residency commitments, personal data rules in France and Quebec and accessibility requirements are taken from published sources, with what they mean for the project.



.webp)
