If Microsoft 365 Copilot is giving your people vague, outdated or plain wrong answers, the problem usually isn’t Copilot. It’s the information Copilot is reading. Copilot answers from what’s in SharePoint, OneDrive, Teams and Exchange, so when that content is scattered, duplicated or overshared, the answers are too.
I see the same pattern in my consulting work all the time. An organisation gets excited about Copilot, rolls it out across the business, and a few weeks later wonders why the results are underwhelming. Almost every time, the information architecture wasn’t ready.
What information architecture means in SharePoint
Information architecture is how your organisation’s knowledge is structured, connected and made findable. Folder structures and naming conventions are part of it, but they’re the smallest part. In SharePoint it comes down to four things:
- Site structure: how your sites, hubs and libraries relate to each other, and who owns each one.
- Metadata and content types: how documents are classified, so you can filter by client, status or document type rather than digging through folders.
- Navigation and findability: how people, and now AI, locate what they need.
- Permissions: who can see what, and why.
When any of these is poorly designed, people struggle to find things. If your people struggle, Copilot doesn’t stand a chance.
Why Copilot makes information architecture urgent
Before Copilot, poor information architecture was an inconvenience. People spent extra minutes searching, or relied on tribal knowledge like knowing Sarah keeps the budget files in her team’s channel.
Copilot changes the stakes because it searches across everything a person has access to in your tenant. If your information is spread across old subsites, duplicated in personal drives or locked behind inconsistent permissions, you’ll see one of three things:
- The wrong answer. Copilot finds an old version of a document and treats it as current.
- A missing answer. The document that matters is somewhere Copilot can’t reach or doesn’t rank.
- A confident answer built on contradictions. Two versions of the same policy say different things, and Copilot blends them.
None of these builds trust, and once people stop trusting Copilot, they stop using it. That’s when the licence spend starts to look hard to justify.
The three foundations to fix first
You don’t need a perfect tenant before you turn Copilot on. You do need these three foundations in the areas where you expect people to use it most.
1. Flatten your site hierarchy
Subsites made sense in SharePoint a decade ago. Modern SharePoint is designed around a flat structure, where every site is its own top-level site and hubs connect related sites for navigation and search. Flat sites are easier to own, easier to secure and easier to retire when the project ends.
If you’re still running deep subsite hierarchies, moving to a flat hub-and-spoke model is usually the single biggest structural improvement you can make.
2. Put metadata on the libraries that matter
Metadata columns beat nested folders. When documents carry a document type, a client, a status or an owner, people can filter and sort instead of hunting, and Copilot has clearer signals about what each file is and whether it’s current.
You don’t have to retag every document in the tenant. Start with the handful of libraries your teams use every day, the ones that hold your policies, templates, contracts and client work, and build from there. I walk through what that looks like in turning SharePoint into a Copilot knowledge base with metadata.
3. Clean up permissions and oversharing
Oversharing is the quickest way to lose trust in Copilot. If someone asks about Q4 revenue and Copilot surfaces a draft that was only meant for the executive team, you’ve got a problem, and it wasn’t Copilot that created it. Copilot only shows what that person already had access to. It just makes the access visible.
Run a permissions review on your most sensitive sites, apply sensitivity labels, and make sure every site has a named owner who’s responsible for who’s in it.
Where to start
The approach that works best is to go narrow before you go wide:
- Audit what you have. Find your highest-traffic sites, your oldest subsites and the places sensitive content is overshared.
- Pick one high-value area. Usually the team or department that would get the most out of Copilot, and has the most painful search problems today.
- Fix the foundations there first. Flatten the structure, add metadata to the key libraries and tidy the permissions.
- Expand from that success. A team that’s getting reliable answers from Copilot is the best business case you’ll ever have for doing the rest.
If you’re unsure where files should live in the first place, start with OneDrive vs SharePoint: what to use when. And if you’re still deciding who needs a Copilot licence, Microsoft 365 Copilot vs Copilot Chat covers what each one can reach.
The organisations that get the most from AI are the ones that did the unglamorous work of organising their information first. It doesn’t make for a great demo, but it’s the difference between an AI that sounds impressive and one people rely on.
If you’d like a clear view of where your tenant stands before you spend more on licences, the AI Workforce Assessment maps it out in five business days. If you’d rather have someone working through it with you month by month, that’s what the AI Concierge is for.
Frequently asked questions
What is information architecture in SharePoint? It’s how your content is structured so people can find and trust it: the way sites and hubs are organised, the metadata on your libraries, your navigation, and who has access to what. Good information architecture makes content findable for people and for Copilot.
Does Copilot need SharePoint to be organised first? Copilot works on day one, but the quality of its answers depends on the content it can reach. Duplicated, outdated or overshared content leads to wrong or incomplete answers, so the areas where you expect heavy Copilot use should be tidied first.
Do I need to remove subsites before rolling out Copilot? Not everywhere, and not before you start. But flattening the subsite hierarchies in your most-used areas makes ownership, permissions and search clearer, which helps both people and Copilot.
Can Copilot show people files they shouldn’t see? No. Copilot only shows content the person already has permission to access. The risk is oversharing that already exists in your tenant, which Copilot makes much easier to stumble on. A permissions review fixes the cause.
