A SharePoint intranet is an internal website built on Microsoft 365 (formerly Office 365) that gives an organisation one place to find news, documents, people and the tools they use every day. Most SharePoint intranet projects fail on adoption, not technology. The platform is rarely the problem. Whether staff actually use it comes down to four decisions: audience, content, architecture and governance. This guide covers each, drawn from the intranets we build for Australian organisations.
If you are weighing up SharePoint more broadly before committing to an intranet, our guide to SharePoint for business covers where it fits across Microsoft 365.
Table of Contents
What is a SharePoint intranet?
A SharePoint intranet is a centralised internal site built on SharePoint in Microsoft 365 that staff use to read company news, find documents, complete tasks and reach other tools. Microsoft builds it from a few standard parts: a home site, communication sites, hub sites, news and Viva.
The art is arranging those parts around how people actually work.
SharePoint itself is not an intranet. It is the Microsoft 365 platform you build one on. It helps to separate the intranet from a single SharePoint site. A team working on one project has a SharePoint site. An intranet is the front door for the whole organisation, the place everyone starts. According to Microsoft’s intranet planning guidance, the building blocks are communication sites for publishing news and information, a home site (a communication site set as the organisation’s landing page), hub sites to organise and connect related sites, the news web part and Viva for wider engagement. None of these is hard to switch on. The difference between an intranet people use and one they ignore is in how those blocks are chosen and arranged, which is the rest of this guide.
SharePoint intranet vs team sites, communication sites and hub sites
A SharePoint intranet is the whole internal site. Team sites, communication sites and hub sites are the building blocks inside it. Team sites are for a group doing work together. Communication sites broadcast to a wide audience. Hub sites connect related sites with shared navigation and search. The root of a modern intranet is a communication site.
Getting these roles right early matters, because the choice is hard to undo later. The table below sets out what each one is for, who it serves and whether it is connected to a Microsoft 365 group.
| Building block | What it is for | Typical audience | Microsoft 365 Group |
|---|---|---|---|
| Team site | A workspace where a group creates and edits together | A project or department, roughly 5 to 50 contributors | Yes |
| Communication site | Publishing news and information to a broad audience | Most of the organisation, mostly readers | No |
| Hub site | Connective tissue that links related sites with shared navigation, theme and search | Families of related sites | A setting, not a separate site type |
| Home site | The communication site set as the intranet landing page, the front door | The whole organisation | No |
Microsoft’s hub site guidance describes hubs as the connective tissue of an intranet that model relationships as links rather than hierarchy, which is why modern intranets use a flat hub-and-spoke pattern instead of deep nested subsites. One practical trap to know about: you cannot convert a team site into a communication site or back again once it is created, so the site type is a permanent decision. When in doubt about whether a section is for collaborating or for broadcasting, that single question, are we working together or sharing finished information, usually settles it.
Why do most SharePoint intranets fail?
Most SharePoint intranets fail because of adoption, not features. The build works, but staff cannot find what they need, the content goes stale and nobody owns it. The common pattern is a site designed around the org chart instead of daily tasks, no governance and a launch with no plan to keep people coming back.
The problem an intranet is meant to solve is real and getting worse. Microsoft’s 2025 Work Trend Index found that employees are interrupted roughly every two minutes during core work hours, up to 275 times a day and that the average worker receives 117 emails and 153 Teams messages daily. Nearly half of employees, 48%, say their work feels chaotic and fragmented. An intranet that people actually use cuts some of that noise by putting the answer one click away. One they ignore just adds another place to look.
Microsoft’s own research into what makes an intranet succeed points to the same handful of factors every time:
- goals tied to real business outcomes
- an executive sponsor and named champions
- clear measures of success
- a design built for simplicity
- a governance plan
Most failed intranets are missing several of these. The pre-state we see most often is a site organised around the org chart rather than daily tasks, so people cannot find what they need and quietly give up. Independent data points the same way: a 2026 enterprise search survey found that internal search returns the right answer on the first attempt only about 10% of the time, against roughly 95% for consumer search like Google. An intranet that does not make the answer findable is not a SharePoint problem. It is a planning problem and it is fixable.
How to build a SharePoint intranet, step by step
Building a SharePoint intranet that people use follows a clear order: define the outcome, understand the audience and their top tasks, plan content and ownership, design a flat hub-and-spoke architecture, set governance, integrate daily tools, then launch with training and a feedback loop. Skipping the planning steps produces the disconnected sites teams later regret.
- Define the business outcome. Tie the intranet to a measurable goal, such as faster onboarding or fewer “where is the file” questions, not “we need an intranet”. Microsoft’s guidance is explicit that intranet goals should map directly to business outcomes.
- Understand the audience and their top tasks. Map what each role does daily. Microsoft’s advice for planning a site is to design around the reader’s top tasks and the language they use, not just what leadership wants them to see.
- Plan the content and assign owners. Inventory what already exists, remove duplicates and give every section a named owner and a review date. Our SharePoint document management guide covers the metadata and library structure that keep content findable as it grows.
- Design a flat hub-and-spoke architecture. A home site at the front, hub sites as connective tissue, with communication and team sites associated underneath. Avoid deep nested subsites, which are painful to reorganise later. Set up Microsoft Search so people can find a document, a person or a page across every site from one search box, since findability is what keeps people coming back.
- Set governance and permissions before you scale. In SharePoint each site is its own container (a site collection) with its own permissions, so plan access per site rather than leaning on one inherited structure. Decide who can create, edit and publish and set access and retention by role. Governance defined up front is far cheaper than untangling permissions after the fact.
- Integrate the tools people already use. Surface Teams, Power Automate approvals, Power Apps forms and dashboards on the intranet so it becomes where work happens rather than a separate destination. A well-built knowledge base sits naturally alongside this as the place answers live.
- Launch with training, champions and a feedback loop. Name an executive sponsor, recruit champions across teams, set measures of success and review usage so the site keeps earning its place.
What a SharePoint intranet people actually use looks like
A SharePoint intranet people actually use is built around daily work, not the org chart. The homepage surfaces what each person needs that day: their tasks, the news that affects them, the documents they touch and a search that works. When the intranet is the fastest way to get something done, adoption takes care of itself.
In our experience the difference is almost always design, not licensing. We build the homepage around a role’s day rather than the org chart, so the first thing someone sees is the short list of things they actually do: the tasks waiting on them, the news that changes their work, the documents they reach for and one search that returns a person, a page or a file. Where it earns its place we surface the tools people already open, Teams, a Power Automate approval, a Power Apps form or a live dashboard, on the intranet itself, so it becomes where work happens rather than another tab to check. None of that is exotic. It is the standard SharePoint building blocks arranged around how people work instead of how the business is drawn on a chart. Staff use an intranet like that because it is the quickest way to get something done, not because they were told to.
How much does a SharePoint intranet cost to build and run?
A SharePoint intranet runs on the SharePoint licence already included in most Microsoft 365 business and enterprise plans, so the platform itself is usually not a new cost. The real investment is the build: planning, information architecture, design, integration and governance. Cost scales with the number of sites, the integrations involved and how custom the design needs to be.
The main cost drivers are scope, integration and design. A single-department intranet is a small project. A multi-site connected platform with dashboards and automation is a larger phased one. Integrations with Teams, Power Automate, Power Apps or Dynamics 365 add build time, as does migrating and cleaning existing content. Some organisations also add the wider Microsoft Viva suite or a third-party “intranet in a box” product, both of which carry their own per-user licensing on top of the base plan. Building on SharePoint gives more control with no extra licence, while a third-party intranet product buys prebuilt design and features faster at a per-user cost, so for organisations already on Microsoft 365 the platform they own is usually the cheaper starting point. Budget for the build, then keep a smaller ongoing allowance for content ownership and iteration, because an intranet that is never updated is the one staff stop using.
This guide is about planning and building a SharePoint intranet well. If you would rather we design and run yours for you, that is our SharePoint intranets service.
Frequently asked questions
Is SharePoint a good intranet for a small business?
Often, yes. For most small Australian businesses already on Microsoft 365, the SharePoint licence is included, so you are not paying for a new platform. Communication sites, news, search and basic hub structure cover what a small team needs. The trade-off is build effort: a small intranet still needs someone to plan the structure, own the content and keep it current, or it drifts like any other.
Can you use SharePoint as an intranet without buying extra products?
Yes. Out of the box, communication sites, hub sites, the news web part and SharePoint search cover the core of an intranet for most organisations. Products like Viva Connections or third-party “intranet in a box” tools add polish, mobile experiences and prebuilt templates, but they are additions rather than requirements. Many organisations run a capable intranet on the standard Microsoft 365 building blocks alone.
What is the difference between a SharePoint intranet and Microsoft Teams?
Microsoft Teams is for conversation and collaboration, the day-to-day chat, meetings and shared files of a working group. A SharePoint intranet is the published front door for the whole organisation: news, policies, structured content and links to the tools people use. They are designed to work together. Intranet pages and dashboards can be surfaced inside Teams, so staff reach the same content from wherever they are working.
How long does it take to build a SharePoint intranet?
It depends on scope. A focused intranet for a single department, with a clear content set and little integration, can be ready in a few weeks. A multi-site organisation with dashboards, automation and content migration is a phased rollout over several months, usually delivered in stages so each part is in use before the next is built. Planning time is never wasted, it is what prevents the disconnected-sites problem.
How do you improve SharePoint intranet adoption?
Design around what people do most, not the org chart. Give every section a named owner, recruit champions across teams, integrate the tools staff already open daily, train people at launch and review usage so you can fix what is not landing. Adoption follows usefulness. When the intranet is the fastest way to find an answer or complete a task, people use it without being told to.
Can a SharePoint intranet work for staff who are not at a desk?
Yes. The SharePoint mobile app and Viva Connections surface the intranet on phones, which matters for field, clinical and frontline staff who rarely sit at a computer. A mobile-first design, with the most common tasks and news reachable in a tap, is what makes an intranet useful to a clinician between appointments or a worker on a site rather than only to head-office staff.
Build an intranet your team will actually use
A SharePoint intranet earns its keep when it is built around how people work, governed properly and kept current. Get the audience, content, architecture and governance right and adoption follows. Get them wrong and you have another place nobody visits. If you are planning a SharePoint intranet, or trying to rescue one staff have stopped using, book a free initial conversation and we will give you an honest view of what makes sense for your organisation.
