The SharePoint Intranet Guide: features, use cases, costs and how to actually make it work.

Intranets have had a rough reputation. For years, they were the digital equivalent of the office noticeboard no one reads — somewhere policy PDFs went to die. In 2026, the SharePoint intranet looks very different. It's become the connective tissue of Microsoft 365: the front door to Teams, Copilot, OneDrive, Viva and the rest of the stack. Get it right, and it's the single most useful piece of software in your business. Get it wrong, and you've built a very expensive document library.

This guide is the result of hundreds of SharePoint conversations we've had with UK businesses — from 15-person construction firms to 2,000-seat enterprises. It covers what a modern SharePoint intranet actually is, the features worth paying attention to, the use cases that land, the honest benefits, what it costs in 2026, and how to avoid the most common pitfalls.

01 What a SharePoint intranet actually is in 2026

Strip away the jargon and a SharePoint intranet is a private, branded set of websites your employees use to find information, collaborate and get work done. What makes it different from a plain old website is that it's wired directly into the rest of Microsoft 365. Every document opens in Word, Excel or PowerPoint online. Every team has a matching Teams workspace. Every page can be personalised to the individual viewing it. And in 2026, every piece of content is indexable by Microsoft 365 Copilot, which is where things get genuinely interesting.

Structurally, a modern SharePoint intranet is built from three things. There's a home site — your front door, typically themed to your brand and showing company news, tools and personalised content. There are hub sites, which group related departments or functions together (think "HR hub" or "Projects hub"). And underneath those sit communication sites (for broadcast-style content) and team sites (for day-to-day collaboration). You don't need to memorise the taxonomy — just know that it lets you scale from a 20-person agency to a 50,000-seat enterprise without rebuilding.

The other thing worth knowing upfront: SharePoint isn't a separate product you go and buy. It's already sitting inside the Microsoft 365 licences most businesses pay for. That changes the economics of intranet projects fundamentally, and we'll come back to that later.

02 The core features worth knowing about

SharePoint's feature list is long enough to fill a book. Here's the short version of what actually matters when you're planning an intranet in 2026.

News, pages and the home experience

Out of the box you get a drag-and-drop page builder with a library of web parts — news, events, Viva Engage conversations, people cards, embedded documents, video, countdowns, call-to-action buttons and dozens more. Pages render beautifully on mobile without extra work. News posts can be boosted (promoted across the tenant), scheduled and audience-targeted so that warehouse staff never see a message meant for HQ marketing.

Search that finally works

Microsoft Search indexes everything your users have permission to see — SharePoint pages, Teams chats, Outlook emails, OneDrive files, third-party apps through connectors — and returns results in one place. The 2026 iteration uses semantic ranking and natural language, so an employee can type "how do I book leave" and get the policy, the form, and the HR contact, rather than a list of filenames.

Integrated document management

Every intranet site is also a fully-featured document management system. Versioning, co-authoring, check-in/check-out, retention labels, sensitivity labels, e-signature via Adobe or Docusign, and automatic records management. Libraries can be configured with metadata and views so a contracts library, for example, automatically sorts documents by client, renewal date or status. This is where a well-designed, metadata-driven library beats a folder-based one every time.

Copilot and Viva

This is where 2026 differs most from 2023. Microsoft 365 Copilot sits on top of SharePoint and can answer questions grounded in your intranet content. Ask "what's our expenses policy for overseas travel?" and Copilot will pull from the policy page with citations. Viva adds modules on top — Connections (the intranet mobile app), Engage (social), Learning (LMS), Insights (wellbeing analytics) and Topics (AI-generated topic pages). You don't need all of them, but knowing they're there informs architecture decisions.

Automation with Power Platform

Power Automate and Power Apps plug directly into SharePoint lists. That means your intranet doesn't just display information — it runs processes. Leave requests, onboarding checklists, IT tickets, approval flows, visitor bookings, expense claims, project summary sheet generation. For most SMBs, 80% of the "workflow apps" they think they need to buy as SaaS products can be built on top of SharePoint in a couple of afternoons.

Governance, security and compliance

Permissions inherit from Microsoft Entra ID (formerly Azure AD), which means single sign-on, conditional access, multi-factor authentication and device compliance all apply without extra setup. You get data loss prevention, sensitivity labels that travel with documents, eDiscovery for legal holds, and immutable retention. For regulated industries — finance, healthcare, legal, construction, public sector — this is usually the deciding factor.

03 Real-world use cases: what people actually build

Rather than list every theoretical use case, here are the patterns we see land most often in real NetMonkeys deployments.

The company home and news hub

The most common starting point. A branded landing page with CEO updates, department news, events, policies and quick links. Done well, it replaces the "all staff" email blast entirely, which tends to produce a visible drop in email volume within a month or two. Audience targeting means regional teams see regional content; leadership sees leadership content.

HR and people operations

The second-most common build. Policies, benefits, leave booking, expenses, training, onboarding journeys, org chart, people directory. Modern deployments fold in Viva Learning so training content appears in context, and Copilot answers policy questions conversationally instead of forcing employees to read a 30-page PDF.

Project and client workspaces

Each project or client gets a Teams-linked site with a metadata-driven document library, task list, meeting notes and a status dashboard. Templates mean new projects spin up in minutes with consistent structure. Consulting firms, agencies, construction and engineering businesses get the most leverage here — we frequently see project handover times drop from days to hours once the template is right.

Frontline and deskless workforce

Retail, logistics, manufacturing and healthcare businesses have historically been the worst served by intranets because their staff don't sit at desks. The Viva Connections mobile app — which is just your SharePoint intranet in an app wrapper — has changed that. Shift handover notes, safety bulletins, equipment documentation and two-way feedback all work on a phone over 4G.

Knowledge base and IT service

A well-tagged SharePoint knowledge base, exposed through Microsoft Search and answered through Copilot, is a credible internal help desk. Combined with Power Virtual Agents for triage, it can deflect a meaningful slice of tier-1 IT tickets before they ever reach a human.

Governance, risk and compliance

Policy management, controlled-document libraries (ISO 9001, ISO 27001, GDPR registers), audit trails, mandatory read-and-sign workflows. Regulated organisations increasingly use SharePoint as the system of record because of how well the compliance and retention features integrate with Purview.

04 The benefits, honestly

Intranet vendors will list thirty benefits on their homepage. Realistically, here's what you should expect from a well-built SharePoint intranet — and what's hype.

Things you can actually bank on

Faster access to information. If your search and information architecture are competent, employees find things in seconds instead of minutes. Across a 500-person business, the compounding time saving is real — often quoted around 20 to 30 minutes per person per week in surveys, though your mileage will vary.

Lower software sprawl. Many organisations discover they're paying for three or four SaaS products (a separate intranet platform, a document system, a workflow tool, a policy manager) that SharePoint already covers. Consolidation usually saves more than the intranet project costs.

Security and compliance consolidation. Putting content inside Microsoft 365 means one identity, one audit trail, one data loss prevention policy. For anyone who's ever tried to run eDiscovery across five disconnected systems, this alone is transformative.

A platform for AI. Copilot is only as good as the content it's grounded in. A structured, well-permissioned SharePoint intranet is effectively a pre-built knowledge graph for your AI assistant. Organisations without one are finding their Copilot rollouts underwhelm.

Things that are oversold

"It'll improve employee engagement." Maybe. An intranet is a tool — engagement comes from leadership, culture and communication habits. A good intranet can amplify a good culture; it won't fix a bad one.

"It'll break down silos." Silos are organisational, not technical. Giving siloed teams a shared platform is necessary but not sufficient.

05 What it actually costs in 2026

This is usually the first question and the hardest one to answer cleanly, because SharePoint pricing sits inside Microsoft 365 pricing, which is bundled with a lot of other things. Here's the shape of it.

Licence costs

SharePoint Online is included in most Microsoft 365 business and enterprise plans. The practical tiers most organisations land on:

Prices shown are indicative list prices for guidance — confirm current figures with your Microsoft partner. If you're already licensed for Microsoft 365 — and roughly 90% of the organisations we work with are — the marginal licence cost of adding an intranet is effectively zero. You're paying for it already; you just aren't using it yet.

Implementation costs

This is where the real spend sits, and it varies enormously. A rough guide:

• DIY / out-of-the-box home site — £0 to £5,000. Suitable if you have an internal champion, basic design skills, and tolerance for a generic look.
• Partner-led SMB intranet (20–200 users) — typically £8,000 to £25,000. Discovery, information architecture, branding, a home site, two or three hub sites, governance setup, training.
• Mid-market intranet (200–2,000 users) — £25,000 to £75,000. Adds custom Power Platform workflows, Viva Connections mobile, migration from a legacy intranet, change management.
• Enterprise programme (2,000+ users) — £75,000 to £500,000+. Multi-country rollouts, multiple languages, custom SPFx development, integration with HRIS and ERP, phased migration.

Ongoing costs

Budget 10–20% of implementation per year for ongoing content governance, small enhancements, Power Platform app lifecycle and quarterly Microsoft feature changes. The biggest ongoing cost is usually human, not technical: someone — ideally an internal communications lead or digital workplace owner — needs to own the thing.

06 Common pitfalls (and how to dodge them)

We've seen hundreds of SharePoint intranets. The ones that fail tend to fail for the same handful of reasons.

Building a technology project instead of a communications one

The single biggest mistake. A SharePoint intranet is 30% technical delivery and 70% editorial, behavioural and organisational change. If the project is owned by IT alone with no internal comms, HR or leadership input, it will launch and die.

Ignoring information architecture

If you skip the boring work of deciding what goes where, how things are tagged, what permissions look like and how content is retired, your intranet becomes a landfill within eighteen months. Spend time on IA early. It's the cheapest thing to do right and the most expensive thing to fix later.

Over-customising

Early SharePoint deployments used to involve heavy custom code (SPFx, master pages, provider-hosted add-ins). In 2026, with modern pages, section templates and Viva, most of that work is unnecessary and actively counterproductive — it fights every Microsoft update. The rule of thumb: use out-of-the-box first, configure second, extend via Power Platform third, and only drop to custom code when nothing else fits.

Treating launch as the finish line

Launch is the starting line. Plan for a content programme, a governance council, analytics reviews and an ongoing enhancement backlog. Intranets that aren't tended to rot faster than any other internal system because the content itself goes stale.

Forgetting the mobile audience

If a meaningful fraction of your workforce is deskless, start with the Viva Connections mobile app in mind and design for it from day one. Retrofitting mobile after the fact is miserable.

Leaving users on File Explorer

A specific pitfall we see constantly: SharePoint gets rolled out, but staff keep using the mapped drive in File Explorer because it's what they know. You haven't actually deployed an intranet — you've deployed a storage location. Addressing this needs a combination of metadata design (so the SharePoint experience is genuinely better, not just different), training, and — sometimes — turning off the old drive.

07 Migrating from a legacy intranet

A good chunk of the SharePoint projects landing on our desk in 2026 aren't greenfield — they're replacements. Usually the incumbent is one of three things: an ageing SharePoint 2016 or 2019 on-premises farm, a standalone intranet-in-a-box product (Interact, Unily, Simpplr and the like), or a wiki that grew into a de facto intranet (Confluence is the usual suspect). Each migration has its own character.

From on-premises SharePoint

Microsoft's own migration tooling — the SharePoint Migration Tool and the Migration Manager in the Microsoft 365 admin centre — handles the heavy lifting for content, permissions, metadata and version history. The trap is assuming the old structure should come across unchanged. It almost never should. On-premises intranets tend to have accumulated a decade of orphaned sites, broken web parts and custom workflows that shouldn't exist in the modern world. Treat the migration as a forced tidying exercise. Bring across roughly 30–50% of what's there; archive the rest.

From a SaaS intranet product

These migrations are usually about contract renewal dates. Your Unily or Interact contract is coming up, you're already paying for Microsoft 365, and the business case writes itself. The content volume tends to be smaller (these platforms discourage dumping), but the visual polish is often higher than the equivalent SharePoint default. Budget real design time so the new intranet doesn't feel like a downgrade on day one. Third-party tools like ShareGate, Tzunami and AvePoint can export content but expect to rebuild page layouts manually.

From Confluence or a wiki

The trickiest migration, because the content model is genuinely different. Wikis are flat and link-heavy; SharePoint is hierarchical and metadata-driven. The honest answer is: don't migrate a wiki one-to-one. Use the move as an opportunity to rewrite the important 20% of pages into proper SharePoint pages with modern web parts, and archive the rest as read-only reference. Copilot will happily index the archive, so nothing is really lost.

08 Measuring whether it's actually working

One last thing most intranet projects skip: deciding, up front, how you'll know it worked. "Launch" is not a success metric. The intranets that prove their worth twelve months in are the ones whose owners agreed on three or four leading indicators on day one and tracked them weekly.

The metrics that matter most, in our experience: monthly active users as a percentage of licensed headcount (aim for 70%+ within six months), average sessions per user per week, search success rate (proportion of searches that result in a click), news readership, and — the most honest one — a twice-yearly employee pulse asking "can you find what you need at work?" Microsoft provides most of the underlying data through SharePoint analytics, Microsoft 365 usage reports and Viva Insights. Exposing those dashboards to the intranet owner so they see them weekly is a surprisingly effective driver of ongoing improvement.

Avoid vanity metrics like "number of pages published". More pages usually means a worse intranet, not a better one. Good intranets are ruthless about retiring content, and the ones with 4,000 pages are almost always worse than the ones with 400.

09 A realistic rollout plan

If you take one thing away from this guide, make it this: build in phases, launch small, iterate. The best SharePoint intranets we've seen didn't ship as a big-bang project. They shipped a minimum-loveable home site, a news feed and an HR hub in eight weeks, then expanded from there.

A reasonable order of operations for a 100–500 person business:

1. Weeks 1–2 — Discover. Short employee survey, stakeholder interviews, content audit of whatever you have today, success metrics agreed with leadership.
2. Weeks 3–4 — Architect. Site structure, navigation, metadata, permissions model, governance plan, brand kit.
3. Weeks 5–8 — Build. Home site, two hub sites (typically HR and Operations or Projects), three to five cornerstone pages, one Power Automate flow to prove the concept, Viva Connections set up.
4. Week 9 — Pilot. Release to a friendly pilot group of 30–50 people, gather feedback, fix the obvious issues.
5. Week 10 — Launch. Coordinated comms campaign with exec sponsorship, training, office hours, and — crucially — a decommissioning plan for whatever it's replacing.
6. Weeks 11+ — Evolve. Monthly analytics review, quarterly feature backlog, content steward network, ongoing training.

10 Is SharePoint right for you in 2026?

Not always. SharePoint is the right answer for the vast majority of Microsoft 365 customers, and almost always the right answer for regulated or larger organisations. It's less obviously the right answer if you're a small business deeply committed to Google Workspace, or if your organisation's needs are so specific (a dealer portal for 5,000 external dealers, say) that a purpose-built product will beat a general one.

For everyone else — which is most businesses — the question isn't really "should we build a SharePoint intranet?" anymore. It's "why haven't we got more out of the one we're already paying for?" In 2026, with Copilot rewarding well-structured content, the cost of not having a good intranet is increasing every quarter.