There Is No AI Without IA
AI in SharePoint just went live. Your metadata work just got more important, not less.
Microsoft shipped AI in SharePoint to general availability on 6 May 2026. Most SharePoint owners I’ve spoken to since are reading it one of two wrong ways. Both miss what actually changed.
On 6 May 2026, Microsoft pushed AI in SharePoint to general availability across all eligible Microsoft 365 tenants. The headline promise reads like a small revolution: SharePoint will now read your files, identify what’s in them, and apply the right metadata automatically. No more empty Document Type columns. No more ‘whose job is it to maintain the term store anyway?’ No more nagging end users to tag their uploads.
If you’ve been carrying SharePoint metadata as part of your job, the announcement probably hit you one of two ways.
The first reaction: relief. Finally, the tedious work goes away. Microsoft has automated the bit nobody enjoyed. We can all stop arguing about whether HR Policies should be a folder or a column value.
The second reaction: quiet panic. If AI is doing the tagging, what was the point of the last five years of architecture work? Was the metadata design obsolete the moment Microsoft shipped this?
Both reactions are wrong. The work most SharePoint owners have been doing just became more valuable, not less.
What AI in SharePoint Actually Does
Strip away the marketing language and AI in SharePoint does three things:
- Builds sites from natural language. You describe what you want (“a site for our HR team with a policies library and an onboarding page”); it builds the structure.
- Reads files and applies metadata. Upload a document; it identifies type, topic, department, status — and populates the matching columns.
- Adapts libraries as content evolves. Patterns it learns from one batch of content inform how it handles the next.
That third one is the most interesting. AI in SharePoint isn’t a one-time tagging tool. It’s adaptive — it watches how content flows through your library and adjusts how it categorises new arrivals.
If you’ve been reading the Microsoft announcement, this is roughly what they told you. What they didn’t tell you is the catch.
The Catch: AI Can’t Design What It Doesn’t Know
Here’s the part nobody is putting on a LinkedIn carousel.
AI in SharePoint applies metadata to the columns that already exist in your library. It populates the Document Type field — only if you’ve created a Document Type column. It assigns the right Department — only if Department is part of your library schema. It uses your Term Store vocabulary — but only if the term sets are there to use.
In other words: AI is filling in your structure. It is not designing the structure for you.
If your library has three random columns with inconsistent values across thousands of files, AI in SharePoint won’t fix that. It’ll learn the inconsistency. It’ll propagate the inconsistency. It’ll automate the inconsistency at scale, faster than you ever could manually.
This is the same dynamic I’ve been writing about for two years — Copilot doesn’t fix the mess, it exposes it. AI in SharePoint is the same principle, one layer deeper: it doesn’t fix the structure, it acts on whatever structure you give it.
Three Reasons Your Metadata Work Just Got More Valuable
If you’ve already done the architectural work — defined a Document Type column, built a clean term store, set up sensible views — AI in SharePoint is a gift. It propagates your good work across thousands of files with almost no effort on your part.
If you haven’t done that work, AI in SharePoint is a hazard. Here’s why.
AI accuracy is bounded by your structural design
The thing AI in SharePoint cannot do is invent good metadata categories out of thin air. It uses what’s there. If your library has a column called Status with values like ‘WIP’, ‘wip’, ‘work in progress’, ‘draft’, ‘in progress’, and ‘DRAFT’, AI in SharePoint won’t standardise them for you. It’ll learn that messy distribution is “what the team uses” and assign new files using the same chaotic vocabulary.
A library that’s well-designed before AI touches it gets clean, accurate auto-metadata. A library that’s poorly designed gets fast, confident, mis-tagged metadata at scale. Same AI feature, very different outcomes.
AI makes confident mistakes you have to catch
Every AI tool that auto-applies metadata has the same failure mode: it tags wrong sometimes, but it tags wrong confidently. The output looks correct. The Status column reads ‘Approved’. The Department reads ‘Finance’. The Document Type reads ‘Policy’. Everything’s filled in. Looks great. Job done.
Except the file was a Draft, owned by Operations, that referenced a Policy but wasn’t one.
You treat it with suspicion. The gap is visible.
You trust it — and discover the problem at the worst possible moment.
Verifying auto-applied metadata on representative samples is now part of the SharePoint owner’s job. AI accelerates the work; it doesn’t remove the need to check it.
Copilot now reads everything — including the mess
Here’s the part that connects AI in SharePoint to the Copilot story most organisations are already in the middle of.
Copilot grounds its answers in whatever it can read. The better your metadata, the better Copilot’s responses — because Copilot uses metadata signals (Document Type, Department, Status) to identify which content is authoritative, current, and in scope. If your metadata is sloppy, Copilot doesn’t get smarter; it gets faster at being wrong.
AI in SharePoint feeds more content into the metadata layer than ever before. That means clean metadata gets cleaner Copilot answers. And messy metadata gets messier Copilot answers, propagated to more users, more reliably.
The phrase there is no AI without IA (Information Architecture) used to be a slogan. After 6 May 2026, it became literal. The AI in your tenant — Copilot, the Copilot Agents, AI in SharePoint itself — is doing more work on more content than at any point in SharePoint’s history. The information architecture underneath it is doing more work too. Quietly. Constantly. For better or worse.
What This Actually Means for SharePoint Owners
Three practical things shifted on 6 May 2026, and none of them are ‘AI does my job now’:
The bar for sloppy metadata just got higher. Pre-AI, a poorly-structured library was inefficient. Post-AI, a poorly-structured library actively misleads at scale. The cost of getting it wrong went up.
Architectural work is more leveraged than ever. Designing a clean column structure used to pay off in better search results and easier reporting. Now it pays off in every AI feature in your tenant being more accurate, including Copilot. The same hour of design work returns dramatically more value.
Auditing metadata is no longer optional. When metadata was applied by humans, you trusted the humans (or chased them down). When metadata is applied by AI, you trust the AI’s accuracy on a small verifiable sample, then audit periodically thereafter. New process; not a one-off.
What To Do This Week
Three concrete things, in order:
- Check whether AI in SharePoint is enabled in your tenant. It’s rolled out to most Microsoft 365 customers but not all. If it’s on, you need a position on how your team uses it. If it’s off, you need to think through governance before enabling it tenant-wide.
- Run an audit on one well-used library. Pick a library with 100–500 files and review the metadata. How consistent are the values? How many empty fields? How many columns have devolved into 17 versions of the same idea? This is the baseline AI will work with.
- Read three knowledge base topics if you haven’t already. Start with the Document Type Column (because every well-designed library needs one). Then the 3-Level Folder Rule (because flat structures plus metadata beats deep folders, every time). Then Choice vs Managed Metadata (because picking the wrong column type at the start makes AI in SharePoint less effective forever).
The work that compounds is the work that holds up under AI. If you do nothing else this week, do that.
The Bigger Picture
Microsoft has been telegraphing this for over a year. Copilot in 2024. Knowledge Agent in late 2025. AI in SharePoint in May 2026. The Copilot Agents (Excel, Word, PowerPoint, Planner) in April 2026. The Claude Opus 4.8 and GPT-5.5 integrations into M365 Copilot in May 2026. Look at that list as a sequence and one thing becomes obvious: AI is doing more work on top of SharePoint, not less.
Every one of those features grounds in your metadata. Every one of them performs better with clean structure and worse without it. None of them are designed to replace architectural thinking — they’re designed to act on it.
The SharePoint owners who’ll benefit most over the next twelve months aren’t the ones who let AI do everything. They’re the ones who get the structure right first so AI has something good to act on.
There is no AI without IA.
That was true before 6 May 2026.
After 6 May 2026, it’s the whole game.
If you’re thinking through how to structure your SharePoint libraries to get the most out of AI in SharePoint, Copilot, and the new Copilot Agents, the Metadata & Organisation section of the Knowledge Base covers all 45 decisions you’ll need to make — from column types to term sets to naming to views. Free, no signup required. Built for the SharePoint owner who has to make this work in real organisations.
