If your team moved to New Outlook, filing email to SharePoint got harder. Emails that used to land in the right library with one drag now take several steps, or quietly stop being filed at all.
That matters more than it sounds. The decisions, approvals, and commitments that run a business mostly live in email, and while they sit in one person’s mailbox nobody else can find them, they fall outside the retention and eDiscovery rules that apply to documents, and they leave with the person when they do. Getting them into SharePoint is what turns a message into a record the organization actually owns.
The common explanation is that New Outlook removed drag and drop. That is not quite it. The gesture still works in most places. What broke is one specific target: a SharePoint library open in a browser window. And even where the drag does work, the file that lands carries none of the email’s details with it.
Can you still drag and drop email in New Outlook?
Mostly yes. It depends entirely on what you drop it onto.
| Drop it onto | Works? |
|---|---|
| A folder in File Explorer | Yes, you get an .eml file |
| A SharePoint library synced to your PC with OneDrive | Yes, it is just a folder |
| A SharePoint library open in a browser | No |
You can also right-click a message and choose Save as, which gives you .eml or .msg.
Why the browser drop stopped working
Dragging an email onto a SharePoint site in a browser window is the one thing that reliably worked in classic Outlook and reliably does not in New Outlook.
Microsoft has confirmed it. In response to one of many threads about it, a Microsoft moderator wrote: “This is a known limitation in the New Outlook for Windows desktop client. Currently, users cannot drag and drop emails or attachments directly into SharePoint from the New Outlook, whereas this functionality does work in the Classic Outlook client.”
What Microsoft has not published is why, or when it will change. Requests for an ETA on those threads remain unanswered.
The practical consequence is a workflow change. Keeping a SharePoint site open in a browser tab and dropping messages onto it as they arrive is gone. The replacement is either syncing the library first or saving the message and uploading it, so one gesture becomes a setup job or a four-step round trip.
The bigger problem: the file arrives with no properties
The step count is the part people notice. It is not the part that costs them most.
However the email gets to SharePoint, by drag, by sync, or by upload, the sender, recipients, subject, and date are not saved as properties on the file. They stay sealed inside it, so there is nothing to sort, filter, or search on, and nothing for a retention policy to key off. A default document library has no columns for any of this in the first place, and even when someone adds them, uploading an email leaves them blank.
A library like that is storage, not a record system. It looks fine until someone has to answer who said what and when, at which point nobody can find anything without opening files one at a time.
This part is not new. Dragging never wrote email details into SharePoint properties in classic Outlook either. The migration is simply when organizations notice, because the extra steps make everyone look at the process again.
Why your old add-in stopped working too
If you had an Outlook add-in that handled filing, it probably broke at the same time, which is why this feels like more than one problem.
Classic Outlook supported COM and VSTO add-ins, which ran as native code inside Outlook. New Outlook is built on web technology and supports only modern web add-ins. Microsoft made the change deliberately, so that one add-in runs on Windows, Mac, and the web without being able to touch the machine it runs on. The result is that COM add-ins have to be replaced rather than upgraded.
Our New Outlook vs Classic Outlook guide has the full comparison, and Microsoft’s official feature comparison is worth checking before assuming anything is permanently gone. The list keeps moving.
The free options, and where each one stops
Sync the library to your PC. Use the Sync button on the SharePoint library and it appears in File Explorer, where the drag from Outlook works again. It is the closest thing to the old gesture and it costs nothing in licensing. It does cost elsewhere:
- Every library needs its own sync setup. Fine for one team site, unwieldy once people file into a dozen.
- Content is cached locally, consuming disk space on every device. Microsoft recommends no more than 300,000 items across synced libraries before performance degrades.
- You are looking at a local copy, not the live library. What you see is what last synced, so changes made elsewhere show up on a delay.
- The emails still arrive without properties. Syncing changes how the file gets there, not what it carries.
Save and upload. The right answer at low volume. If your team files a handful of emails a month, do this and buy nothing. Just know the files arrive without properties.
Power Automate. A flow watches a mailbox or folder and writes matching messages to a library. The strongest free option for predictable capture: everything from a sender, everything in a folder. Its limit is that the flow picks the destination in advance, so it cannot help with the decision that drives most filing, which is a person reading a message and knowing this one belongs in that matter folder. Metadata columns have to be mapped by hand in the flow.
Stay on classic Outlook. Microsoft supports it until at least 2029. With a large COM add-in estate, that is a reasonable call and it buys real time. It is a deferral with a date on it.
Filing email as a record instead of a file
Drag-and-drop filing can be rebuilt inside New Outlook, which is what New harmon.ie does. Your SharePoint, Teams, and OneDrive locations sit in a sidebar next to your inbox. Drag the message onto the folder you want and it saves, without leaving Outlook or opening a browser.
The more important part is what arrives. Email headers become SharePoint columns, so To, From, Subject, and Date are real metadata. The library becomes something you can sort, filter, and search, and so can the colleague who needs it two years later. That is the difference between a copy and a record.
The time difference is not marginal. Klotz cut email archival time from 30 seconds to 3 seconds per document, a 90% reduction. At a few emails a week that is nothing. At a few a day per person, it decides whether a filing policy works or just exists on paper.
For messages that always go to the same place, there is no need to save each email by hand at all. You define which emails belong in which location and which conversations should be captured, and harmon.ie files them for you from then on. Shared categories mark what you and your colleagues have already saved, so nobody files the same message twice or assumes someone else did. These automation features are currently in beta.
Custom metadata is worth a word, because it is where email filing usually falls down. Email headers are captured on their own. Beyond that, if your library requires a matter number, a client name, or a document type, harmon.ie prompts for those fields at the moment of saving. The metadata gets applied when the person still has the context to supply it, rather than being left for a cleanup project that never happens.
For IT. harmon.ie is client-side only, with no server to run. Content moves between Outlook and your own Microsoft 365 tenant and never leaves it. The add-in deploys centrally through the Microsoft 365 admin center or Intune and updates itself, so users install nothing. It is ISO 27001 certified. The web add-in works with SharePoint Online; for content still on premises, harmon.ie Classic is included in the same license.
Which option fits you
| Your situation | What to do | Worth knowing |
|---|---|---|
| A few emails a month | Save and upload. Buy nothing. | The emails are stored, but without metadata, so they stay hard to find |
| Predictable capture: everything from a sender or folder | Power Automate, free with your licensing | Same limitation: emails land in the library with no properties unless you build the mapping yourself |
| People file several times a day and choose the destination each time | An add-in, where step count decides whether filing happens | Email details are saved as properties, so the library stays searchable |
| A large COM add-in estate, no budget this year | Stay on classic, with a date in the plan before 2029 | Whatever filing happens today keeps working, metadata gaps included |
Whichever you choose, choose it deliberately. As one chief legal counsel put it: “Emails in Exchange cannot be assumed records. You need to get them into SharePoint.” The move to New Outlook is a good moment to check whether that is actually happening at your organization.
Want to see the sidebar version? Start a free 21-day trial. Nothing for end users to install.
