Twenty years ago I started working with SharePoint. This week it turned 25. Yes, I’m that person who gets genuinely excited about a SharePoint birthday. I’ve seen every announcement cycle. Some were brilliant. Some quietly disappeared. Some made me question my life choices at 10pm while fixing broken permissions. But what Microsoft laid out at the 25th birthday event, combined with everything building since Ignite, is the clearest direction I’ve seen in years.
So here’s my honest take. What’s new. What’s been building for a while. And what it really means if you work in this space.
What Actually Launched at the 25th Birthday Event
Let’s start with accuracy. The headline announcement this week was the reimagined SharePoint experience entering public preview. That’s the core change tied specifically to the birthday event. A redesigned app bar. A visual refresh. A reframing of what SharePoint is for.
Other features that got airtime — like the SharePoint Admin Agent, Knowledge Agent and Viva Amplify integration — were announced earlier and have already been in preview. They’re part of the same strategic direction.
Now let’s break down what’s actually changed.
The Reimagined SharePoint Experience: Discover, Publish, Build
The new SharePoint interface is structured around three core jobs: Discover, Publish and Build. On the surface, it looks like a cosmetic update. It isn’t. It’s a positioning shift.
Discover: SharePoint as the Semantic Foundation
Discover is about finding knowledge wherever you work. Not just through a search box, but through Copilot, through Teams, through SharePoint itself. SharePoint content now underpins the semantic layer of Microsoft 365. That means Copilot reasons over your documents, your sites and your libraries.
Here’s the part I’ve been saying for years: if your content is organised properly, it will surface intelligently. If it’s messy, duplicated, permission-sprawled and unstructured, it will still surface. Just not in the way you’d want. AI does not fix poor information architecture. It amplifies it.
Publish: AI-Assisted Communication at Scale
Publish introduces AI-assisted publishing embedded directly into the SharePoint web experience. Viva Amplify now connects into SharePoint so a news post can be distributed across Outlook, Teams and Viva Engage in one step, with unified analytics to track reach and engagement.
For intranet managers and communications teams, this is genuinely useful. One source of truth. Distributed everywhere. Measured in one place. That’s a maturity shift in how internal communication works.
Build: AI-Driven Solution Creation Inside Governance
Build is where it gets interesting for practitioners. SharePoint is positioning itself as a governed environment where teams can plan, create and iterate solutions with AI. Procurement repositories, IT knowledge bases, marketing content hubs — all built within the Microsoft 365 governance framework.
This isn’t about random AI experiments. It’s about building structured solutions inside an environment that already has permissions, compliance and lifecycle controls.
Custom AI Skills: Powerful and Potentially Dangerous
A major part of the Build story is Custom AI Skills. These are structured packages of organisational knowledge — your standards, your terminology, your governance rules and your business logic — that shape how AI behaves in your environment.
This is powerful. It lowers the barrier to building intelligent, context-aware solutions without heavy development. Describe what you need, and SharePoint scaffolds it.
Here’s the flip side. If the content underneath is inconsistent, permissions are chaotic, old documents sit alongside current ones and metadata hasn’t been applied, these skills won’t quietly fail. They will confidently automate the wrong things. At scale.
Custom AI Skills are probably the strongest argument yet for fixing your information architecture before layering intelligence over the top.
The SharePoint Admin Agent: Governance at Scale
The SharePoint Admin Agent has been building since Ignite, but its role in this new direction is significant. For anyone responsible for large environments, this matters.
The Admin Agent monitors inactive sites, overshared content and permission sprawl. It highlights risk. It can help apply lifecycle policies. It surfaces patterns that would take humans weeks to uncover manually.
Anyone who has audited permissions across hundreds of sites knows that archaeology work. The digging is exhausting. The Admin Agent doesn’t replace human judgement, but it dramatically reduces the manual excavation. That is not a small step forward.
File Collection in Document Libraries: Useful, But Govern It
Another practical update is the ability to collect files into document libraries via structured forms, even from people who don’t have access to the library itself. They submit through a link, attach a file, and metadata is applied on upload.
That’s useful. On many of my recent builds, the client has asked for exactly that. The ability to fill out a metadata form when uploading a document. Contractors, clients and external contributors can also provide content without being granted full access.
But governance still applies. You are effectively creating an inbound door into a document library. That door needs ownership. It needs expiry dates. It needs oversight. Enabled thoughtfully, it’s helpful. Enabled and forgotten, it becomes a quiet risk that one day appears in an audit report.
Knowledge Agent: The Engine Behind Discover
Knowledge Agent has been building for some time, but the birthday event reinforced its importance. It fills metadata, improves discoverability and connects organisational knowledge into Copilot’s reasoning layer.
This is the engine behind Discover. It’s what makes contextual answers possible.
And it works dramatically better when the content it interacts with is structured, current and properly tagged. This is not a side observation. This is the entire point.
What This All Adds Up To
Across the event, Microsoft made one core argument repeatedly: SharePoint is now the primary grounding source for Microsoft 365 Copilot. Knowledge can no longer remain passive. It needs to be activated.
Activated knowledge requires structured content. Structured content requires information architecture. Information architecture requires work. The work most organisations have been postponing for years.
Every feature in this release assumes your environment is in reasonable shape. The ones designed to help you fix it exist because Microsoft knows most environments aren’t.
I’ve been saying for two decades that you cannot bolt intelligence onto chaos and expect clarity. This week, Microsoft effectively made that argument at scale.
If your organisation is rolling out Copilot and your SharePoint structure hasn’t been reviewed since 2019, that’s no longer a background issue. It’s a live operational risk. AI doesn’t create order. It amplifies what’s already there.
Final Thoughts: 25 Years In
SharePoint is 25. It’s grown up. It’s clearer about its role. And for the first time in a while, the strategy feels cohesive.
But none of it changes the fundamentals. Good governance. Clear site structure. Sensible permissions. Thoughtful metadata. That’s still the foundation.
There is no AI without IA.
And if you’ve been in this space as long as I have, you’ll know that part isn’t new. It’s just finally being said out loud.
