By the time Bill Gates took the stage in early 2008 to talk about Microsoft Office SharePoint Server 2007, the numbers had stopped being a software story and become an infrastructure story. Microsoft reported that SharePoint had broken 100 million licences sold and passed $1 billion in annual sales, with some 2,250 certified partners building on it. No intranet platform had ever scaled like that. And almost none of it was the result of a considered decision about how organizations should manage information. SharePoint 2007 adoption happened because the product was already in the building.
The Distribution Trick
The strategic move was not the feature set. It was the packaging. Windows SharePoint Services shipped as a free, licensed component for Windows Server. Any organization already running Windows Server — which was very nearly all of them — could stand up team sites without a purchase order, a procurement cycle or a business case. The full Office SharePoint Server product then sat above it as the paid upgrade for search, portals, records management and web content. The consequence was predictable. A department with an IT-adjacent employee and a spare afternoon could have a working intranet site by Friday. Thousands of organizations discovered they had a SharePoint estate before they had a SharePoint strategy.
What It Genuinely Fixed
It is easy to be cynical in hindsight. SharePoint 2007 solved real problems that file shares had failed at for fifteen years:
- Version history and check-in/check-out ended the era of
proposal_final_v4_JB_REVISED.doc, at least in principle. - Document libraries with metadata columns allowed content to be organised by attributes rather than by folder path.
- Basic workflow put approvals and reviews inside the document rather than in an email thread.
- Enterprise search indexed content across sites, which for many organizations was the first time internal documents were findable at all.
- Web-based access meant remote and branch users could reach the same content without a mapped drive or a VPN session that half-worked. For teams migrating off shared drives, the improvement was real and immediate.
And What It Created
The same properties that drove adoption produced the governance problem that defined the next decade. Sprawl. Sites multiplied because creating one was free and trivial. Few organizations tracked how many they had. Fewer could say who owned each one. Duplication. Without a coherent information architecture, the same policy document ended up in six libraries across four sites, each diverging slightly. Search surfaced all six, which taught users to distrust search. Permission drift. Inheritance was broken site by site, library by library, item by item, usually to solve an urgent access request. Over a few years the effective permission model became impossible to describe on a whiteboard. Orphaned content. A team reorganised, a project closed, an owner left — and the site stayed, indexed and accessible, quietly ageing. Metadata that nobody maintained. The taxonomy designed in month one required discipline in month twenty-four that no one had budgeted for. Most SharePoint 2007 deployments ended up as file shares with a web interface and worse navigation. That was not a product failure. It was a governance failure that the product made very easy to commit at scale.
The Same Pattern, Nineteen Years Later
Anyone running Microsoft 365 today is living in the sequel. Every team created in Teams provisions a SharePoint site behind it. Every private channel adds another. Provisioning is now measured in seconds and requires no IT involvement whatsoever, which means the sprawl of 2007 has been reproduced at a volume the 2007 administrators could not have imagined. Two developments changed the stakes. First, AI assistants surfaced the over-sharing problem. When a colleague could only find a document by knowing which site it lived on, loose permissions were a latent risk. When an assistant can answer "what are we paying the new CFO?" by retrieving anything the user technically has access to, loose permissions become an immediate disclosure event. Organizations deploying Copilot-style tools routinely discover their permission model is far broader than anyone believed. Second, the on-premises estate became a security liability. The exploitation of SharePoint Server vulnerabilities in July 2025 — where Microsoft's initial patches proved incomplete and had to be re-released within the same week — was a reminder that legacy SharePoint farms left running because nobody wanted to migrate them are internet-facing application servers with deep access to corporate content.
What Collaboration Governance Should Actually Specify
- A named owner for every site or workspace, revalidated on a schedule, with automatic escalation when the owner leaves.
- A lifecycle, including an expiry date and an archive path. Content that cannot be deleted can at least be removed from search and from active permissions.
- A permission model with few exceptions, reviewed against reality rather than against the design document.
- A provisioning path with light friction — enough to force a two-minute decision about purpose and ownership, not enough to push people back to email attachments.
- Findability as the success measure. If people cannot locate the authoritative version in under a minute, the platform has failed regardless of how much content it holds.
- An AI readiness pass before deployment: over-shared sites, stale sensitive content and broken inheritance need to be fixed before an assistant starts retrieving from them.
| Governance area | Record to maintain |
|---|---|
| Ownership | Name the current owner and the reassignment route. |
| Lifecycle | Record the purpose, review date and archive path. |
| Access | Describe permitted access and review exceptions. |
| Authoritative content | Identify the current source and retire conflicting copies. |
| AI readiness | Review oversharing, stale sensitive content and inheritance before retrieval. |
Qualitative summary of this article's source text, not a measured outcome or performance estimate.
Common Questions
Why did SharePoint 2007 spread so quickly?
Windows SharePoint Services was included with Windows Server, so teams could deploy sites without new licence spend or a procurement process. Adoption was driven by availability rather than by strategy.
What is intranet sprawl?
The uncontrolled growth of sites, libraries and duplicated documents without ownership, lifecycle or consistent structure. It degrades search quality, creates conflicting versions of authoritative content, and complicates access control.
Does modern SharePoint Online avoid these problems?
No. Provisioning is easier, which accelerates sprawl. What has improved is the tooling for governance — sensitivity labels, expiry policies, access reviews and reporting — provided someone is assigned to use it.
Where should an intranet clean-up start?
With ownership and permissions, not with content. Identify sites with no active owner and sites with unusually broad access. That intersection is where both the clutter and the disclosure risk concentrate.
Intranet Governance Review — Outpace maps your SharePoint and Teams estate: ownership gaps, over-shared content, duplicate authoritative documents and stale sites. Particularly worth doing before you switch on an AI assistant that can read all of it.