Introduction
“We’re already paying for Microsoft 365 so why invest in an intranet on top of that?” It’s the question that lands on the table as soon as the CFO joins the project. And it’s a fair question. Microsoft 365 easily costs an organisation of 300 employees six figures a year. That budget shouldn’t quietly double because someone, somewhere, thinks the SharePoint homepage “could look a bit sharper”.
The short answer: a Microsoft 365 intranet isn’t included in your licence. You get the building blocks – SharePoint, Teams, OneDrive, Viva – but not a working intranet experience for an organisation of 200, 500 or 1,000 employees. And the gap between those building blocks and what an intranet actually needs to do is exactly where time and money quietly disappear.
In this article we explain what your Microsoft 365 licence does and doesn’t include, the three routes you have to close the gap, and how – as a CFO or Comms Manager – to make an informed choice based on Total Cost of Ownership instead of licence price alone.
What’s in your Microsoft 365 licence (and what isn’t)
Microsoft 365 delivers a set of strong building blocks: SharePoint Online for documents and sites, Teams for chat and collaboration, OneDrive for personal storage, Outlook for email, Viva Engage for social interaction, Stream for video, and Viva Connections as a thin “intranet feel” layer on top of SharePoint.
They’re excellent tools. But they are tools, not an intranet.
The difference comes down to three things:
1. An intranet is an experience, not a collection of apps.
An intranet is where a new hire goes on day one to understand where they work. Where the nurse looks up the updated protocol on her phone between two shifts. Where the manager of a 60-person team posts one message that visibly reaches everyone – including the people without a fixed desk. Microsoft 365 supplies the building blocks for that; it doesn’t supply the ready-made experience.
2. SharePoint is a platform, not a solution.
SharePoint communication sites are powerful, but they start empty. Someone has to design the information architecture, build the templates, set up governance, configure search, manage permissions, deliver the mobile experience and measure adoption. All that work still needs to be done è- just not by Microsoft, but by your own team.
3. Teams and Viva don’t fill the gaps automatically.
Teams is built for collaboration inside a group, not for getting one message in front of everyone in the organisation. Viva Connections adds a dashboard layer on top of SharePoint, but doesn’t replace the full intranet experience (news, events, people directory, onboarding, policies, alerts, analytics).
In other words: your Microsoft 365 licence gives you a workshop full of tools. An intranet is what you build with them – not what comes in the box.
Why organisations think M365 is already an intranet
Three reasons, and all three are understandable:
- Microsoft’s marketing. Microsoft actively promotes Viva Connections as an intranet layer. That’s not wrong – it is a layer – but it’s not a complete intranet solution for an organisation of 200+ employees.
- The “we already have it” reasoning. If finance is already paying for 300 E3 licences, investing extra feels like paying twice. It looks logical at first – until you factor in the hidden costs (see below).
- The homepage illusion. One communication site with a few news posts looks like an intranet. But without targeting, without a mobile app for frontline employees, without analytics and without a maintenance rhythm, within three months it becomes a neglected website nobody visits any more – what the industry calls “Dead Intranet Syndrome”.
The problem isn’t that Microsoft 365 delivers nothing. The problem is that the step from “tools” to “an intranet that works for 300 people” takes work. And that work costs money – whether it sits in an internal IT build project, in an intranet that nobody uses, or in a specialised solution.
The hidden costs of leaving the gap open
Before you spend anything on an intranet, it’s worth looking at what it costs you to not have one that works. Research from Coveo (2025) found that knowledge workers spend an average of three hours a day searching for the right information. Even if you discount that figure significantly and assume just 30 minutes a day, the impact is still substantial:
0.5 hours × 48 weeks × €50 hourly cost × 500 employees = €600,000 per year. Capital that disappears into the search bar, instead of being invested in customers or innovation.
And that’s just search time. On top of that come:
- Onboarding time for new hires who, without a central starting point, spend longer looking over a colleague’s shoulder.
- HR and IT helpdesk tickets that could have been replaced by a solid self-service section.
- Communication that doesn’t reach frontline employees without a fixed workplace, leading to operational errors.
- Knowledge that walks out the door with experienced colleagues because there was no central place to capture it.
So the question for the CFO isn’t “can we afford an intranet?” – it’s “can we afford to keep paying the current cost?“
Three routes to close the gap (and their TCO profile)
You have, broadly speaking, three options to bridge the difference between your Microsoft 365 licence and a working intranet.
Route 1: Custom build on SharePoint (build it yourself or have it built)
Here you take SharePoint Online and have an internal IT team or an external consultancy build the information architecture, templates, governance and customisations. The upside: maximum flexibility. The downside: a sizeable project with a long timeline.
What typically sits inside the 3-year TCO calculation:
- Initial: discovery, design, build, content migration, training (often 3-6 months, sometimes longer)
- Ongoing: maintenance, further development, governance role, adoption work
- Risk: a SharePoint implementation without a clear product end-state tends towards scope creep and overruns
What consultancies charge for this varies widely by market and scope – which is why we won’t put fictional numbers here. What does come back consistently: the licence savings compared to a ready-to-go solution are often wiped out by the build and maintenance costs over three years.
Route 2: Ready-to-go intranet on top of Microsoft 365
Here you pick a solution that sits on SharePoint, uses the same Microsoft 365 tenant, and already brings the information architecture, templates, mobile app and governance with it. Involv intranet is exactly that – an omnichannel SharePoint intranet that brings every department together, running inside your existing Microsoft environment, with all data staying inside your own Microsoft tenant.
What typically sits inside the 3-year TCO calculation:
- Licence for the solution (per employee per year)
- Implementation (shorter timeline than a custom build)
- Ongoing support, updates and new features included in the product
- No migration needed – everything stays inside the existing SharePoint environment
The difference with Route 1 isn’t just in the price but in its predictability. A ready-to-go solution with a fixed scope is easier for finance to budget for than an open-ended build project.
Route 3: Do nothing
This is the most expensive route, and at the same time the one that’s least visible on the budget. You keep paying for your M365 licence, your employees keep searching instead of working, and the cumulative cost of Route 3 over three years exceeds both Route 1 and Route 2 – only spread across invisible lines across different departments (HR helpdesk, productivity, retention).
For an organisation of 500 employees, the projected cost of search time alone runs to €1.8 million over three years (3 × €600,000 – based on the calculation above). And search time is just one of the cost lines.
The four questions every CFO should ask before signing
Before you sign off on a Microsoft 365 intranet investment, these are the questions that make the business case watertight:
- What is the 3-year Total Cost of Ownership?
Not the licence alone, but licence + implementation + maintenance + governance + adoption. Compare that against Route 1 and Route 3. - How quickly do we break even?
An intranet that halves search time, speeds up onboarding and reduces HR tickets often pays for itself within 12 to 18 months for mid-sized organisations – depending on salary costs and organisation size. Run the numbers with an ROI calculator that works on your own figures. - Does our data stay inside our Microsoft tenant?
For finance this is a compliance question, not a tech question. The answer needs to be “yes” – no separate SaaS tenant, no data outside your M365 environment. That’s exactly how Involv intranet works. - What happens if we want to stop after a year?
Ask about contract terms, data ownership and the exit route. A ready-to-go solution on SharePoint has the advantage that your content stays in your own SharePoint – no migration is needed to step away from it.
How to make the difference visible
Want to turn the “we already pay for M365” discussion inside management into a constructive one? Put three things side by side: what your M365 licence delivers today, what a working intranet adds on top, and what the gap is costing you right now – search time, missed communication, and onboarding that takes too long.
Nine times out of ten, the outcome is that the gap is bigger than the solution – and that the real question isn’t whether you close it, but how.
Conclusion: your M365 licence is a foundation, not a building
Microsoft 365 gives you the tools for a digital workplace, not a working intranet. The difference between those two isn’t a luxury spend; it’s the place where search time, onboarding periods and missed communication quietly stack up.
Anyone who wants to make an informed decision – as a CFO or a Comms Manager – looks at Total Cost of Ownership over three years, not at licence price alone. And in that calculation it often turns out that doing nothing is the most expensive option, and that a ready-to-go intranet on top of your existing Microsoft 365 foundation is the most predictable route.
Want to run the numbers on your own figures? Our ROI calculator gives you an estimate in two minutes, based on your organisation size and average salary cost.
Is Microsoft 365 an intranet?
Microsoft 365 provides the building blocks for an intranet (SharePoint, Teams, Viva Connections), but not a ready-made intranet experience. For a working intranet in an organisation of 200+ employees, you need an additional layer or build that brings targeting, mobile access for frontline employees, governance and analytics.
What does an intranet on top of Microsoft 365 cost?
The cost varies by route: custom-building on SharePoint (variable, often 3-6+ months to implement), or a ready-to-go solution with a fixed scope and shorter timeline. An ROI calculator based on your own organisation size gives the most concrete picture.
Does my data stay inside my Microsoft 365 tenant?
With Involv intranet: yes. The intranet runs inside your existing SharePoint environment and all data stays inside your own Microsoft tenant. There’s no separate SaaS tenant and no migration needed.
How long does an implementation take?
A custom SharePoint build typically takes several months to a year, depending on scope. A ready-to-go solution like Involv intranet typically takes a few weeks – because the information architecture, templates and components already exist.
Why don't Viva Connections and Teams qualify as an intranet?
Viva Connections is a dashboard layer on top of SharePoint and solves part of the problem (a starting point). Teams is built for collaboration inside groups, not for broad one-to-many communication. For a full intranet experience (news, targeting, mobile app, people directory, alerts, analytics) both are additions to a real intranet, not replacements for one.