New Outlook Cannot Attach Files From a Network Drive: Fixes

Why can new Outlook not attach files from a network drive?#

If the attach dialog will not show your mapped drive, nothing on your machine is broken and no setting will bring it back. New Outlook cannot attach files from a network drive because the client does not support it. Microsoft's feature comparison between new and classic Outlook lists access to files on a network share as available in classic Outlook and not supported in new Outlook, checked 30 July 2026.

The reason is architecture. New Outlook for Windows is web-architected: it runs the same web interface Outlook on the web runs, so it reaches files through a browser-style picker rather than a desktop file dialog wired into the Windows shell. Microsoft documents the outcome rather than the mechanism, but the mechanism is why the outcome is permanent rather than a bug in the queue.

There is a second, separately documented restriction that catches people out. Microsoft KB 2918627 states that in Exchange Server and Exchange Online you cannot use Outlook on the web to access shared files through a UNC path, and calls it by design. So a link to a path like \\fileserver\clients\contract.pdf does not open for anyone reading in a web client either.

What works and what does not#

Not everything about attachments changed, and it helps to know which half you are fighting. Local files and cloud files are fine; anything that requires reaching across the network from inside the client is not.

The fix that always works: copy locally, then attach#

This is the route Microsoft's own KB points at, and it works on every account type and every file size the mailbox will take. It costs about two minutes.

1. 1

   Open the folder in File Explorer, not in Outlook

   Go to the mapped drive, or paste the UNC path into the Explorer address bar. Explorer still reaches the share normally — it is only the client's attach picker that cannot.

2. 2

   Copy the file, do not move it

   Ctrl+C on the file, then paste it into a local folder. Moving it takes the document away from colleagues who expect to find it on the share, which is a far bigger problem than an attachment.

3. 3

   Attach the local copy in new Outlook

   In the compose window choose Attach file, then browse this computer, and pick the copy. From that point it behaves as an ordinary local attachment and the only ceiling is your provider's size limit.

4. 4

   Check you copied the current version

   A stale local copy is the real risk of this method, especially on documents several people edit. Compare the modified date against the share before you send anything contractual.

5. 5

   Delete the copy once the mail has gone

   Local copies of controlled documents are exactly what an auditor asks about. Keep one staging folder, empty it weekly, and keep the share as the system of record.

That is why copy-first is less untidy than it first sounds. Out of a shared folder holding thousands of documents, the two you are actually sending are the only ones that ever leave it.

Three routes, and what each one costs#

Which route fits depends less on the file than on who owns the rules about where that file may live. Costs stated honestly, because for some readers two of these are not permitted.

"Just put it in SharePoint" is real advice, and it is not free#

Moving the share into SharePoint or OneDrive genuinely fixes this, and it fixes several adjacent problems at once: version history, links instead of 40 MB attachments, access from a phone. If your organisation is heading there anyway, this attachment problem is a reason to go sooner.

But it is a migration, not a workaround. Folder structures rarely survive the move unchanged, permissions have to be rebuilt against groups instead of NTFS, and external sharing runs into whatever policy your tenant has set. Line-of-business applications that write to a UNC path — practice management, CAD, accounting exports, scanners that drop PDFs onto a share — keep writing there regardless of where you moved the email workflow.

There are also files that may not go. Some regulated and client-confidential material sits on-premises by contract or by policy, and no attach dialog changes that. If that describes your files, treat the local-copy route and classic Outlook as the two real options and stop evaluating the third.

Which Outlook clients can reach a network share?#

Advice on this topic goes wrong when it forgets to name the client. Here is the whole picture as of July 2026 — verify on Microsoft's own pages before planning around it, because this table is exactly the part that changes.

When staying on classic Outlook is the right answer#

If your business runs an on-prem file server and a large part of the day is open the share, attach the file, send it, then the cleanest answer is to keep classic Outlook for that work. That is a fit judgement, not procrastination. The workflow exists in one client and does not exist in the other.

You have room to make that call calmly. Microsoft supports existing classic Outlook installs through perpetual and subscription licensing until at least 2029, and no firm final cutover date has been announced. The same architecture that removes network-share attachments also removes COM add-ins, VBA macros and custom forms, which we cover at /blog/com-add-ins-not-working-in-new-outlook.

One date does deserve a diary entry for admins. Enterprise opt-out — new Outlook becoming the default for enterprise tenants, with switching back still possible — is scheduled for 1 March 2027 according to message centre post MC949965. Message centre posts are tenant-scoped and never appear on Microsoft Learn, so confirm that date in your own admin centre rather than taking it from any article, including this one.

• Stay on classic if attaching from a share is a daily, non-negotiable step and the files cannot be copied off it.
• Stay on classic if COM add-ins, macros or custom forms are also in your critical path.
• Switch if your documents already live in SharePoint, OneDrive or Teams — the link route is better than an attachment anyway.
• Switch if the share is occasional, and use one staging folder for the times it comes up.
• Either way, put a quarterly reminder in the calendar to re-check the feature comparison page.

Where AI Emaily fits, and where it does not#

Straight answer, since we build AI Emaily: we are a web-architected client too, so broadly the same file-picker constraints apply to us. Attaching directly from \\server\share is not a problem we solve, and the copy-locally route is what we would tell our own users to do. Our macOS and Windows downloads are real desktop apps built as an Electron shell around the web interface, not native binaries with shell-level file access.

What we do is the part after the attachment — triage, thread summaries and drafted replies written from a Personal Context you set yourself and client profiles you control, rather than from reading your past mail. Nothing sends without your approval in Copilot mode, and every action has undo and an audit trail. Details at /features/ai-email-assistant and /docs/composer-tools.

The short version#

New Outlook cannot attach from a network drive because it is a web client, and Microsoft lists network-share access as unsupported rather than upcoming. Copy the file locally and attach the copy, or send a OneDrive or SharePoint link if your documents live there.

If the share is your system of record and always will be, keep classic Outlook for that workflow. It is supported until at least 2029, and choosing it deliberately beats fighting a client that was never built to reach your file server.