Is OneDrive End to End Encrypted?

The short answer: no. Microsoft OneDrive is not end to end encrypted. Your files are encrypted in transit and at rest, but Microsoft holds the keys. That distinction matters more than most explainer articles let on, and it matters especially now that AI tools are reaching into cloud storage through OAuth integrations you probably approved without reading. If you are asking "is OneDrive end to end encrypted," you are really asking whether Microsoft can read your files. They can. So can a government with the right paperwork.

Key Takeaways

• OneDrive encrypts files at rest (AES 256-bit, per-file keys) and in transit (TLS), but Microsoft controls the encryption keys. This is server-side encryption, not end to end encryption.
• OneDrive Personal Vault adds identity verification steps and stores synced files in a BitLocker-encrypted container on Windows, but it is still not zero-knowledge. Microsoft can still access the contents.
• A 2025 vulnerability in the OneDrive File Picker exposed a broader risk: hundreds of web apps, including ChatGPT and Slack, could gain read access to your entire drive even when you intended to share a single file.
• True OneDrive end to end encryption would require client-side key management where only you hold the decryption key. Microsoft does not offer this. Third-party tools like Cryptomator can layer it on.
• The encryption-versus-privacy gap is widening as AI copilots and agents index cloud files. Encrypted at rest means little if your provider's own AI can read the plaintext.

What Kind of Encryption Does OneDrive Actually Use?

OneDrive uses AES 256-bit encryption at rest and TLS encryption in transit. Each file gets its own unique encryption key, and each file update generates a new key. The keys themselves are stored separately from the content, which is a meaningful architectural choice. The implementation is FIPS 140-2 compliant. All of this is real security engineering.

But it is server-side encryption. Microsoft generates the keys, Microsoft stores the keys, Microsoft can decrypt the files. The encryption protects you from a third party who breaches Microsoft's storage layer. It does not protect you from Microsoft.

For enterprise customers, Microsoft offers Customer Key, which lets organizations bring their own encryption keys managed through Azure Key Vault. This adds a layer of control: Microsoft cannot decrypt data without access to your Customer Key. But Customer Key is only available on Microsoft 365 E5 plans, requires substantial setup, and still relies on Microsoft's infrastructure for key orchestration. It is closer to envelope encryption than to true client-side zero-knowledge encryption.

Does OneDrive Personal Vault Provide End to End Encryption?

No. Personal Vault is an identity-gated folder, not a zero-knowledge vault. It requires re-authentication (via biometric, PIN, or two-factor) to access, and it auto-locks after a period of inactivity. On Windows, synced Personal Vault files are stored in a BitLocker-encrypted VHD container rather than the regular OneDrive sync folder. This is a tiny encrypted drive inside your real drive.

The common misconception is that Personal Vault provides something approaching zero-knowledge encryption. It does not. The files inside Personal Vault are still stored on Microsoft's servers with Microsoft-held keys, the same as any other OneDrive file. The vault adds access friction, not cryptographic isolation.

Office Watch put it plainly: Personal Vault is not the fully encrypted online storage customers have been asking for. Files saved on Microsoft's servers remain accessible by the company or government agencies. Full online encryption would use a key known only to the customer, like Apple's Advanced Data Protection. Microsoft has not shipped anything equivalent for OneDrive.

There is also a practical limitation worth knowing. The free OneDrive plan limits Personal Vault to three files. A Microsoft 365 subscription removes the limit. So the "secure" storage option is effectively a paid feature, and even the paid version does not deliver the encryption model the name implies.

Why Does It Matter That Microsoft Holds the Keys?

Because key custody determines who can read your data. When a provider holds the encryption keys, three things follow.

First, the provider can comply with legal requests by decrypting your files and handing them over. Microsoft does not offer zero-knowledge encryption, which gives Microsoft developers and the U.S. government access to data stored in OneDrive if required. This is not speculation; it is the architectural consequence of server-side key management.

Second, the provider's own internal systems can process your plaintext data. This includes content scanning, policy enforcement, and increasingly, AI features that index your files to provide search, summaries, and recommendations. When your provider's AI copilot can read your documents, "encrypted at rest" describes only the storage layer, not the access reality.

Third, any breach of the provider's key management infrastructure exposes your data in cleartext. Per-file keys stored separately from content is good defense-in-depth, but it is not the same as a model where the provider never possesses the key at all.

How Does OneDrive Compare to Other Cloud Providers on Encryption?

The landscape is not as differentiated as marketing would suggest. Most mainstream cloud storage services use server-side encryption with provider-held keys. OneDrive for Business encrypts at rest and in transit and supports HIPAA BAAs on eligible plans, which puts it roughly on par with Google Drive and Dropbox for regulated workloads.

The meaningful outlier is Proton Drive, which offers zero-knowledge end to end encryption by default: files are encrypted on the client before upload, and Proton never holds the decryption key. Apple's iCloud with Advanced Data Protection uses a similar model for most data categories. These are architecturally different from OneDrive, not just feature-different.

For users who want zero-knowledge encryption on top of OneDrive (or any other cloud provider), client-side encryption tools like Cryptomator create an encrypted virtual drive that syncs opaque ciphertext blobs to the cloud. The provider sees only encrypted data. The tradeoff is reduced convenience: no web-based preview, no collaborative editing on encrypted files, no mobile quick access without the Cryptomator app.

What Is the OneDrive File Picker Vulnerability, and Why Should You Care?

In May 2025, security researchers at Oasis Security reported a flaw in the OneDrive File Picker that reframed the entire "is OneDrive secure" question. The problem was not in the encryption layer. It was in the OAuth permission model.

When a web application uses the OneDrive File Picker to let you upload or select a file, the consent screen suggests you are granting access to a specific file. But the underlying OAuth token actually grants the application full read access to your entire OneDrive. Every file, every folder. The consent prompt was misleading, and the OAuth scopes were overly broad.

Hundreds of widely used web applications were affected, including ChatGPT, Slack, Trello, and ClickUp. If you had used the OneDrive File Picker in any of these apps, those apps had (or could have) read access to your entire cloud storage. Not the one file you selected. Everything.

This matters because the conversation about OneDrive end to end encryption usually focuses on whether Microsoft can read your files. The File Picker flaw showed that the more immediate risk might be which third-party apps can read your files, with your apparent consent, through permission models you did not fully understand.

How Does This Compare to Google Drive's OAuth Model?

Google Drive offers fine-grained OAuth scopes like drive.file, which restricts an application's access to only files it created or that the user explicitly selected. Microsoft's implementation lacked equivalent granularity, granting unrestricted access to all OneDrive content when a user interacted with the File Picker.

As of mid-2025 reporting, Microsoft acknowledged the disclosure but provided no fix or fix timeline. The structural issue (broad OAuth scopes combined with vague consent screens) remained. This is worth keeping in mind every time you see a "Connect OneDrive" button in a productivity app or AI tool.

What Should OneDrive Users Know Before Connecting AI Tools?

The intersection of cloud storage and AI is where the encryption question gets genuinely interesting, and genuinely underserved by most security content.

When you connect OneDrive to an AI tool (a copilot, a writing assistant, a data analysis app), the tool typically requests OAuth access to read your files. The encryption-at-rest on Microsoft's servers is irrelevant at this point. The AI tool receives the plaintext through the API. What happens to that plaintext depends entirely on the AI tool's data handling practices, not on OneDrive's encryption.

Consider the chain: your file is encrypted at rest on Microsoft's servers, decrypted by Microsoft when the API serves it, transmitted over TLS to the AI application, and then processed by whatever model infrastructure that application uses. If the AI tool sends your file content to a model provider for inference, your data has now touched at least three organizations' infrastructure. OneDrive's AES 256-bit encryption protected exactly none of those hops beyond the first TLS tunnel.

This is not a theoretical concern. The OneDrive File Picker vulnerability demonstrated that apps could silently acquire read access to an entire drive. Combine that with AI tools that process file contents through third-party model APIs, and the attack surface extends well beyond what "encrypted at rest" was designed to address.

If you are syncing sensitive files to OneDrive and also connecting AI tools to your Microsoft account, you are implicitly trusting every application in that chain with your plaintext data. The encryption label on the storage layer is doing less work than you think.

Can You Add True End to End Encryption to OneDrive?

Yes, but not through Microsoft. You need client-side encryption software that encrypts files before they reach OneDrive's sync folder. Cryptomator is the most commonly cited open-source option. It creates an encrypted vault that appears as a virtual drive on your machine. Files written to the vault are encrypted locally, and only the ciphertext syncs to OneDrive. Microsoft sees only opaque blobs. No key, no access.

The downsides are real. You lose web-based access to those files (you cannot open them in the OneDrive browser interface). Collaborative editing breaks (encrypted files cannot be opened by Office Online). Search across encrypted files does not work. Mobile access requires the Cryptomator app. These are fundamental tradeoffs of client-side encryption, not bugs in any particular tool.

For enterprise users, Azure Blob Storage supports client-side encryption at the SDK level, but this is a developer-facing capability for custom applications, not a consumer OneDrive feature.

The honest summary: if you want true zero-knowledge encryption for files stored in OneDrive, you will need to layer it on yourself, and you will give up the convenience features that make OneDrive useful as a collaboration tool.

What Does "Encrypted" Actually Mean When Your Provider Holds the Keys?

This is the distinction most explainer articles get wrong, and it is worth stating precisely.

Server-side encryption at rest (what OneDrive provides) protects against a narrow but important threat: an attacker who gains physical access to the storage media, or a breach that exposes raw storage without compromising the key management layer. This is not nothing. It is a meaningful defense against certain classes of infrastructure attack.

End to end encryption (what OneDrive does not provide) protects against a broader set of threats: the provider itself, legal compulsion directed at the provider, insider threats at the provider, and any breach that compromises the provider's key management. In an end to end encrypted system, the provider stores data it cannot decrypt. The key exists only on the client.

When people ask "is OneDrive end to end encrypted," they usually mean: "Can Microsoft read my files?" The answer is yes. And with it, any government with jurisdiction over Microsoft.

AES 256-bit is a strong cipher. FIPS 140-2 compliance is a meaningful certification. Per-file keys stored separately from content is good architecture. None of that changes who holds the keys. Encrypted does not mean private when the provider can decrypt at will.

Is Microsoft Likely to Add End to End Encryption to OneDrive?

There is no public indication that Microsoft plans to ship true client-side, zero-knowledge encryption for OneDrive. A March 2025 Microsoft Q&A moderator response confirmed that OneDrive does not currently provide built-in client-side end-to-end encryption where only the user holds the keys. No roadmap item or preview feature has been announced since.

There are structural reasons this is unlikely to change soon. Microsoft's entire productivity stack (Office Online, Copilot, search, compliance tools) depends on server-side access to file contents. End to end encryption would break Copilot's ability to index and summarize your documents. It would break real-time co-authoring in Word and Excel. It would break compliance and eDiscovery workflows that enterprise customers pay for.

Apple managed to ship Advanced Data Protection for iCloud in part because Apple's productivity tools are primarily local applications, not web-based editors that need server-side access to file contents. Microsoft's architecture is fundamentally more server-dependent, which makes the same move harder.

This is not a criticism of Microsoft's engineering. It is a description of architectural constraints that make different encryption models more or less compatible with different product strategies. Microsoft chose deep server-side integration. That choice is incompatible with zero-knowledge encryption. Both are legitimate engineering decisions. They just serve different threat models.

What Should You Actually Do?

If you are using OneDrive for files you would not want Microsoft, a government, or a breached third-party app to access, you have a few concrete options.

Use client-side encryption (Cryptomator or similar) for sensitive files, accepting the convenience tradeoffs. Review which third-party applications have OAuth access to your OneDrive account, and revoke any you do not actively use. Be particularly cautious about AI tools that request OneDrive access through the File Picker, given the documented over-permissioning issue. For files that need both security and collaboration, consider whether a zero-knowledge provider (Proton Drive, Tresorit) is a better fit for that specific use case, even if OneDrive remains your primary storage.

And be precise about what you are protecting against. OneDrive's encryption is real and competent for what it does. It protects your files from infrastructure-level attacks. It does not protect your files from Microsoft, from legal process, or from third-party apps you have granted access to. Those are different threat models, and they require different mitigations.

If you are looking for an AI assistant that treats file encryption as a design constraint rather than an afterthought, and where transfers are zero-knowledge encrypted by default, start a free 7-day trial, no card required.

Michael C.

Founder & Principal Engineer, Selina Labs

Michael builds Selina, a privacy-first AI that remembers you across conversations. He ships security-sensitive AI in production — real attacks, real fixes, measured in minutes and dollars — and writes about privacy, security, and LLMs from that seat. Top Rated Plus and expert-verified on Upwork.

• www.upwork.com
• x.com
• medium.com
• selinalabs.io