Intranet governance is the allocation of decision rights and accountability. It answers two questions: who gets to decide, and who is answerable for the outcome.
The purpose is practical. An intranet with those two questions settled is still achieving its goals in two years' time. Without them, it gets maintained by whoever happens to notice. A page goes out of date, someone mentions it in a Teams channel, and whoever holds edit rights fixes it if they have time that week. Noticing isn't the same as being answerable.
The drift that follows is a progression you can see on plenty of intranets. Nobody owns the content, so it goes stale. People stop trusting it, so they stop coming. The falling traffic then removes whatever motivation there was to maintain it.
Governing and managing are not the same job
Governance evaluates, directs and monitors. Managing the intranet plans, builds and does the work. Deciding that every page needs a named content owner is governance. Chasing the pages that don't have one is management.
Both jobs often sit with the same person, who sets the standard on Monday and then publishes pages under it on Tuesday. That's workable, and it's also where the distinction earns its keep, because the decision tends not to get written down and nobody asks later whether it was right.
The areas governance covers
We have identified seven areas that we feel are core for intranet governance. This series goes into detail for each: decision rights, site ownership and access, publishing standards, the content lifecycle, navigation and findability, oversharing and Copilot, and measurement. Each gets a post of its own.
One important point before going further is that governing the intranet isn't the same as governing the tenant. The intranet usually belongs to internal communications, and the tenant to IT. Some decisions sit in both worlds at once, including who can create sites, external sharing and retention. Each of those should be assigned to one group or the other, and the two groups need to talk regularly rather than only when something has gone wrong.
The governance tools in Microsoft 365
Microsoft 365 gives you a set of governance tools rather than a governance system, and they're spread across several admin areas. Site lifecycle policies and the data access governance reports sit in the SharePoint admin center. Control over who can create groups sits in Microsoft Entra ID. Retention policies and the sensitivity labels applied to sites sit in Microsoft Purview.
Licensing decides how much of that you can reach. Site lifecycle policies, site access reviews and Restricted Access Control are SharePoint Advanced Management (SAM) features rather than baseline SharePoint. Assigning at least one Microsoft 365 Copilot license gives your SharePoint administrators the SAM features that support Copilot deployment.
There's no single view across these tools, so anybody assembling a picture of how their intranet is governed does it by hand. Which controls you can reach depends on licensing rather than on what your intranet needs, so two organizations with the same problem can have different options for dealing with it. And no tool allocates accountability. You can configure every tool and still run an intranet that nobody answers for. That work happens between people, and it's the subject of the post how intranet governance decisions get made.
Common questions
What is SharePoint intranet governance?
Intranet governance is the arrangement that says who gets to make decisions about your intranet, and who is answerable when one of them turns out wrong. In practice it covers questions like who approves a new site, who owns a page once it's published, and who settles a disagreement between two teams. Configuring the SharePoint settings that enforce those decisions is management, and doing it well isn't the same as governing. If a decision that comes up regularly has nobody's name against it, that part of your intranet isn't governed yet.
Is intranet governance the same as SharePoint governance?
No. SharePoint governance covers the platform across the tenant and usually belongs to IT, while intranet governance covers the content, structure and standards of the intranet itself and usually belongs to internal communications or a dedicated intranet team. They overlap in tenant-wide decisions such as who can create sites, and each of those should be assigned to one group or the other.
Do you need SharePoint Advanced Management to govern an intranet?
No, but it does provide access to some useful controls. Assigning at least one Microsoft 365 Copilot license gives SharePoint administrators the SAM features that support Copilot deployment. However, many organizations don't have SAM, and governance still works without it. The decisions that make up governance, who owns what and who is answerable, aren't licensed features at all.
Series links
→ Next in the series: how intranet governance decisions get made
