Save email attachments to SharePoint without Power Automate
A Power Automate flow can save attachments from a Microsoft 365 mailbox into SharePoint, and it is included in Microsoft 365 plans like Business Standard and E3. Email It In does the same job without a flow: it gives you an email address that files each attachment into the document library you choose. Here is when each one fits.
Who this is for
This page is for IT admins and operations people who need mail from outside senders, business systems or office copiers to land in a SharePoint document library. SharePoint in Microsoft 365 has no email address for a library: incoming email was a feature of SharePoint Server. So many teams build a flow.
What a Power Automate flow needs
- A mailbox for the mail to arrive in, such as a shared mailbox. The account that runs the flow needs access to it.
- A flow that someone builds and tests: a trigger such as "When a new email arrives in a shared mailbox (V2)", then a step that creates a file in SharePoint for each attachment.
- The owner's account. An automated flow runs in the context of its owner. If the owner leaves the organisation, Microsoft advises changing the owner, or giving the flow its own licence, so that it keeps running.
- A size limit. The Outlook triggers skip any email larger than 50 MB, or larger than the limit your Exchange admin set, if that is lower.
- Someone to look after it. Microsoft turns off a flow that keeps failing for 14 days. A flow that is not triggered for 90 days may be turned off too, unless its owner has a Premium licence.
It costs nothing extra. Microsoft 365 plans such as Business Basic, Business Standard, Business Premium and E3 include Power Automate with the standard connectors, and the Outlook and SharePoint connectors are both standard.
When a flow is the better choice
- The mail already arrives in a Microsoft 365 mailbox. Microsoft 365 usually blocks automatic forwarding to outside addresses until an admin allows it, so filing the mail where it is can be simpler.
- Your team already builds and runs flows, and someone owns them.
- Each file needs more than filing: metadata columns, an approval, a message in Teams, a different name based on its content.
- Mail and files must not pass through another company's service.
When an Email It In address is simpler
- Copiers and scanners. A copier can send straight to our mail server, with no sign-in. At the end of December 2026, Microsoft 365 turns off password sign-in for sending mail (SMTP AUTH) by default, and many copiers scan to email that way. See scan to SharePoint from any copier for the copier settings.
- Outside senders and systems. Suppliers, report mailers and other apps send to one address. There is no mailbox to set up or watch.
- Large files. Paid plans have no email size limit, and large files go to SharePoint in parts. The sender's own mail service may still have a limit.
- Nothing to build. Sign in, choose the library, and the address works. Your delivery log lists every file that was filed and when.
- A folder per tag. With a routing rule (every paid plan), mail to you+invoices@emailitin.com, or with [invoices] in the subject, goes to an invoices folder in the library. The Pro plan adds automatic folders by sender or month.
- Failures are visible. If a file cannot be saved, the sender's mail server tries again later, or the sender gets a bounce message.
Side by side
| Power Automate flow | Email It In | |
|---|---|---|
| Where mail arrives | A Microsoft 365 mailbox that the flow watches | Its own address, like jane42otter@emailitin.com |
| Setup | Build and test a flow | Sign in, then pick the site, library and folder |
| Copiers | They need a way to send into Microsoft 365 | They can send straight to Email It In, with no sign-in |
| Size of one email | Emails over 50 MB (or your Exchange limit) are skipped | No limit on paid plans; 5 MB on the free plan |
| Whose account it uses | The flow owner's | The Microsoft account that connected SharePoint |
| More steps per file | Anything a flow can do | A notice email or a web hook; or a flow that starts when the file reaches the library |
| Where mail is handled | Inside Microsoft 365 | On Email It In servers (Amazon Web Services, US East); attachments are deleted once filed |
| Price | Included in Microsoft 365 plans with Power Automate | From $5 a month; a small plan at no cost to try it |
When to use which
| Use | |
|---|---|
| Mail already arrives in a Microsoft 365 mailbox, and your team runs flows | A flow |
| Each file needs more steps: metadata, approvals, a Teams message | A flow, or Email It In plus a flow that starts when the file arrives |
| Mail must stay inside Microsoft 365 | A flow |
| An office copier scans to SharePoint | Email It In |
| Outside senders or systems email files to the team | Email It In |
| Emails over 50 MB | Email It In, on a paid plan |
| Nobody wants to build or look after a flow | Email It In |
How it works
- Sign in with SharePoint, using a Microsoft 365 work account (see the next section for which one). If your organisation only allows apps an admin has approved, Email It In shows you a link to send to your admin.
- In Settings, pick the site, the document library and a folder in it, or the top of the library.
- Give out the address: to suppliers, in the copier's address book, or in the system that sends the reports. Each attachment lands in the library under its own name.
- On a paid plan, add routing rules: each tag, like +invoices or +contracts, files into its own folder.
Connect with a shared account, not a person's
Email It In files with the Microsoft account that connected SharePoint, and it can only reach the sites and libraries that account can open. If that person leaves and their account is turned off, filing stops and mail to the address bounces. Someone else who signs in gets a new Email It In account with a new address, so every copier and sender would need the new one.
So connect with a shared work account that IT controls, such as a service account, and give it access to the library. The Email It In settings and billing then stay with that account, not with one employee. Use an account whose mail someone reads: Email It In sends account notices to it, such as a request to reconnect. A flow has the same problem: when a flow's owner leaves, Microsoft's advice is to change the owner.
Which plan fits
- Personal, $5 a month for 200 files a month: a small team that files supplier invoices into one library. It has routing rules, large emails and allowed senders.
- Pro, $15 a month for 2,000 files a month: an office copier, or a system that sends reports every day. It adds automatic folders by sender or month, and clean file names that start with the date.
- Business, $49 a month for 20,000 files a month: many senders or busy systems, with priority support.
A file is one attachment. The free plan, to try it first, files into one folder and has no routing rules. See pricing for yearly prices.
Try it with SharePoint
The Email files to SharePoint page has more on libraries, folders and admin approval.
Paid plans start at $5 a month for 200 files a month, with no email size limit. To try it out, the free plan takes up to 20 files a month, in emails up to 5 MB.
Sources
Read on 19 November 2026:
- Microsoft Learn: Office 365 Outlook connector (shared mailbox trigger, 50 MB limit)
- Microsoft Learn: SharePoint connector
- Microsoft Learn: Power Automate licensing FAQ (included plans, flow owners)
- Microsoft Learn: Power Automate limits (flows turned off)
- Microsoft Support: incoming email for a list or library (SharePoint Server)
- Microsoft Learn: automatic external email forwarding
- Exchange Team Blog: SMTP AUTH basic authentication timeline
