You have SharePoint. Maybe Teams. Maybe OneDrive. Maybe all three, with the same files scattered across all of them. And somewhere in the middle of it all, there's a folder called "FINAL DOCUMENTS" that contains another one called "FINAL DOCUMENTS 2" and a third called "FINAL DOCUMENTS CORRECT VERSION".
If that sounds familiar, you're not alone. And you're also not using what you have.
The File Nobody Can Find Anymore
Folders work like physical drawers: you open them, put something in, close them. The logic is immediate, comfortable, universal. Anyone who used Windows in the 2000s understands the model without any training.
The problem appears when the drawer starts having drawers inside. And those have more drawers. And someone reorganized the second level in 2023 but forgot to tell anyone.
A concrete example that repeats itself in almost every organization:
- User A stores the contract in
Clients > 2022 > Active > Contracts > Signed - User B stores the same type of file in
Legal > Current > Active Clients - User C creates a new folder because they couldn't find either of the two
The file exists. It's there. It's just lost inside a structure that grew without criteria, with each person adding a new layer based on the logic that made sense to them at that moment.
This has a name: folder forest. And it's the dominant pattern in most organizations that migrated to the cloud without rethinking how they organize content.
What a File Really Is
A service contract isn't just a file in a location. It's a document with several simultaneous dimensions:
| Dimension | Example |
|---|---|
| Type | Service contract |
| Client | Company X |
| Status | Active |
| Responsible area | Legal |
| Confidentiality | Restricted |
| Expiration | December 2026 |
All that information exists. The question is: is it encoded in the folder structure (or in the file name), or is it in columns the system actually understands?
Metadata are columns added to a SharePoint library that describe each file without depending on where it's stored. Instead of navigating to find, you filter: "show me all contracts for client X with Active status". Five seconds. No clicking through anything.
Folders determine where a document lives. Metadata describes what a document is.
The same file appears in multiple views simultaneously, because it doesn't belong to a physical location. It belongs to a set of attributes.
Folders vs. Metadata: The Direct Confrontation
| Criterion | Folders | Metadata |
|---|---|---|
| Adoption curve | None | Requires initial setup |
| Flexibility | Rigid (one file, one place) | High (one file, multiple views) |
| Search | Depends on knowing where it is | Filters by any attribute |
| Scalability | Degrades with volume | Maintains performance |
| Automation | Limited | Native (Power Automate, retention, AI) |
| Reorganization | Costly and risky | No impact on files |
For small libraries and single-person teams, folders work. For anything larger, the table above already tells the end of the story.
Now AI Is the One Doing the Searching
For a long time, the metadata vs. folders debate was about user experience: who preferred navigating vs. who preferred filtering. A matter of taste, habit, team culture.
In 2026, the variable changed.
Microsoft 365 Copilot answers questions about your organization's documents. It searches, reads, synthesizes. It just doesn't open folders. In July 2026, Microsoft confirmed the following behavior:
When you reference a library or folder in a query, Copilot uses the library's column metadata to refine and make results more accurate.
That means an architectural decision that seemed internal, almost invisible, now directly determines the quality of AI responses your team receives.
- Library with clear metadata: precise, contextualized, useful responses
- Library with nested folders and empty columns: generic responses, noise, hallucinations
Document chaos always had a cost. Now that cost appears in real time, every time someone asks Copilot something.
The Transition Everyone Keeps Postponing
If metadata is so much better, why do folders still dominate?
Zero friction. Anyone with SharePoint access creates a folder without training, without configuration, without having to ask anyone anything.
Metadata requires a decision before use. Someone needs to define:
- Which columns exist in that library
- Which values are valid for each column
- Which fields are mandatory on upload
- How the default views are configured
It's an investment of a few hours that pays dividends for years, but one that rarely has a clear owner in organizations. The result is the pattern seen in almost every SharePoint environment with more than three years of life: a mix of old folders that "nobody touches because no one knows what's in there" and isolated metadata attempts that never scaled.
The Point Where Everything Starts to Change
Nobody migrates a folder forest all at once. It's not realistic or necessary. What works is starting a new library the right way.
Five columns that solve 80% of cases:
| Column | Type | Example values |
|---|---|---|
| Document type | Choice | Contract, Report, Proposal, Minutes |
| Responsible area | Choice | Legal, Sales, IT, HR |
| Status | Choice | Draft, Under review, Approved, Archived |
| Client / Project | Managed metadata | Centralized client list |
| Confidentiality | Choice | Public, Internal, Restricted |
When the team sees that "filter by Approved status" is faster than opening six folders, adoption happens without needing a mandate.
The right document architecture isn't the most elaborate one. It's the one any team member can use correctly without having to ask where to save a file.
Worth an Entire Episode
Document management sounds like an internal IT topic. In practice, it's the difference between an organization that finds what it knows and one that discovers it lost information precisely when it needed it most.
If this topic interests you, subscribe to the Macareno newsletter. We talk about Microsoft 365, SharePoint, and all the infrastructure that makes modern work actually function, without detours and without unnecessary jargon.
Sources
- Managing documents in SharePoint: 2026 admin guide - Orchestry
- Folders vs. Metadata | SharePoint Maven - SharePoint Maven
- What's New in Microsoft 365 Copilot - July 2026 - A Guide to Cloud and AI
- SharePoint Showcase: How Metadata and the Knowledge Agent Elevate Microsoft 365 Copilot Responses - Microsoft Tech Community