What is a SharePoint intranet?

Built into Microsoft 365, managed by IT

Ready to go digital?
Discover how Zoomforth can help you.

Join 500+ enterprise sales, marketing and HR teams building trackable microsites — no developer needed.

Rated 4.5/5 on G2 · Trusted by Fortune 500 teams

A SharePoint intranet is an internal company website built on Microsoft SharePoint, usually bundled into an existing Microsoft 365 subscription. It typically includes a home site for company-wide news, department or team sites underneath it, and a document library that inherits the same permissions structure as the rest of Microsoft 365.

Because most enterprise companies already pay for Microsoft 365, SharePoint is often the intranet a company ends up with by default rather than by a deliberate choice — which explains why so many SharePoint intranets look like templates and get used mostly for file storage rather than as a hub employees actually visit. For the broader picture of intranet formats beyond SharePoint specifically, see our general intranet examples page.

The gap between SharePoint and a branded microsite shows up most in four situations:

Brand-distinct company news — where the default SharePoint home site theming makes every announcement look like a generic Microsoft 365 tenant, not your company.

Content that changes weekly — where onboarding steps or benefits details need updating faster than SharePoint's page and web-part system lets a non-technical team move.

SSO and access controls that fit alongside Microsoft 365 — where visitor access needs to work with existing permissions, not duplicate them from scratch.

Comparing intranet formats beyond SharePoint — where the decision is bigger than one platform. See general intranet examples for the wider picture.

Where SharePoint works well

SharePoint intranet examples that work

SharePoint's strength is document storage and permissions inherited straight from Microsoft 365 — the jobs it does without a custom project.

1. Document library and file permissions

A company kept its policy documents, templates, and department files on SharePoint specifically because permissions were already set up through Microsoft 365 groups — no separate access system to manage, and version history built in by default.

What worked: reusing an access-control system the IT team already maintained meant zero extra setup for a use case SharePoint is genuinely built for.

2. Department team sites for internal file sharing

Individual departments used their own SharePoint team sites as a shared drive with a page wrapped around it — useful for a team that mainly needed organized file storage with light structure, not a destination employees would browse for news.

Result: departments got a working file-sharing setup without waiting on a custom build, which is exactly the job SharePoint handles well.

Where SharePoint hits friction

Where SharePoint intranets hit friction

The complaints are consistent across companies: the look, and who can change it.

3. The templated-look problem

A comms team wanted their company news hub to feel distinct and on-brand, but the default SharePoint home site theming left it looking like every other Microsoft 365 tenant's intranet — recognizable web parts, standard layout, minimal room for a branded visual identity without a custom development project.

What didn't work: matching brand guidelines required custom SharePoint Framework development, which put a "just update the homepage" request behind an IT backlog.

4. The IT-dependency problem

An HR team wanted to add a new onboarding page type and update the layout each quarter as their process changed. Each structural change needed IT involvement, because SharePoint's page and web-part system isn't designed for a non-technical team to restructure independently.

Result: content that needed weekly updates — onboarding steps, benefits details — moved at IT's release pace instead of HR's, and the page slowly fell out of date between IT tickets.

Zoomforth site editor next to a branded welcome page and content dashboard
The branded microsite alternative

What teams build instead — or alongside SharePoint

The two frictions above — templated look, IT dependency — are exactly what a branded microsite is built to solve. It isn't a rip-and-replace decision: several teams keep SharePoint as the system of record for files and permissions, and build the employee-facing hub as a separate microsite instead.

5. Company news hub, rebuilt as a branded microsite

A company kept SharePoint for file storage but moved its employee-facing news hub to a branded microsite the comms team could update directly — no IT ticket for a new announcement, no templated web-part layout. One Zoomforth customer described the result in a G2 review: "Zoomforth is essentially our company's intranet — we link various sites and pages to share information and resources with our internal employees. This has allowed us to cut down on mass emails, convey information in a visually impactful way, and empower our employees to find information they're looking for whenever they need it."

What worked: the comms team published updates the same day they were written, instead of queuing a change behind IT's SharePoint backlog.

Zoomforth visitor access settings with Single Sign-On (SAML) selected, alongside a password-protected site prompt

Build the intranet SharePoint can't, without replacing it

Zoomforth lets comms and HR teams launch a branded internal hub in hours, not an IT project — with granular access controls, SAML SSO, and SOC 2 Type II security built in, so it fits alongside your existing Microsoft 365 permissions rather than fighting them. Request a demo to see how it works.

Request a demo

Frequently asked questions about SharePoint intranets

A SharePoint intranet is an internal company website built on Microsoft SharePoint, usually bundled into Microsoft 365. It typically includes a home site for company news, department sites, and a document library sharing the same permissions structure.

The two most common complaints are look and ownership. SharePoint sites tend to look templated without custom design work, and meaningful changes usually route through IT rather than the comms or HR team that owns the content.

Keep exploring

Related resources

Intranet examples

Beyond SharePoint specifically — see intranet patterns for corporate comms, onboarding, and team hubs.

Enterprise security features

SAML SSO, multi-factor authentication, and SOC 2 Type II — how a Zoomforth hub fits alongside Microsoft 365 permissions.

Internal communications tools compared

How a branded intranet hub compares to dedicated internal comms platforms like Staffbase, Workvivo, and ContactMonkey.