Opens in a new tab

SharePoint Intranet: What It Does Well, and Where It Falls Short

By Meghana
Published: January 26, 2026
Last Update: November 18, 2026

A SharePoint intranet is an internal site built on SharePoint Online, which is included with most Microsoft 365 plans. It handles news, documents, policies and team sites well. It does not arrive ready-made. You get a platform and a set of parts, not a finished intranet, and the build and the governance are where the real cost sits.   

Key takeaways

  • SharePoint is already in your licence. Business Basic and up include SharePoint Online. You are not buying an intranet, you are building one.
  • The platform is free. The intranet is not. Information architecture, build, content and ongoing ownership are the real cost.
  • Viva Connections was renamed in 2026. It is now the SharePoint app in Teams, and core intranet features moved into standard Microsoft 365 plans.
  • It cannot fix a weak foundation. Surfacing a disorganised intranet inside Teams shows the same problems to more people.
  • Copilot makes governance non-optional. It surfaces stale policies and overshared files in seconds, which is a reason to fix content before deploying it.

Can SharePoint be used as an intranet?

Yes, and most organisations running Microsoft 365 already have everything they need to start.

SharePoint Online is included in Microsoft 365 Business Basic, Business Standard, Business Premium, and the enterprise plans. You do not buy an intranet separately. You build one from communication sites, hub sites and team sites that are already in your tenant.

The catch sits in that one word: build. SharePoint gives you the parts. It does not give you an intranet. What separates a working intranet from a folder structure with a homepage is information architecture, governance and somebody who owns it.

What a SharePoint intranet includes

A SharePoint intranet usually brings together six things.

Area What SharePoint provides
Company news Communication sites, news posts, audience targeting by role, department or location
Documents and policies Document libraries with versioning, metadata, retention and co-authoring
Team and department sites Team sites linked under hub sites, each with their own permissions
Search and people Tenant-wide search across sites, documents and people directories
Workflow Power Automate for approvals, requests and notifications
Security and compliance Role-based permissions, data loss prevention, audit logging and eDiscovery

The question most organisations should ask is not whether SharePoint can do this. It is whether anyone has been given the time to set it up and keep it current.

The 2026 change: Viva Connections is now the SharePoint app in Teams

This is recent enough that a lot of guidance on SharePoint intranets predates it.

Microsoft renamed Viva Connections during 2026. It is now the SharePoint app in Teams, with the rollout completing across production tenants by the end of June 2026.

Two practical changes came with it. Administrators can now create and designate home sites directly from the SharePoint admin centre. And two new web parts, Resources and Announcements, are available on home sites.

On licensing, the app is included with Microsoft 365 plans including E3, E5, F1 and F3 at no extra cost. Running several targeted experiences still needs the Viva Suite.

What the app does has not changed. It is a delivery layer, not an intranet. It surfaces SharePoint content inside Teams, including on mobile. It creates no content of its own and manages no documents.

That matters because it cannot fix a weak foundation. If your sites are fragmented or your content is out of date, turning it on puts the same problems in front of more people.

SharePoint as an intranet platform: where it falls short

SharePoint is still the right answer for most organisations already running Microsoft 365. It also has real limits, and those are less often spelled out.

Product documentation covers what SharePoint can do. What it will not do without more work or more licensing is harder to find in one place, so here it is.

Limit What it means in practice
Nothing is ready-made You get building blocks. Branding, navigation and page design are all configuration work before launch
Everyone needs a licence Anyone without a Microsoft 365 licence, such as contractors or volunteers, needs guest access configured rather than simply logging in
Analytics are basic by default Reactions, click-through and a full year of page data need a Viva licence on top
Deep branding needs development Matching a corporate brand closely usually means the SharePoint Framework, which is a development exercise
Adoption is not automatic A well-built intranet still fails if nobody owns the content after launch
It depends on Teams usage Reaching people through the SharePoint app in Teams assumes they are in Teams. For frontline-heavy organisations that is not a given

What a SharePoint intranet costs to run

It depends on what you count, and most answers count too little.

SharePoint Online itself is included in your Microsoft 365 plan. So is the core intranet experience in Teams, since the 2026 licensing change. On that basis it looks free.

Three things sit outside that.

The build is the largest. Information architecture, site structure, branding, navigation, content migration and permissions all take time. Someone does that work, whether it is your team or a partner. A third-party intranet product bundles it into the subscription. SharePoint does not.

Some capability needs more licensing. Deeper page analytics need a Viva licence. That means reactions, click-through and a full year of data. Microsoft 365 Copilot is a separate per-user add-on and is not in E3 or E5.

Then there is the part nobody budgets for. Somebody has to own the intranet after launch. Content goes stale fast, and a stale intranet is worse than none, because people stop trusting it and go back to asking each other.

The useful comparison is not licence against licence. Count your total over three years, including the build and somebody’s time to run it. Then compare that with a vendor subscription that includes both.

Microsoft 365 intranet options

There are three realistic routes inside Microsoft 365, and they are layers rather than alternatives.

Option What it is When it fits
SharePoint communication site A single site, built from templates, with news and document libraries Small organisations, or a first step before a full build
SharePoint with hub sites Multiple sites unified under hubs, with shared navigation and search Most organisations. This is the standard modern intranet pattern
SharePoint plus the SharePoint app in Teams The above, surfaced inside Teams and on mobile When you need to reach frontline or deskless staff who live in Teams, not a browser

Copilot sits across all three rather than being a fourth option. It changes how people find content. It does not change what is there, and it will surface whatever governance you have, or have not, put in place.

SharePoint or a third-party intranet platform?

If your organisation runs on Microsoft 365, SharePoint is almost always the right foundation. The cases where a third-party platform wins are specific and worth knowing.

  SharePoint Third-party intranet platforms
Access Needs a Microsoft 365 licence per user, or guest access Often unlimited users, including staff without email addresses
Setup Configuration and build work before launch Usually ready to use, with templates out of the box
Customisation Extensive, through SharePoint Framework and Power Platform Simpler, but with a lower ceiling
Integration Native across Teams, Outlook, OneDrive and Power Platform Broader third-party integration, better for mixed toolsets
Cost shape Licence is included, build and ownership are not Subscription that usually includes the build
Adoption Depends heavily on how well it is built Often faster, since the design work is done

A third-party platform is worth considering in three cases.

  • You have a large frontline workforce without Microsoft 365 licences
  • You need an intranet live in weeks rather than months
  • You have no internal capacity to own it

Outside those, you are paying a subscription for something your licence already covers.

Planning and building a SharePoint intranet

Start with the people, not the platform. Map who needs the intranet, what they need from it, and on which device. Frontline staff on phones have different needs from head office on desktops.

Then design the structure before you build anything. Decide your hub sites and how departments sit under them. A flat set of unrelated sites is the most common and most expensive mistake, because search and navigation both depend on that structure. When we are called in to fix an intranet nobody uses, this is almost always where it went wrong.

Set governance at the start, not after launch. Decide who can publish, who owns each page, and when content gets reviewed. This matters more than it used to. Copilot does not create governance problems. It makes them impossible to ignore, because it surfaces outdated policies and overshared files in seconds.

Two links belong in this paragraph: SharePoint security and governance mistakes, and getting SharePoint ready for Copilot. Both slugs confirmed 2026-10-23, see section 5.

Build small and expand. A homepage, a news feed, a policy library and two department sites, done properly, beat a twenty-site launch nobody maintains.

Then launch it where people already are. Enable the SharePoint app in Teams so the intranet reaches mobile and deskless staff without asking them to visit a separate site.

The bottom line

If you already pay for Microsoft 365, SharePoint is the right foundation for your intranet. That part is not a close call.

The close call is whether you have the capacity to build it and keep it current. The licence is the cheap part. The structure, the content and the ownership are the expensive parts, and they decide whether anyone uses it.

Before you start, settle three things: who owns the intranet after launch, what the hub structure looks like, and how content gets reviewed. Get those right and the build is straightforward. Skip them and no amount of configuration will save it.

Frequently asked questions

An intranet is the thing you are building, an internal site for news, documents and team spaces. SharePoint is a platform you can build it on. Most Microsoft 365 organisations build their intranet on SharePoint, which is why the two words often get used as though they mean the same thing.

Yes, and arguably more so than before. Microsoft moved core intranet features into standard Microsoft 365 plans during 2026 and positioned SharePoint as the content layer underneath Teams and Copilot. The relevant question now is not whether SharePoint is current. It is whether your content is organised well enough for Copilot to use.

Through a browser at your organisation’s SharePoint address, or through the SharePoint app in Teams, which was called Viva Connections until the 2026 rename. The Teams route is usually better for mobile and frontline staff. Your IT team or provider sets which site is the home site.

Yes, for normal access. Anyone without a licence, such as a contractor or volunteer, needs guest access set up instead, which is more limited and has to be managed. For organisations with a large unlicensed frontline workforce, this is the point where a third-party platform becomes worth pricing.

Talk to us about your intranet

If you are planning a SharePoint intranet, or you have one that nobody uses, the fix usually starts with structure and ownership rather than design. We can look at what you have and tell you which it is.

Book an intranet review →

Meghana

Content Strategist & Blogger
Meghana is a digital marketer with over 8 years of experience helping brands grow through SEO and storytelling. She writes about marketing trends, productivity, and the future of work. When she’s not writing, she enjoys hiking and photography.

Contact Us

Fill out the form below to get details

Fill out the form below to get details

Fill out the form below to get details