Save Outlook Attachments to OneDrive Automatically (2026 Guide)

It's a Tuesday. You open Outlook and search hasattachments:yes from:stripe. 38 results.

You right-click the first attachment. "Save As." Browse to OneDrive. Pick a folder. Rename the file because Stripe calls every invoice invoice.pdf. Switch back to Outlook. Open the next email.

You do this 37 more times. Then again for AWS. Then for Adobe, Notion, Linear, Cursor, Vercel, Postmark, your domain registrar, every SaaS subscription you've signed up for since January.

Two and a half hours later, you've filed maybe 60 PDFs and your wrist hurts.

There is a better way. Microsoft will tell you the answer is Power Automate. They are technically correct and practically wrong. Here's the full picture, including the version that actually ships.

Table of Contents

• The native Outlook + OneDrive answer is "kind of"
• What Power Automate actually costs you
• What we built instead
• Setup, end to end
• App folder mode: we cannot see anything else
• What about M365 work accounts?
• What we don't do
• TL;DR

The native Outlook + OneDrive answer is "kind of"

Microsoft does have a story here. Two of them, actually.

The first is "Save to OneDrive" right inside Outlook. You hover over an attachment, click the OneDrive icon, and the file lands in your Email attachments folder. One click instead of three.

The problem is that "one click" times "30 vendors" times "12 months" is still 360 clicks a year, and they all pile into the same flat folder. By April you've got invoice.pdf, invoice (1).pdf, ... invoice (47).pdf. Useless to your accountant.

The second answer is Outlook rules. Rules can do a lot - move messages, set categories, forward, mark as read. They cannot save an attachment to OneDrive. That's not a feature. It has never been a feature. Microsoft's recommended fix is to forward the message to Power Automate.

So we end up at Power Automate. Which is where most blog posts about this stop, with the words "and that's how easy it is to save Outlook attachments to OneDrive!" Reader, it is not easy.

What Power Automate actually costs you

Power Automate's free tier (bundled with M365) gives you 750 actions per day per user. Sounds like a lot. It isn't.

Each "save to OneDrive" run uses at least three actions: trigger fires, get-attachment, create-file. A heavy-receipt user with 30 vendors emailing 5+ PDFs each in a busy month chews through 750 actions in a couple of weeks.

When you blow the limit, your flow doesn't just stop - it queues. Filings show up days late. By the time you notice, you've already missed a tax-deductible receipt that lived in your inbox for 72 hours and got auto-archived.

The fix is Power Automate Premium, which starts at $15/user/month. That's more than AutoFileEmail Pro will cost when it ships.

There's also the build cost. The default "Save Outlook attachments to OneDrive" template dumps everything in one folder. To get vendor-domain folders like /stripe.com/2026/05/, you have to write custom expressions:

split(triggerOutputs()?['body/from'], '@')[1]

split(triggerOutputs()?['body/from'], '@')[1]

Then nested if() calls to strip mail., noreply., notifications. prefixes from sender domains, because notifications.aws.amazon.com should land in aws.amazon.com, not its own folder.

The expression language gets ugly fast. Most people give up around the third nested if() and accept that noreply.stripe.com and stripe.com will be separate folders forever. Now your accountant has 80 folders instead of 30. Worse, not better.

For a deeper look at why these duct-tape automations cost more than purpose-built tools, see the Outlook + OneDrive freelancer's filing setup.

What we built instead

You connect Outlook. You connect OneDrive. AutoFileEmail watches your inbox. When a new email with an attachment arrives, three things happen:

1. We pull the registrable sender domain. noreply@billing.stripe.com becomes stripe.com. bills@aws.amazon.com becomes amazon.com. The hand-coded prefix-stripping that nobody wants to write in Power Automate, we do for you.
2. We build the folder path: /Apps/AutoFileEmail/stripe.com/2026/05/.
3. We save the attachment there with the original filename, prefixed by the email date.

A real example. Stripe sends a payout invoice on May 7, 2026. Subject: "Your invoice from Stripe." Attachment: invoice.pdf.

It lands in OneDrive at /Apps/AutoFileEmail/stripe.com/2026/05/2026-05-07-invoice.pdf.

No vendor seed list to maintain. No expression to debug. The first time Postmark emails you, a postmark.com folder appears. The first time some new SaaS you signed up for last week sends a receipt, that folder appears too.

When tax time rolls around, you open OneDrive, navigate to Apps > AutoFileEmail, and your CPA gets a clean per-vendor breakdown. That's the whole workflow.

Setup, end to end

The actual click-by-click for Outlook + OneDrive:

1. Sign up at autofile.email with your Microsoft account. 30 seconds.
2. Click "Connect Outlook." Microsoft consent screen. Approve Mail.Read (we read mail and download attachments, that's it).
3. Click "Connect OneDrive." Second consent screen. Approve "Have full access to the application's folder."
4. Done. AutoFileEmail starts polling within 30 seconds of you finishing onboarding.

If you signed up today, you also get a 30-day historical preview free. Last month's receipts file themselves retroactively without you doing a thing.

If you want the last full tax year filed too, buy the $29 Tax Year Pack. One-time payment, no subscription. Backfill runs in the background; you can close the tab.

The full setup walkthrough lives at /integrations/outlook-onedrive.

App folder mode: we cannot see anything else

This part matters more than people realize.

OneDrive has a permission scope called Files.ReadWrite.AppFolder. It's the narrowest scope Microsoft offers for OneDrive. Translated: AutoFileEmail can create, read, update, and delete files inside /Apps/AutoFileEmail/. We cannot see, list, or touch anything else in your OneDrive. The Microsoft Graph API will refuse if we try.

Your family photos, your work docs, your half-finished pitch decks, the Documents folder, the desktop sync, the Personal Vault - all invisible to us. Not "we promise not to look." Literally not in the API surface we have access to.

Compare that to Hubdoc, Dext, or any of the OCR-based receipt tools. They want broad inbox access AND broad file access. They scrape every receipt, send it through GPU-backed OCR, and store the parsed line items. The trade is "give us your data, we give you searchable receipts." We don't make that trade. We just file the PDFs Stripe sent you, in the folders your accountant wants to see them in.

The /Apps/ prefix in OneDrive is a real-world consequence of this sandbox. If you've ever connected another Files.ReadWrite.AppFolder app, you've already got an Apps folder; AutoFileEmail just adds a sibling subfolder.

What about M365 work accounts?

If your inbox is at a Microsoft 365 work account (yourname@yourcompany.com), there's an extra step: many enterprise tenants block third-party apps by default. The consent screen will say "Approval required" and the connection fails until your IT admin grants tenant or per-user consent.

The good news is the scopes we ask for are narrower than what tools like Power Automate, Zapier, or Hubdoc request. Most IT teams approve Mail.Read + Files.ReadWrite.AppFolder without much pushback because the footprint is genuinely small.

For solo founders running a single-user M365 tenant (you're the admin), this is just one extra "Consent on behalf of your organization" checkbox during onboarding. Tick it. Done.

What we don't do

A few things worth being explicit about, because the receipt-filing category is full of tools that quietly do more than you'd expect:

• No OCR. The PDF in your OneDrive folder is the same PDF Stripe sent. We don't parse line items. We don't extract amounts. We don't categorize. Your accountant's software does that better than any of these tools, and we're not reading your receipts - we're just filing them.
• No outbound mail. Mail.Read only. We can't send, reply, forward, or mark as read.
• No per-email metering. The free tier files unlimited new attachments going forward. The Backfill Packs are the only paid product, and they're one-time, not subscription.
• No Cash App Pay. Standard checkout, Stripe-backed.

If you want OCR, your accountant's software does it better than any of these tools. Filing is the part that's actually missing for most people.

TL;DR

• Outlook's native "Save to OneDrive" is a one-click flat dump. Doesn't scale past 50 receipts.
• Outlook rules can't save attachments. Microsoft's official fix is Power Automate.
• Power Automate's free tier (750 actions/day) runs out in busy months; Premium is $15/user/month. Vendor-domain routing requires custom expressions that nobody enjoys writing.
• AutoFileEmail's Outlook + OneDrive setup: two OAuth screens, files land under /Apps/AutoFileEmail/{vendor}/{YYYY}/{MM}/, free for one inbox.
• App folder mode means we literally cannot see anything else in your OneDrive.

Free for one inbox + one cloud. 30-day historical preview included. The $29 Tax Year Pack covers a full year of backfill if you want April's receipts already filed.

We don't read your receipts. We just file them. Try it - worst case, you save an hour next April.