HomeNotesTalksThe roast curve
M365 Barista Talk · LinkedIn
Home /Notes /R-01

R-01 SharePoint & Teams

Hands off the paperclip. Why files don't belong on SharePoint list items

19/11/20268 minDark · ImplementationShare

“We’ve got lists, we can just attach the files there.” I hear that sentence all the time. And yes, the paperclip in Microsoft Lists is convenient. Click “Add attachments”, drop the file in, save, go get a coffee. No thinking about storage locations, no library, no columns.

That’s fine as long as nobody wants to do more with the files than look at them. But the moment you want to automate, the moment a flow, a script or a Copilot agent needs to get at those attachments, it gets ugly. Honestly. You end up fishing files out of folders that Microsoft creates and hides in the background just so lists can cope with attachments at all. That’s why my advice has been the same for years. Don’t. Use a document library and link the documents to your list with a lookup column.

Where attachments actually live

A list stores rows and columns, a library stores files. Attachments are Microsoft’s attempt to glue the two together. To do that, SharePoint creates a hidden Attachments folder in every list and inside it one subfolder per item, named after the item ID. Attach a file to item 236 of the list “Test” and it ends up under /Lists/Test/Attachments/236/.

Sounds harmless, but it explains almost every problem that comes later. The file is not an item in its own right with its own properties. It is a passenger of the list item and inherits its behaviour, permissions included. And it has a hard limit. A single attachment can be at most 250 MB, while a library allows 250 GB per file.

Automation, where it really hurts

Let’s start with my favourite annoyance. In Power Automate you don’t simply get the attachments along with the item. First you get the list of attachments, then you loop over each one and fetch its content separately. Two actions and a loop just to get at a file that would simply be there in a library. And because the attachment has no columns of its own, your flow only knows the file name afterwards. Whether it’s the contract, the quote or the photo of the whiteboard, it gets to guess.

Microsoft Graph doesn’t make it better. According to Microsoft’s own answers in Q&A and the Tech Community, Graph only tells you whether a list item has attachments. Yes or no. Upload, list, download? No chance. Developers fall back to the older SharePoint REST API with AttachmentFiles. Microsoft confirmed Graph support as a backlog item back in 2021 (Tech Community). It still hasn’t shipped. Files in libraries, on the other hand, are fully reachable through Graph as DriveItems.

And OneDrive sync? You can sync libraries. Offline sync for lists covers the list data, not working with attached files in File Explorer.

What else comes back to bite you

Versioning stops at the paperclip

Lists only keep major versions and only for column values. SharePoint does not version changes to attachments (Microsoft Support). If someone swaps the attached file, the old one is not in the version history. Restore an older version of the item and you get the old column values back, while the current attachments just stay where they are. Good luck finding the contract from three edits ago.

In a library, versioning is the core feature. Every file has its own history, up to 500 major versions by default. With automatic version history limits, SharePoint thins out old versions by age instead of hoarding everything.

A file name is not a metadata strategy

An attachment has a name. That’s it. No document type, no status, no expiry date, no content type. If five files hang off an item, the only thing that tells them apart is the name, and experience says it’s “Quote_final_v2_new_reallyfinal.pdf”. You’ll never build a view of “all contracts expiring next month” this way.

Permissions come as a bundle

The attachment inherits the item’s permissions. Want to share one file with an external person? You share the whole item. Want to protect one file? You lock down the whole item. In a library you can go down to the individual file. Whether you always should is another question. But at least you have the choice.

Compliance looks right past the list

This is where it gets uncomfortable for admins. Microsoft explicitly documents in Purview that retention policies don’t support list items. For those you need retention labels. And even they have a catch. A standard retention label on the item is not automatically applied to the attachment. Only a label that marks the item as a record takes the attachment along, as long as the attachment doesn’t have a label of its own.

Sensitivity labels look similar. You configure a default label for new files per document library. There is no such switch for list attachments. So your nice Purview strategy applies to libraries. Everything sitting in attachments slips through the net.

Copilot agents don’t see attachments

Microsoft has released SharePoint lists as a knowledge source in Agent Builder (Roadmap 561920), with up to 20,000 items per list. But the roadmap also states clearly that list attachments and lookup columns are not included yet. So your agent knows status, owners and dates, but not what’s in the attached quote. Put the same file in a library, add it as a knowledge source, and Copilot finds it within the permissions of the person asking. If you’re getting your lists ready for agents right now, that’s a pretty solid reason to retire the paperclip.

Side by side

Criterion Attachment on a list item File in a document library
Power Automate Get attachments, loop, fetch each content File with all properties directly available
Microsoft Graph Only “has attachments, yes or no” Full access via DriveItem
File versioning No Yes, per file, with automatic version limits
Own metadata No, file name only Yes, columns, content types, views
Permissions Only via the whole item Down to file level
Maximum file size 250 MB per attachment 250 GB per file
Retention policy Doesn’t apply to list items Applies
Default sensitivity label Not available Configurable per library
Agent Builder Attachments not supported yet Usable as a knowledge source
OneDrive sync No Yes

When the paperclip is fine

Let’s be fair. The photo for a damage report, the receipt for an expense claim, the screenshot for a helpdesk ticket can happily stay on the item. Those are evidence, not working documents. Uploaded once, never touched again, no deadline of their own.

My rule of thumb. Will the file be edited later, does it have its own deadline, do you want to search for it, or should some process keep working with it? Then it belongs in a library. If it only proves that something happened, it can stay.

What I do instead

Often the list is really a library

Many lists with attachments are actually document registers. A contract register with the contract attached is a library with the columns partner, term and status. A library can do everything a list can, meaning columns, views, formatting, rules and Power Automate. Plus everything the file needs on top. With every new list, ask yourself briefly whether the file isn’t actually the heart of the item.

Marry list and library with a lookup column

If the list really is a list, say a project or customer register with several documents per item, separate the two cleanly. The list stays your master data source. In the library you add a lookup column pointing to the list. Every document knows its project and keeps all library features. Your flow gets file and project reference in one go, without looping through hidden folders. For real document packages with shared metadata, Document Sets are worth a look too.

An honest note. Agent Builder doesn’t support lookup columns for lists as a knowledge source yet either. Copilot still finds the documents themselves through the library. The link is meant for people, views and flows, not as a bridge for the agent. And before you open libraries up to Copilot, check the permissions first, more on that in Avoiding Copilot oversharing.

Redirect forms instead of banning them

Many attachments come in through forms, either the Lists forms with their new attachment field or Power Apps with the attachments control. A small flow helps here. It moves the file into the right library once it arrives, carries over the metadata from the item and writes a link back to the item. Your people keep their convenient route, and the file still ends up where it belongs.

Cleaning up in four steps

  1. Take stock. Find out which lists actually have attachments and how many. The script below helps.
  2. Define the target structure. Decide per list whether it becomes a library or whether you connect list and library with a lookup column.
  3. Move the files. Download the attachments or move them with a flow, assign metadata and check permissions and labels in the target library.
  4. Turn attachments off. Only once everything has moved and been checked, disable attachments in the advanced list settings. Test this on a copy of the list first.

PnP PowerShell is enough for the inventory. Keep in mind that since September 2024 you need your own app registration in Entra ID. The shared “PnP Management Shell” app is gone.

# Connect with your own Entra app registration
Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/projects" -Interactive -ClientId "<your-app-id>"

# Find all items with attachments in the list "Projects"
$items = Get-PnPListItem -List "Projects" -PageSize 500 -Fields "Title","Attachments"
$items | Where-Object { $_["Attachments"] -eq $true } |
    Select-Object Id, @{ Name = "Title"; Expression = { $_["Title"] } }

# Save the attachments of one item locally (example: item 236)
Get-PnPListItemAttachment -List "Projects" -Identity 236 -Path "C:\Export\Projects\236"

The documentation for Get-PnPListItemAttachment shows more parameters. If you prefer the CLI for Microsoft 365, you’ll find the counterpart there.

My take as an MVP

I can’t get out of this one without criticising Microsoft. Attachments are on by default in new lists, the Lists forms even got their own attachment field with MC1005510, and Graph hasn’t been able to handle list attachments for years. So Microsoft makes the convenient route even more convenient without plugging the holes behind it. Fixing that is left to us, with training, templates and a clear rule.

At the same time, Microsoft has made the library really strong over the last few years. Automatic version limits, default labels per library, libraries as a knowledge source for Copilot and agents. The library is no longer the dusty file dump it used to be. This is where Microsoft puts its money into document management, compliance and AI. The paperclip doesn’t get a cent of it.

Speaking of lists. They get a new interface in December. What to check beforehand is in SharePoint Lists gets a new experience.

Conclusion

Attachments on list items aren’t a mistake, but they are a shortcut that catches up with you later. For evidence that is uploaded once and never touched again, they’re fine. For everything that needs to be edited, searched, retained, protected, automated or found by Copilot, the document library with a lookup column is the right address.

☕ Espresso moment: You don’t clip the coffee grounds to the cup either. They go in the knock box, and that’s where you’ll find them again.

Your takeaways

  • Attachments live in a hidden folder per list item and have no properties of their own.
  • Power Automate only reaches the files through detours, Graph not at all.
  • No versioning, no metadata, no own permissions, no retention policy.
  • Agent Builder doesn’t read list attachments yet.
  • Better: a document library, connected to the list with a lookup column where needed.
  • Photos, receipts and screenshots as pure evidence can stay.

How many paperclips are in your tenant? Tell me on LinkedIn which list moves first.

Share this note

Ferdi Lethen-Oellers
Ferdi Lethen-Oellers

Senior Modern Workplace Consultant at amexus, Microsoft MVP, author of “Microsoft 365 Administration für Dummies”.