---
title: "How to Save Email Attachments to SharePoint Automatically"
description: "Save email attachments to SharePoint automatically: the Power Automate flow step by step, where it stops, and a workflow that files each one by what it says."
url: https://thedrive.ai/blog/save-email-attachments-to-sharepoint
published: 2026-11-02
updated: 2026-11-02
tags: ["sharepoint", "email attachments", "outlook", "power automate", "microsoft 365", "workflows"]
author: "Bigyan Karki"
publisher: The Drive AI
---

# How to Save Email Attachments to SharePoint Automatically

> **TL;DR:** Outlook cannot save attachments to SharePoint on its own; rules move messages, not files. The usual first attempt is a Power Automate flow, included with Microsoft 365, that drops every attachment from one mailbox into one library folder under its original name. That works until the folder depends on what the document is. A workflow in The Drive AI reads each attachment, names it from its contents and files it into the right SharePoint folder, from Outlook or Gmail, with a person approving anything you choose. Both routes are below, step by step.

A SharePoint library is where a team's documents are supposed to live, and email is where they actually arrive. Vendor invoices land at ap@, signed subcontracts at a project manager's inbox, certificates of insurance wherever the broker sent them. Someone downloads each one, opens the library, finds the folder, uploads, and renames `Scan_0043.pdf` to something a colleague could find. Miss a week and the inbox is the filing system.

This guide covers every way to save email attachments to SharePoint automatically, what each does with the folder and the filename, and how to set up the one that decides from the document.

Disclosure: The Drive AI publishes this guide and is one of the options compared. Microsoft facts come from Microsoft's own documentation, checked November 2, 2026.

## Can Outlook save attachments to SharePoint automatically?

No. Outlook rules move, copy, flag, forward and categorise messages; the complete list of rule actions has nothing that saves an attachment to a library or a folder. ([Microsoft Learn: rule actions](https://learn.microsoft.com/en-us/office/vba/api/outlook.olruleactiontype)) The old workaround, a rule that runs a script in classic Outlook, was disabled by a Microsoft security update, and Microsoft points to Power Automate instead. ([Microsoft Q&A](https://learn.microsoft.com/en-us/answers/questions/5695983))

By hand, Outlook can save all attachments from one message (Save All Attachments in classic Outlook, Download all in new Outlook and on the web), and the Box for Outlook and similar add-ins save a message's attachments into a folder you pick. ([Microsoft support](https://support.microsoft.com/en-us/office/open-or-save-attachments-92f87f3f-1085-425a-87f6-08d43c19b43d)) Nothing in Outlook does it for the next message without you.

## What are the ways to save email attachments to SharePoint?

| Option | Mailboxes | Picks the library and folder by | Filename | Reads the document | Old mail | Cost basis |
|---|---|---|---|---|---|---|
| The Drive AI workflow | Outlook (Microsoft-hosted), Gmail | What the document says: vendor, client, type, date | Built from values inside the file | Yes, including scans | Historical Sync, 30 to 365 days on Outlook | Max or any Team plan |
| Power Automate flow | Outlook.com, Microsoft 365 | One library and folder per flow; conditions you build | The attachment's original name, unless you write expressions | No | No, new mail only | Included with Microsoft 365 (standard connectors) |
| Outlook filing add-ins (Ideagen Mail Manager, inMailX) | Classic Outlook for Windows | A person picks, with suggestions | As attached, or renamed by hand | No | By hand | Per user, by quote |
| Zapier | Gmail, Outlook and others | One folder per Zap | A name field you fill from email fields | No | No, the trigger looks back one hour | Free for 100 tasks a month, then from $19.99 a month |

The difference that matters is the third column. A flow or a Zap knows the sender, the subject and the filename. The information that decides where a document belongs (which vendor, which project, whether it is an invoice or a statement) is inside the file, and only one option on the list opens it.

## How do you save email attachments to SharePoint with Power Automate?

The standard build, from Microsoft's own training module, is five steps. ([Microsoft Learn: save email content to SharePoint](https://learn.microsoft.com/en-us/training/modules/email-power-automate/5-save-sharepoint))

1. **Create an automated cloud flow** with the trigger **When a new email arrives (V3)** from the Office 365 Outlook connector.
2. **Narrow the trigger.** Set **Include Attachments** to Yes, and filter by **From** or **Subject Filter** so the flow ignores the rest of the mailbox. The trigger watches one mail folder, so an inbox rule that moves matching mail elsewhere will stop the flow seeing it.
3. **Add the SharePoint action "Create file".** Choose the site and the library folder. For **File Name** pick the attachment's name and for **File Content** its content; Power Automate wraps the step in **Apply to each** so it runs once per attachment.
4. **Optionally update file properties** (a SharePoint column such as the sender or received date) with a second SharePoint action.
5. **Save and test** by sending yourself a message with an attachment.

Microsoft also publishes templates that start you here, including "Save email attachments to a SharePoint library and receive a notification" and "Save my email attachments to a SharePoint document library"; open them from the template gallery inside Power Automate.

**What it costs.** A Microsoft 365 licence includes cloud flows with standard connectors, and Office 365 Outlook and SharePoint are standard, at a limit of 6,000 actions per user per day. Premium connectors and some advanced features need Power Automate Premium at $15 per user per month, paid yearly. ([Licensing deep dive](https://learn.microsoft.com/en-us/power-platform/admin/power-automate-licensing/deep-dive-on-specific-license), [Power Automate pricing](https://www.microsoft.com/en-us/power-platform/products/power-automate/pricing))

## Where does the Power Automate route stop?

It stops at the point where the folder depends on the document.

- **One library, one folder.** The folder is fixed when you build the flow. A folder per vendor means a Condition or Switch per vendor, maintained by hand, matched on the sender address, and broken the day the vendor's billing address changes.
- **The original filename.** Create file uses the attachment's name unless you write an expression, and the expression can only use what the trigger gives you: sender, subject, date. `INV_88213.pdf` stays `INV_88213.pdf`, or becomes `2026-11-02 accounts@northwind.com INV_88213.pdf`.
- **New mail only.** The trigger fires for mail that arrives after the flow is on. The backlog in the inbox stays there.
- **Nobody is asked.** The flow files everything that matches, including the reminder with the invoice re-attached and the draft contract that was never signed.
- **Someone owns the flow.** When the SharePoint site is renamed, the connection expires or the loop fails on a .msg attachment, the flow stops and the owner gets an email.

Power Automate remains the right choice when the routing depends on data outside the document, such as a lookup in another Microsoft system, and a person is available to maintain it. For a mailbox that receives documents from many senders, the limits above are the whole problem.

## How does a workflow that reads the attachment file it into SharePoint?

In The Drive AI you connect the mailbox and the SharePoint site, then describe the filing in a sentence. The workflow is drawn from it and shown before it runs:

> When an attachment arrives at ap@, save a copy to the Finance library in SharePoint. Read the vendor, invoice number, date and total. If it is an invoice, rename it "Invoice - Vendor - Date - Total" and file it under Vendors, then the vendor, then the year. If the total is over $5,000, ask Dana to approve before filing. If it is a statement, file it under Vendors/Vendor/Statements.

The steps that appear:

1. **Email Attachment** is the trigger: an attachment arrives in the connected Outlook or Gmail account, optionally limited to senders containing `@northwind.com` or subjects containing "Invoice".
2. **Save a Copy** comes first, always. An attachment has no home until something gives it one, so this step puts a copy into the SharePoint library (or a OneDrive folder, or The Drive AI). The email is never saved, moved or changed.
3. **Read Details from File** pulls the vendor, invoice number, date and total off the page, including scanned PDFs.
4. **Ask AI About the File** decides which kind of document it is, along branches you name: invoice, statement, other.
5. **Rename** and **Move** apply the name pattern and file it into the vendor's folder for the year.
6. **Ask a Person to Approve** holds the ones you named. The approver sees the planned name and destination and approves or rejects; set it to Always ask while you build trust, or Only when unsure afterwards.

The sender, subject and email text are read as context for the file, so "attached is the signed subcontract for Lot 14" helps the filing, and the text is treated as information about the file, never as instructions. Every run is recorded and can be replayed; a failed run hands the file back rather than leaving it half-filed. This is the same model as the general guide to how to [save email attachments to folders](https://thedrive.ai/blog/save-email-attachments-to-folders); SharePoint is one destination.

## Does connecting SharePoint need admin approval?

Yes, once for the whole organisation. Because SharePoint permissions reach other people's sites, Microsoft requires a tenant administrator to approve the app before any user can connect, and this applies to SharePoint Online only; on-premises SharePoint Server is not supported. If the connection is refused, The Drive AI gives you the approval link, the permissions in plain language and a request ready to paste into a ticket. The walkthrough is in [SharePoint document library workflows](https://thedrive.ai/blog/sharepoint-document-library-workflows).

Outlook has its own version of this. Many organisations require a Microsoft 365 administrator to approve The Drive AI before anyone can connect a work or school mailbox, and only Microsoft-hosted mailboxes connect (Microsoft 365, Outlook.com and custom domains on Microsoft hosting; not on-premises Exchange). The Outlook side, including OneDrive as the destination, is covered in how to [automatically save Outlook attachments](https://thedrive.ai/blog/outlook-attachment-workflows-automate-filing).

## Can Gmail attachments be saved to SharePoint?

Yes, by the same workflow. Companies on Google Workspace for mail and Microsoft 365 for documents are common enough that this is a frequent question, and Power Automate's standard template does not cover it. Connect Gmail and the SharePoint site in The Drive AI and the Email Attachment trigger picks up Gmail mail the same way; the destination is the library. If the destination is Google Drive instead, see how to [save Gmail attachments to Google Drive automatically](https://thedrive.ai/blog/gmail-attachment-workflows-automate-filing).

## What about attachments already in the inbox?

Run Historical Sync on the connected account. It brings in attachments from the last 30, 90 or 180 days, or up to a year on Outlook, with sent mail included if you want. They land at the top level of your workspace as they are, with images, calendar invitations, blocked senders and already-imported files skipped; from there a workflow that watches new uploads files them into SharePoint by the same description, or the assistant organises them as one previewed change. Power Automate has no equivalent; its triggers fire only on new mail.

## What will neither route do?

- **Change the mailbox.** Neither moves, labels or deletes messages. Attachments are copied out.
- **Read the document, in Power Automate's case.** Without AI Builder, a flow knows the envelope, not the letter.
- **File without error, in The Drive AI's case.** Steps that read a file carry an ai badge because they can occasionally be wrong; the approval step, the activity record and undo exist for that.
- **Reach a shared mailbox nobody signs in to.** The Drive AI watches the connected accounts that receive the mail; in a team workspace a workflow can watch several members' inboxes. Shared mailboxes are not something it documents.
- **Message Teams.** The Drive AI's Send a Message reaches Slack or an email address, not a Teams channel.
- **Keep running unattended, in Power Automate's case.** Flows stop on expired connections and unsupported attachments, and someone has to own them.

## Setting it up

1. **Connect Outlook or Gmail**, and the SharePoint site. If either is refused, send the approval request to your administrator and come back; nothing needs rebuilding.
2. **Pick one inbox and one document type.** Usually the mailbox that receives invoices.
3. **Describe the filing in one sentence**, including the library, the folder pattern and the name pattern. Check the drawn steps.
4. **Add approval on everything** for the first week, then narrow it to the branch that matters, such as totals over a limit.
5. **Send a test attachment** and open the run. Adjust, then switch the approval to Only when unsure.
6. **Run Historical Sync** for the backlog once the live filing looks right.

If the mailbox is ap@ or invoices@, the invoice-specific setup, including Microsoft 365 shared mailboxes, is in how to [automate an AP inbox](https://thedrive.ai/blog/automate-ap-inbox-invoices). Connecting mailboxes and SharePoint needs the Max plan on a personal workspace or any Team plan; workflows on files uploaded to The Drive AI work on every plan. For the full field of tools, including the Outlook add-ins that file by matter, see the roundup of [email attachment management software](https://thedrive.ai/blog/best-email-attachment-management-software).

## Frequently Asked Questions

### How do I automatically save email attachments to SharePoint?

Either build a Power Automate flow (trigger When a new email arrives, action SharePoint Create file inside Apply to each) that saves every matching attachment to one library folder under its original name, or connect the mailbox and the site to The Drive AI and describe the filing in a sentence, so each attachment is read, named from its contents and filed into the right folder.

### Can Power Automate save Outlook attachments to a SharePoint library?

Yes. The Office 365 Outlook trigger and the SharePoint Create file action are standard connectors included with Microsoft 365, at up to 6,000 actions per user per day. The flow saves to one folder you choose, keeps the original filename unless you write an expression, and only handles mail that arrives after it is switched on.

### Can email attachments be filed into different SharePoint folders by content?

Yes, with a tool that reads the document. The Drive AI's Read Details from File and Ask AI About the File steps pull the vendor, client, document type and date off the page and use them in the folder path and filename. Power Automate can branch only on what the trigger knows: sender, subject and attachment name.

### Does saving attachments to SharePoint need an administrator?

Usually. Connecting SharePoint Online to The Drive AI needs a one-time tenant administrator approval, and many organisations also require administrator approval before a work mailbox can connect. Power Automate runs under your own Microsoft 365 account and needs no approval for standard connectors.

### Can I save Gmail attachments to SharePoint?

Yes. The Drive AI connects Gmail and SharePoint and files Gmail attachments into a library by the same workflow. Power Automate's standard email-to-SharePoint template is built for Outlook.

### What happens to the email after the attachment is saved?

Nothing. Both routes copy the attachment out and leave the message where it was. Deleting or moving the email would be an extra action you add to a Power Automate flow; The Drive AI never changes a mailbox.

### Can old attachments be saved to SharePoint, not just new ones?

With The Drive AI, yes: Historical Sync imports the last 30, 90, 180 or 365 days of Outlook attachments, and a workflow files them into the library. Power Automate triggers fire on new mail only.

## Start with the mailbox that receives invoices

Pick the inbox where documents pile up, connect it and the library, and describe the first filing in one sentence. Watch a week of attachments land in the right folders with names a colleague can read, then add the next document type. [Build the first workflow](https://thedrive.ai/signup), or see how [file workflows](https://thedrive.ai/file-workflows) fit together first.