Move Outlook attachments into OneDrive without a flow
Microsoft already ships an automation tool for this. It is worth being precise about where it stops being the cheaper option.
How do you save Outlook attachments to OneDrive automatically?
You connect Outlook over OAuth — a Microsoft consent screen, no password — describe the document in one sentence, and pick the OneDrive folder. Findest reads each new attachment, decides whether it matches, and writes it out renamed. There is no Power Automate flow to build or maintain.
-
Connect by consent, not by password
An app password will not work here: Microsoft shut off basic authentication for IMAP and POP on 30 April 2026. The Outlook button opens Microsoft's consent screen instead.
-
Pick a destination within that account's reach
The folder browser shows what the connected account can see: personal OneDrive, Business, SharePoint document libraries or Teams folders. What the account cannot reach does not appear.
-
Maintain nothing afterwards
No flow to repair when a connector changes, no steps to re-check at licence renewal. The rule is a sentence, and what changes over time is your documents, not the automation.
Where Power Automate stops being the cheap option
Power Automate genuinely does move Outlook attachments into OneDrive, and if every invoice you receive comes from one sender with one subject line, its templates will handle it on the free tier. The trouble starts when the routing depends on the document rather than the envelope.
At that point the flow needs a condition, and the condition can only test things Outlook exposes: who sent it, what the subject says, what the filename is. To branch on whether the PDF is an invoice or a delivery note you need a premium connector and a per-user licence — and you still have to maintain the branch by hand.
Who ends up owning the flow
A flow is software. Someone builds it, and then someone owns it — which in a small company means the person who built it, indefinitely. When the finance system changes its subject lines, the flow silently stops matching and nobody notices until the folder is a month short.
A rule written as a sentence has no branches to rot. There is no condition tied to a subject line that a vendor can change without telling you, because the sentence describes the document and the document has not changed.
One sentence instead of a condition tree
The interesting comparison is not features, it is maintenance. Below, the same routing decision written the way a flow forces you to write it, and written the way you would explain it to a colleague.
“Documents from the Madrid office”
Ties the rule to an office rather than a document, so it breaks the day someone in Madrid emails you something else.
“Signed contracts and addenda, already countersigned by both parties. Not drafts, not proposals awaiting signature.”
Signed and unsigned versions of the same contract look nearly identical to a filter; “already countersigned” is the distinction a reader can make and a filter cannot.
What lands in OneDrive
The document type, the counterparty and the date are read out of the file, then the name is rebuilt:
Contract_Contoso-Ltd_2026-02-03.pdf
It is written to Legal Contracts Signed in the account you connected. On the Business plan the same rule can write a second copy into Dropbox or Drive at the same time, which is the usual arrangement when legal and finance keep separate archives.
Outlook is the one provider where the app-password route is gone for good: Microsoft shut off basic authentication for IMAP and POP on 30 April 2026. Findest connects to Outlook over OAuth instead, which is why the Outlook button asks for consent rather than a password — and why an app password generated for Outlook will fail no matter how carefully it is typed.
Questions about Outlook and OneDrive
Can it file into SharePoint or a Teams library?
If the location is reachable from the OneDrive account you connected, you can pick it as a destination. Personal OneDrive, OneDrive for Business and the document libraries behind SharePoint and Teams all appear in the same folder browser.
What happens when my Microsoft password changes?
Nothing. OAuth consent survives a password change — that is one of the reasons it replaced app passwords. The connection only breaks if you revoke Findest's access, and if it does break you get an email about it.
Does this work with a shared mailbox?
It works with whatever the connected account can read over Graph. A shared mailbox that shows up in your Outlook will generally work; a mailbox you have not been granted access to will not.
Related questions
Save Gmail attachments to Google Drive, automatically
Gmail routes envelopes. It has never been able to route what is inside the attachment — which is the part you actually want filed. Read it →
When a Zap is the wrong shape for filing attachments
Zapier is a better product than Findest at almost everything. This page is about the one job where being narrow wins. Read it →
Why email filters miss what is inside the attachment
This is not a complaint about Gmail. It is a description of what envelope-level matching can and cannot decide — including the version of it we shipped and had to remove. Read it →
Try it against the contracts you already have.
Connecting Outlook takes a consent screen and no password. If it misreads your documents you will know within one mail cycle.