Most companies on Microsoft 365 already own everything they need for a good intranet — and still end up with a SharePoint start page nobody opens. This guide covers what a modern SharePoint intranet should contain, how to structure it, how to launch it and how to keep people using it.
What is a SharePoint intranet?
An intranet is the internal website of a company: the place for news, policies, people and the tools employees need to do their work. A SharePoint intranet is an intranet built on SharePoint Online, which is included in most Microsoft 365 business and enterprise plans.
A modern intranet is no longer a static wall of links. It is personalised, mobile-friendly, connected to Teams and Outlook, and maintained by communicators and department editors rather than by IT.
Why build your intranet on SharePoint?
- You already pay for it. SharePoint Online is part of Microsoft 365, so there is no separate intranet platform to license for basic capabilities.
- Single sign-on and security. Employees use the same Microsoft account; permissions, compliance and data residency follow your existing Microsoft 365 policies.
- Documents are already there. Policies, forms and templates live in SharePoint and OneDrive anyway — the intranet simply makes them findable.
- Teams and mobile. With Viva Connections the intranet appears inside Teams on desktop and mobile; the SharePoint mobile app covers news and pages on the go.
- Search. Microsoft Search indexes intranet pages, documents and people in one place, and Copilot (where licensed) can answer questions from intranet content.
What a good intranet home page contains
Company news
Featured stories with images, published by communications and departments — the main reason people come back.
Events
Town halls, trainings and company events in a clear card or calendar view.
Quick links and tools
One-click access to the systems people use daily: HR portal, help desk, CRM, expense app, booking tools.
People
Employee directory, new joiners, birthdays or anniversaries, and recognition such as an employee spotlight.
KPIs and announcements
A few company-wide numbers or goals, plus urgent announcements that need to reach everyone.
Policies and documents
The current version of every policy, form and template — with an owner and a review date.
Department pages
HR, IT, finance, facilities: who they are, what they offer and how to request it.
Services and requests
Clear entry points to request IT help, leave, equipment or facility support.
How to structure a SharePoint intranet
Use communication sites and a hub
Create the home page as a communication site and set it as the organisation's home site. Give each department its own communication site and associate them with a hub site, so they share navigation, branding and search. Keep collaboration (project work, team files) in Teams and team sites — not on the intranet.
Navigation by task, not by org chart
Employees look for “request leave” or “expense policy”, not for “HR department, subsection 3”. Build the main navigation around tasks and topics, and test it with a few employees before launch.
Audience targeting
Use Microsoft 365 groups to target news, links and navigation to locations, departments or roles, so each employee sees what is relevant to them.
Metadata and search
Tag documents and pages with consistent metadata (document type, department, owner, review date). It makes search, filtering and content reviews dramatically easier.
Bringing the intranet into Microsoft Teams
Viva Connections places your SharePoint intranet inside Teams with a dashboard of cards, a personalised news feed and links to your intranet resources. The basic Viva Connections experience is included with Microsoft 365, which makes it the simplest way to reach employees who live in Teams all day — including frontline staff on mobile.
Four ways to build a SharePoint intranet
| Out-of-the-box SharePoint | Ready-made intranet | Custom development | SaaS intranet | |
|---|---|---|---|---|
| What it is | Standard pages and web parts, configured internally | Pre-built intranet components deployed into your tenant | Intranet designed and coded from scratch (SPFx) | Separate intranet product connected to Microsoft 365 |
| Look and feel | Standard SharePoint | Branded, designed components | Fully custom | Vendor templates |
| Speed | Depends on internal capacity | Fast | Slowest | Fast |
| Cost model | Internal time | Usually fixed project price | Highest project cost | Per-user subscription |
| Where content lives | Your tenant | Your tenant | Your tenant | Often partly in vendor cloud |
Ready-made intranets — sometimes called “intranet-in-a-box” — add designed components such as news layouts, KPI tiles, events, employee spotlight and quick-link launchpads on top of SharePoint. Flex Intranet is our example of this approach: eleven SharePoint web parts that editors arrange without IT.
An 8-step plan to launch your intranet
- Set goals and stakeholders. Agree what the intranet must achieve (e.g. fewer “where do I find…” questions) and who owns it — usually internal communications plus HR and IT.
- Audit existing content. List what exists, what is outdated and what is missing. Delete or archive before you migrate.
- Design the structure. Home site, department sites, hub, navigation and audiences.
- Brand and build. Apply your theme, logo and page layouts; configure the home page components.
- Assign owners and editors. Every site and every key page gets a named owner.
- Define governance. Who can publish what, how often content is reviewed, how new sites are requested.
- Pilot. Test with 20–50 employees from different departments and fix what confuses them.
- Launch and drive adoption. Announce it from leadership, add it to Teams, set it as the browser start page, and publish news from day one.
Timeline: a standard Flex Intranet rollout typically takes 5–10 business days. The actual timeline depends on scope — number of departments, content migration, integrations — and is confirmed after a short discovery workshop.
Governance that keeps the intranet alive
- Roles: intranet owner, site owners per department, editors and an IT admin.
- Publishing rules: who may publish company-wide news versus department news.
- Content lifecycle: every policy and key page has a review date; outdated content is archived.
- Site creation: new intranet sites are requested and approved, not created ad hoc.
- Permissions: read access for everyone, edit access through groups — never item by item.
Seven ways to make employees actually use it
- Publish news at least weekly — a stale home page is the fastest way to lose readers.
- Put the intranet in Teams with Viva Connections.
- Make it the default browser start page on company devices.
- Link every daily tool from the home page so it becomes the starting point of the workday.
- Recognise people: new joiners, anniversaries, employee spotlight.
- Let departments own their pages instead of routing every change through IT.
- Ask for feedback after 30 days and show what you changed.
How to measure intranet success
- Unique visitors and page views from SharePoint site usage analytics
- Share of employees who visit at least once a week
- News reach: views per article in the first week
- Search queries with no result — they show missing content
- Fewer repeated questions to HR and IT
Common intranet mistakes
- Mirroring the org chart instead of employee tasks.
- Migrating every old document “just in case”.
- Launching without owners and a news plan.
- Mixing collaboration files and published content on the same sites.
- Measuring success by launch date instead of usage.
Frequently asked questions
See Flex Intranet running in your tenant
Book a free demo — we will show you a modern SharePoint intranet live in Microsoft 365 and map it to how your company communicates.
Book a demoAbout Flex Intranet