In short
A SharePoint intranet gets used when you build it around a few tasks people already need to do, not around the org chart. Start with one pilot scenario and a business metric, set up the home site, global navigation and hubs so news flows to the right place, plan design work where SharePoint is weakest, and launch in waves. Then measure use by department and country against the metric you set at the start.
Key takeaways
- Microsoft’s own intranet guidance says to judge initiatives by business impact, not only by system metrics such as news post views.
- A home site is a communication site with intranet-wide search, official organisational news and global navigation in the SharePoint app bar; from July 2026 you set it in the SharePoint admin center.
- Hub news flows up from associated sites to the hub, never down, and a site can belong to only one hub out of up to 2,000.
- In Tryane’s Digital Workplace Benchmark 2026, SharePoint scored 68/100, with 2/5 on Look and Feel, Customizable User Interface and Analytics / Insights, but 5/5 on Interoperability.
- The Portal launch scheduler releases a portal in waves of one to seven days, scheduled at least seven days ahead, after the home page passes Page Diagnostics.
Why build your intranet on SharePoint at all?
If your organisation runs on Microsoft 365, SharePoint is already there. Your employees sign in with the same account they use for Outlook and Teams, documents they open from the intranet are the same files they co-author every day, and every new team in Microsoft Teams automatically gets a SharePoint site behind it. That integration is SharePoint’s strongest argument, and it is also why the intranet project is rarely about the platform choice: it is about what you build on it.
Microsoft’s view is that with SharePoint in Microsoft 365, anyone can create intranet pages without writing code, and the pages work on any device.[1] That is true, and it is also the trap. Because building pages is easy, many SharePoint intranets grow site by site until nobody can find anything, and the home page becomes a list of links to departments. The rest of this guide is about avoiding that: deciding what the intranet is for, laying out the structure so news and navigation reach people, and launching it so employees actually come back.
Step 1: What should you decide before building anything?
Start with the organisation’s priorities, not with the look book. Microsoft’s planning guidance makes the point directly: the most successful intranets are focused on helping people get work done, and an intranet aligned with strategic goals is the one that gets the right level of funding. It also recommends reading recent employee survey results to find the pain points people already report.[1]
Then do four things in order.
- Write personas. New starter, office worker, field worker, people manager, content author. Talk to people who fit each one. Site owners alone are not enough, because what they want to publish is often not what their readers want to find.
- Inventory what you have. List existing sites, their owners and how current their content is. You do not have to migrate everything; Microsoft notes that writing new content for the modern experience is often more effective than moving out-of-date pages. A focus group of people who joined in the last two or three months will tell you what is missing.
- Agree governance early. Who can create sites, who is accountable for content, how often content is reviewed, and whether intranet content falls under your retention or sensitivity policies. These decisions are easier to make at the start than to enforce later.
- Pick one pilot scenario. Rank candidate initiatives by whether they solve a real problem, how many people they reach, whether they can be built in a reasonable time, and the return. Microsoft’s criteria for a good pilot: you can build a prototype in a few days, there is a committed sponsor, there is enough up-to-date content, and there is a specific audience.[1]
For the pilot, set two metrics before you build: a system metric that the platform can count, and a business metric your sponsor cares about. Microsoft’s own examples pair them like this.
| Pilot scenario | Business owner | System metric | Business metric |
|---|---|---|---|
| Benefits site: explain employee benefits | HR | News post views, training video views | Help requests reduced by x% |
| Leadership community: build agreement on strategy | HR | Monthly posts by leaders and comments by employees | Comments answered within 24 hours; x% rise in satisfaction with executive communication |
| Marketing site: faster proposals | Marketing | Slide downloads | x% less time to create a proposal |
The table is adapted from Microsoft’s planning article.[1] Fill in the x before launch. If you cannot name the business metric, the scenario is not ready to be a pilot.
Step 2: How do home site, navigation and hubs fit together?
A modern SharePoint intranet is flat: instead of subsites nested inside each other, it is a set of separate sites connected by hubs, roll-up web parts and navigation.[2] That means you can move a site from one area to another without breaking links when the organisation changes. Four building blocks do most of the work.
| Building block | What it does | Decision to make |
|---|---|---|
| Communication site | Shares news, reports and information with a broad audience; few authors, many readers | Which topics deserve their own site |
| Home site | A communication site set as the intranet’s landing page, with intranet-wide search and official organisational news | Which site becomes the front door, ideally the root site |
| Hub site | Groups related sites with shared navigation, branding, search scope and news roll-up | Which families of sites need a hub: HR, IT, a region |
| Global navigation | Intranet links in the SharePoint app bar, visible on every modern SharePoint site | The handful of destinations everyone needs |
Set up the home site as the front door
A home site is a communication site with special capabilities. Its search covers the whole intranet rather than one site, news published from it automatically becomes official organisational news and takes priority on the SharePoint start page, and it unlocks global navigation in the SharePoint app bar. Microsoft recommends swapping your chosen communication site into the tenant’s root site location before setting it as the home site, because doing it the other way round can lose the home site settings. As of July 2026, you set the home site in the SharePoint admin center.[3]
Use the home site for what is relevant to everyone: company news, the top tasks from your personas and links to the high-traffic portals such as HR. Microsoft also recommends turning on audience targeting for navigation links, news and certain web parts, and a page approval flow so only reviewed content is published there.[3]
Keep global navigation short
Global navigation can only be enabled and customised from the home site, by someone with site owner permissions, and changes can take up to 24 hours to reach users. Audience targeting works on its menu links. It also matters for Teams: global navigation must be enabled for SharePoint resources to appear in the SharePoint app in Teams (formerly Viva Connections).[4] Treat it as the list of destinations everyone needs, not a copy of the org chart.
Use hubs for families of sites, and publish news where it should travel
An organisation can have up to 2,000 hub sites, a site can be associated with only one hub, and hub navigation can go three levels deep. When a site joins a hub, it takes on the hub’s theme and navigation, its content rolls up into the hub’s web parts and it enters the hub’s search scope. Roll-up is security trimmed, so people only see content they already have access to.[5]
The rule internal communicators most often miss is the direction of news. Microsoft is explicit: news does not flow down to associated sites, only up from the associated site to the hub. If you want the broadest reach for a story, publish it on the hub, or on the home site for organisation-wide news.[5] A story posted on a regional team site reaches the regional hub, not the whole company. Our article on why SharePoint news goes unread covers what this does to readership.
Step 3: Where does SharePoint need extra design work?
SharePoint is a strong base, but it is not designed first and foremost as an internal communication platform. Tryane’s Digital Workplace Benchmark 2026, which scores 12 intranet and employee communication platforms based on demos, expert interviews and public data, gave SharePoint an overall Tryane Score of 68/100, the lowest of the 12. Its category scores were 65% for UI/UX, 72% for Publishing, 72% for Targeting, 88% for Administration and 45% for Analytics. On individual criteria, SharePoint was rated 2/5 on Look and Feel, Customizable User Interface and Analytics / Insights, and 5/5 on Interoperability with Other Environments, Admin Role Management and Ease of Authentication. The report’s summary: a must-have platform that requires customisation to be truly effective for internal communication. Download the full Digital Workplace Benchmark 2026 to compare SharePoint with the other 11 platforms criterion by criterion.
Read that as a planning list, not a verdict. The weak spots tell you where to spend design time before launch.
- Look and feel. Budget for a proper theme, a header and footer, and page templates for news, events and policies, so pages look like one intranet rather than 40 sites. Start the home site from a template such as Microsoft’s Organization home template and adapt it.[3]
- Customisable interface. Decide which web parts authors may use on which page types. Fewer choices give a more consistent experience and faster publishing.
- Targeting. Specific audience targeting and adapting content to profiles were rated 3/5 in the benchmark. Set up the Microsoft 365 groups you will target before you need them, because targeting is only as good as the groups behind it.
- Analytics. Native reporting is the weakest area. Decide now how you will report on the business metric from Step 1, because site usage numbers alone will not answer it.
Step 4: How do you launch without a quiet go-live?
A new intranet that appears overnight with one email tends to get one visit. Plan the launch as a communication campaign with a technical roll-out underneath it.
Check health, then roll out in waves
Before you schedule anything, run the Page Diagnostics for SharePoint tool on the home page: the Portal launch scheduler will not let you continue until the page has a healthy score. The scheduler then releases the portal to batches of users in waves, manages redirects and lets you pause between waves to fix problems. Launches must be scheduled at least seven days in advance, and each wave lasts one to seven days.[6]
| Expected users | Waves set by the scheduler |
|---|---|
| Fewer than 10,000 | Two |
| 10,000 to 30,000 | Three |
| More than 30,000 up to 100,000 | Five |
| More than 100,000 | Five, plus contact Microsoft support |
If the new portal replaces an old one, use the bidirectional redirect: people in launched waves go to the new site even from the old address, and people in later waves are sent back to the old site until their turn. Permissions are separate from waves, so grant access first; adding a security group to a wave does not give it access to the site.[6] Use the waves for communication too: put a few of your champions and a friendly department in the first wave, and collect their feedback before the next.
Make it easy to find
Add the home site to the Microsoft 365 app launcher and as a featured link on the SharePoint start page, and announce it with a SharePoint news post that you also share by email and in Teams.[3] Then work from both ends: Microsoft recommends executive sponsors who explain why the intranet matters, champions across the organisation, launch events, training and regular office hours.[1] Bring your help desk in before the first wave so they can answer questions.
Step 5: How do you know employees use the intranet?
Go back to the metrics you set in Step 1. The system metric tells you whether people arrive; the business metric tells you whether the intranet changed anything. Both need a baseline taken before launch.
SharePoint’s native site usage page gives site owners unique viewers, site visits, average time spent per user, popular content, traffic by hour and traffic by device, over the last 7, 30 or 90 days, and lets owners export 90 days of data to a CSV file. Popular content covers only the last seven days, and the most recent 60 minutes of activity are not yet included.[7] That is enough to see whether the home site is visited. It does not tell you which departments, countries or sites are reading your news and which are not, and it does not keep a history beyond the window.
So track a small set of measures every month, from day one:
- Reach by audience: the share of each department and country that opened the home site or a news post, against headcount, not against visitors.
- News readership: how many people read each organisational news post, and whether hub news reaches beyond the hub.
- Task completion: the business metric from your pilot, such as fewer help requests or faster proposals.
- Returning use: whether people come back after the launch month, by wave.
Our guide to healthy SharePoint intranet adoption rates gives reference points, and measuring the impact of a SharePoint redesign explains how to compare before and after. This is the gap Analytics for SharePoint fills: it reads your SharePoint sites and news, joins readership to your organisational structure and keeps the history, so you can report reach by department and country in one place and decide what to change next. To see what that report looks like for your intranet, book a 15-minute call with Jérémy.
Frequently asked questions
Is SharePoint a good choice for an intranet?
For organisations on Microsoft 365, usually yes, because it shares sign-in, files and Teams with the tools people already use. Tryane’s Digital Workplace Benchmark 2026 rates SharePoint 5/5 on interoperability but 2/5 on look and feel, interface customisation and analytics, so plan design and measurement work on top of it.
What is the difference between a home site and the SharePoint start page?
The SharePoint start page is personalised for each user by Microsoft Graph, based on their recent activity, followed sites and saved items. The home site is a landing page you design for the whole organisation, with universally relevant news and links. You cannot merge them, but you can add the home site as a featured link on the start page.
Should I use one hub or several?
Nothing requires more than one hub, but with a single hub you lose the ability to group related content in context and to set a search scope for a family of sites. Most intranets use hubs for major functions such as HR, Finance or IT, or for regions. Remember that a site can join only one hub.
Why does news from a team site not appear on the home page?
News rolls up from associated sites to their hub, not down and not sideways. A post on a departmental site reaches its hub only if the hub’s news web part includes it. For company-wide reach, publish on the home site or another official organisational news source set in the SharePoint admin center.
How long does a SharePoint intranet launch take?
The technical roll-out alone needs at least a week of lead time: the Portal launch scheduler requires launches to be booked seven days ahead, and each wave lasts one to seven days. Planning, the pilot and content preparation come before that, and the length depends on how much existing content you rewrite.
Can I measure my SharePoint intranet by department?
Not with the native site usage page, which reports viewers, visits, time spent, popular content, time of day and device for one site. To see reach by department or country, you need to join usage data to your organisational structure, either in your own build or with an analytics tool.
Sources
Further reading
• Intranet adoption rate: healthy SharePoint benchmarks
• Measuring the Impact of a SharePoint Intranet Redesign
• What Is an Intranet, and Why the Definition Decides What Your Reporting Can Claim
• Why SharePoint News Goes Unread, and What the Data Actually Shows
• The Limits of SharePoint Native Analytics for Internal Communications
If you want to see what cross-channel reporting looks like against your real data, Tryane runs a 15-minute walkthrough with no slides. Book a slot with Jérémy.
