SharePoint doesn't know where your intranet ends

Search returns results from projects and team workspaces and content you didn’t create becomes your problem because SharePoint has no concept of where your intranet ends. Fresh Fabric is that boundary.

Why SharePoint alone isn’t enough

SharePoint gives you the building blocks: sites, metadata, audience targeting, web parts. But each one is configured independently. There is no shared definition of what your intranet is or how it should behave. The result is fragmentation.

Fresh Fabric is the contract that fixes this. One boundary, one taxonomy model, one set of rules, enforced consistently across your intranet.

SharePoint gives you the tools. Fresh Fabric makes them work together.

What defines an intranet in Fresh

An intranet in Fresh is not everything inside your SharePoint tenant. It is a deliberately scoped set of sites and content, identified and governed as a single, coherent experience.

Fresh Fabric defines that scope. It draws a clear line between what is part of the intranet and what is not: project sites, team workspaces, and unmanaged content sit outside it. What is inside is structured, targeted, and governed using shared rules.

This is what makes Fresh an intranet, not just a collection of SharePoint sites and pages.

How Fresh Fabric brings your intranet together

Define the intranet boundary

Specify which sites belong to your intranet and which do not. Every component in Fresh, including search, web parts, and FreshMind, operates within that scope.

Structure your content

One taxonomy and metadata model, applied across every page and web part. FreshMind can auto-generate metadata, so the governance layer stays current without manual effort.

Control what stays current

Lifecycle rules including publish dates, expiry, and ownership controls keep content relevant. Governance rules flag or remove outdated content from intranet components.

Connect it all with search

Governed content surfaces dynamically across web parts, search, and FreshMind. Clean input, clean output.

Benefits

A clearly defined intranet

The boundary between intranet content and the wider SharePoint environment is explicit. Every component in Fresh knows exactly what it is working with.

Governed content that stays current

Lifecycle controls ensure the intranet reflects what is still accurate and relevant. Content does not outlive its intended use.

No separate deployment

Fresh Fabric ships with Fresh. When Fresh is deployed, Fresh Fabric is already active. Nothing to provision separately, no new support category for IT.

A governed intranet inside SharePoint

Scope the intranet experience without restructuring your tenant. Full SharePoint flexibility for IT. A predictable, governed surface for everyone else.

Use cases

Use case	Description
IT and platform owners	Maintain a clear, governed separation between intranet content and the wider tenant, without limiting flexibility elsewhere in SharePoint.
Comms teams	Define content structure and targeting consistently. Every page and component applies it without needing IT involvement for each update or new site.
Global organizations	Run multiple intranet experiences within a single Microsoft 365 tenant. Each with its own boundary, taxonomy model, set of rules.
Content governance	Ownership and lifecycle rules applied systematically across the intranet. Not managed page by page.

Build your intranet on a clearly defined foundation.

Book a demo