Diagram of intranet governance: a small governance team linking a business owner, an IT partner and named site owners across SharePoint sites, with review and measurement loops

Intranet governance: who owns what and how to keep it

By Nicolas Saliba · Published November 2026 · 13 min read

In short

Intranet governance rarely fails loudly. Owners get named, the launch ends, and nobody checks whether content stays accurate. Here is how to assign ownership, set review rules, automate enforcement in Microsoft 365, and measure whether it works.

Key takeaways

Microsoft recommends a business-led governance team with IT as partner, small enough to make decisions quickly.

NN/g found average task times of 78 seconds on centralized intranets versus 123 seconds on distributed ones.

SharePoint Advanced Management policies can require at least two owners per site and flag inactive sites.

Site lifecycle policies notify owners and administrators; they do not delete SharePoint sites directly.

Page views alone cannot reveal outdated content; readership by department shows owners what is actually used.

Most intranet governance fails quietly. The plan is written once, for launch day: owners are named, permissions are set, the site goes live, and attention moves to the next project. Six months later, nobody can say which pages are still accurate, which sites still have an accountable owner, or which news areas employees have stopped reading. Microsoft's planning guidance treats governance differently: your intranet governance plan evolves as your organization evolves and as new capabilities are added to SharePoint and Microsoft 365, and planning should happen during the exploration phase to ensure that all stakeholders have shared vision and goals^[1]. A plan that never changes was never really a plan. It was a launch document.

Microsoft Learn is also specific about what makes ownership stick. Roles and responsibilities must be clearly defined and communicated, and ideally incorporated into job descriptions or performance goals. And the governance team should not be disbanded when you launch, because governance has an ongoing role in your intranet's success. If the team disbands, the plan stops evolving the moment the platform does. Three patterns tell you governance was treated as a launch document:

Site owners exist in the site settings, but no one has asked them a single question since go-live.
Responsibilities were announced in a kickoff email, never written into job descriptions or performance goals, so content review competes with everything else in the owner's day job.
The governance team disbanded after launch, so decisions about new sites, new capabilities and retired content have no forum.

The cost shows up in your content, not in your documentation: outdated pages keep ranking in search, contradictory versions circulate, and employees learn to distrust the intranet as a source. The fix is not a better document. It is tying every named owner to a measured review routine: a business owner with IT as partner, rules owners can actually follow, automation that enforces the minimum, and metrics that show whether any of it works. The rest of this article builds that routine.

Who should own the intranet?

Microsoft Learn answers the ownership question without hedging: most intranet professionals agree there is one organization that should not be the exclusive intranet owner, and that is IT. IT cannot build an intranet for the business; it can only build one with the business and with a commitment from the business. Successful intranets have a champion and owner from the business, ideally at executive level^[1]. For you as a Digital Workplace or IT manager, that is not a loss of control. It is the partnership that keeps your intranet funded, prioritized and used after the launch enthusiasm fades.

Around that business owner, build a governance team with core members from key business stakeholder groups in addition to IT. There is no magic size: small enough to make decisions easily, representative enough to carry the voice of the business. When a topic exceeds the team's expertise, bring in outside members such as legal or records management so decisions stay aligned with organizational constraints. Then push ownership down to site level, so every site has people whose names sit against it:

Role	What they hold
Business owner (executive level)	Vision, priorities and funding; accountable for the intranet as a business asset
Governance team	Policies and guidelines, site provisioning and decommissioning, information architecture, measurement
Site owner	Day-to-day content health, permissions and the review schedule for their site
Primary and secondary contact	Named per site; Microsoft's example policy states that all SharePoint sites have a primary and secondary contact responsible for the site and its content
IT and Digital Workplace	Platform, security, automation and analytics; partner to the business, not exclusive owner

Two practical notes. First, Microsoft points out that intranet ownership is often shared by more than one organizational unit, and that is acceptable; what matters is that every site has a named accountable pair, because the secondary contact is what keeps governance alive when the primary changes roles or leaves. Second, ownership decisions extend beyond the intranet itself: our Digital Workplace Guide walks through who should own each Microsoft 365 surface and the governance decisions nobody wants to make.

Which rules keep content healthy?

Ownership only protects content if it converts into rules a site owner can follow without interpretation. The clearest evidence on what those rules look like comes from the Nielsen Norman Group (NN/g), which has usability-tested 57 intranets over 18 years with more than 285 employees. In the teams with effective content, one practice recurred: they regularly checked content for its relevance, effectiveness and accuracy, and adjusted content as needed to uphold standards. When content becomes outdated, it is updated, consolidated, or removed^[2].

NN/g summarizes that practice as a four-part content model. Build your content rules around the same four stages:

Plan: decide who manages each piece of information, where it lives, and how long it stays on the intranet.
Create: publish against the standards the governance team has defined.
Maintain: check relevance, effectiveness and accuracy on a schedule, not on suspicion.
Unpublish: update, consolidate or remove content that no longer meets the standard.

Set review intervals by reach. Microsoft's guidance is explicit that you may want more formal policies and stricter governance guidelines for sites that face the entire organization, and less strict policies for content that is more targeted, such as content for an individual department or a one-time event^[1]. Apply the same gradient to review: organization-wide policies and news get short, fixed intervals with a named reviewer, while departmental content gets a lighter cycle. Microsoft's own planning questions make the accountability explicit: who is accountable to review content, and at what frequency, the site owner, the content author, or another role?

There is also a measurable argument for keeping some central oversight. In NN/g's research, employees completed tasks in 78 seconds on average on intranets with a centralized content-management model, versus 123 seconds on distributed models, a statistically significant difference; hybrid models averaged 84 seconds and also beat distributed ones^[2]. Distributed publishing is not the problem. Distributed publishing without central checks is where content health dies, because no individual owner ever sees the whole picture.

What can Microsoft 365 enforce automatically?

Rules that depend on memory fail. SharePoint Advanced Management addresses this with site lifecycle management policies that automate common governance tasks, so sites stay active, properly owned and regularly reviewed. The policies do not delete sites directly: they notify site owners and administrators and take actions based on how you configure them^[3]. That makes them the enforcement layer for the ownership rules in the sections above.

Policy	What it enforces
Site ownership policy	A minimum number of owners or administrators per site; Microsoft's example requires at least two site owners, and the policy notifies designated recipients when a site falls below the threshold
Inactive site policy	Inactivity thresholds: it evaluates activity across SharePoint and connected workloads such as Microsoft Teams, Exchange and Viva Engage, then asks owners to confirm the site is still in use
Site attestation policy	Periodic confirmation from owners or administrators that a site is still needed, meets organizational requirements, and has correct ownership and permissions

Before you promise this automation in your governance plan, check your licensing. SharePoint Advanced Management is not included in every Microsoft 365 plan. Microsoft's prerequisites page requires an eligible base subscription, such as Office 365 E3, E5 or A5 or Microsoft 365 E1, E3, E5 or A5, plus at least one user assigned a Microsoft Copilot licence or the SharePoint Advanced Management Plan 1 add-on; some features, such as restricted site creation, require the add-on regardless^[4]. Confirm where your tenant stands before you write lifecycle policies into the plan.

Be clear about what automation can and cannot do. It enforces ownership minimums and catches inactivity, but it cannot tell you whether a page is still accurate. Attestation asks the owner to confirm; readership data shows whether anyone would notice if the page disappeared. That gap between confirmation and evidence is what measurement closes.

How do you measure whether governance works?

Named owners cannot judge content health without usage evidence, and page views will not give it to them. Microsoft Learn puts it directly: look for metrics that are more than just page views, because a page being viewed does not mean the content is current or useful. Your measurement plan should define the metrics and analytics used to track success, any associated KPIs, and processes for evaluating them and taking action^[1].

Four metrics map directly to the governance decisions in this article:

Readership by department: shows each site owner which audiences actually use their content, so review decisions rest on evidence instead of habit.
Unread and low-reach content: flags news items that never surfaced or headlines that were skipped, which are the first candidates to update, consolidate or unpublish.
Reach against the intended audience: a page with high views from the wrong viewers is a targeting problem, not a content problem.
Trend after changes: confirms whether a review actually changed behaviour, or whether the content needs a different owner.

Native reporting makes this harder than it should be. In Tryane's Digital Workplace Benchmark 2026, SharePoint's Analytics category scores 45%, the lowest of its category scores in the report, which Tryane grounds in in-depth platform demonstrations, interviews with industry experts and analysis of publicly available data^[5]. We cover which SharePoint numbers mislead and what to use instead in our guide to which intranet metrics matter, and why SharePoint news goes unread even when view counts look healthy. Download the full to compare platform analytics before you commit to a measurement stack.

Close the loop by delivery, not by dashboards: readership data only affects content health when it reaches the site owner on a schedule. When every owner sees which of their pages are unread each month, review intervals stop being a policy statement and become a decision with evidence behind it.

Microsoft's guidance on rhythm is realistic: your governance team may meet frequently during intranet planning and then less frequently over time, and the goal is to establish a rhythm that works for your intranet and team members. Since governance has an ongoing role in your intranet's success, the governance team should not be disbanded when you launch. By reviewing and revising the governance plan regularly, you help ensure that your intranet remains a critical asset for your organization^[1]. The practical question is what that rhythm looks like in a calendar. A cadence that holds up in Microsoft 365 environments:

Quarterly: the governance team reviews policy exceptions, new site requests, and the sites automation has flagged as ownerless, inactive or unattested.
Per review interval: site owners check their pages against readership data and update, consolidate or remove what fails.
Twice a year: publish a short content-health summary per department, so every owner sees themselves in the data.
Annually: revise the governance plan itself, its policies, intervals and automation, as SharePoint and Microsoft 365 add capabilities.

Keep the plan findable. Microsoft suggests replacing the governance document with a resource site that combines "how to" (training) with "how should" (governance), so users understand both why and how your intranet is designed and governed. Align attestation and review cycles with the team's meeting rhythm instead of running them as one-off projects. And when you sit down to judge performance, start from a defined population and a defined question, not from an exported report; we explain that approach in our guide to analyzing intranet performance.

Give content owners the readership data governance relies on

The routine in this article stands on four legs: a business owner with IT as partner, review rules owners can follow, automation that enforces the minimum, and metrics that show what is actually used. Most Microsoft 365 tenants have the first three in some form. The fourth is where it breaks, because the readership data lives in separate consoles per channel, if it is reachable at all, and rarely reaches the site owner in a form they can act on. Microsoft's measurement guidance asks for exactly that: defined metrics and analytics to track success, associated KPIs, and processes for evaluating them and taking action^[1].

That is the gap Communication Insights closes. It is an all-in-one, cross-channel analytics platform that connects your email newsletters, your SharePoint intranet, Viva Connections and Viva Engage into one central dashboard, so site owners get the department-level readership data their review decisions depend on, without exporting from three consoles.

What that changes in the routine you have just built:

Each site owner sees who reads their content, by department, on a schedule.
Review intervals get evidence: unread pages surface first, so owners update, consolidate or unpublish with confidence.
You get one cross-channel view instead of disconnected point solutions, and your comms team stops asking you for exports.

Book a 30-minute call with Jérémy to see how Communication Insights gives your content owners the readership data governance relies on.

Frequently asked questions

Who should own the intranet, IT or internal communications?

A business owner, with IT as a partner rather than the sole owner. Microsoft Learn states that intranet governance must reflect the goals of business stakeholders and the legal and regulatory environment, not just the expectations of the IT department, and recommends a small governance team with core members from key business groups alongside IT.

How many owners should a SharePoint site have?

At least two. Site ownership policies in SharePoint Advanced Management let you define a minimum number of owners or site administrators; Microsoft's example configuration requires all sites to have at least two site owners, and the policy notifies designated recipients when a site falls below the threshold.

Do SharePoint site lifecycle policies delete sites?

No. Microsoft states that site lifecycle management policies do not delete SharePoint sites directly. They monitor sites, notify site owners and administrators, collect responses, and take enforcement actions based on how you configure each policy.

Is SharePoint Advanced Management included in Microsoft 365?

Not in every plan. Site lifecycle management policies are part of Microsoft SharePoint Advanced Management, a separate capability with its own licensing prerequisites, so check what your tenant already includes before planning governance automation around these policies.

How often should intranet content be reviewed?

Regularly, with intervals set by content reach. NN/g found that the best teams check content for relevance, effectiveness and accuracy on an ongoing basis, and update, consolidate or remove whatever is outdated. Apply stricter review rules to organization-wide sites and lighter rules to departmental or event content.

What metrics show whether intranet governance is working?

Look beyond page views. Microsoft Learn recommends using metrics that flag outdated and irrelevant content, together with readership broken down by department, so each site owner can see what is actually used and make review decisions based on evidence rather than guesswork.

What is a SharePoint site attestation policy?

A policy in SharePoint Advanced Management that periodically asks designated site owners or administrators to explicitly confirm that a site is still needed, business-relevant and compliant with internal governance requirements. Unlike inactive site policies, which rely on detected activity, attestation policies request a direct review from the people accountable for the site.