SharePoint Encryption vs Sensitivity Labels
What SharePoint encrypts by default, and when labels and bulk labeling are needed.

SharePoint encryption is on by default, at rest and in transit, but it only protects storage and connections. Sensitivity labels stay with each file and can control who opens it after it leaves the library. A library's default label does not reach files already stored there, so older libraries need labeling in bulk.
Yes, SharePoint Online is encrypted. Microsoft encrypts your files at rest and in transit as part of the service. But when a board member, an auditor or your own leadership asks "are our files protected?", encryption at rest is usually not what they mean. They want to know who can open a file once it has been shared, downloaded or attached to an email. Platform encryption does not answer that. Sensitivity labels can.
This article sets out what Microsoft encrypts by default, where that stops, and what to do about the years of files already sitting in your libraries.
What Microsoft encrypts by default
Microsoft's documentation on data encryption in OneDrive and SharePoint describes two layers.
In transit
Connections between users and the service use TLS, with 2048-bit keys. Data that moves between Microsoft data centers, for example for disaster recovery replication, is also encrypted.
At rest
There are two parts:
- BitLocker disk-level encryption, deployed across the service.
- Per-file encryption. Each file is broken into chunks, and each chunk is encrypted with its own key. Every update to a file is encrypted with its own key too. Microsoft states that this uses AES with 256-bit keys and is FIPS 140-2 compliant.
The encrypted content, the keys and the map needed to put a file back together are kept in three physically separate stores. Microsoft's point is that the information in any one of them is unusable on its own.
So the honest one-line answer is: yes, your SharePoint content is encrypted at rest and in transit, as Microsoft describes it for its multitenant service.
What platform encryption does not decide
That encryption protects the storage and the connection. It does not decide who is allowed to open a file. That is the job of SharePoint permissions and sharing settings.
The gap shows up in ordinary work. A loan officer downloads a borrower file to a laptop to finish it at home. A clinic manager attaches a staff list to an email for an outside payroll provider. A project lead shares a folder with a contractor and forgets to remove access. In each case the person had legitimate access, and the copy now lives outside the library, where the library's permissions no longer apply to it.
Microsoft makes the same point in its overview of sensitivity labels: content no longer stays behind a firewall, it roams across devices, apps and services. If you want protection to go with it, it has to be attached to the file itself.
What sensitivity labels add
Sensitivity labels in Microsoft Purview let you classify content and, where you choose, protect it. According to Microsoft:
- A label is stored in the file's metadata, so it stays with the content wherever it is saved.
- A label can apply encryption and content markings such as headers, footers and watermarks.
- Label encryption can restrict what specified people can do with the content, and that protection stays with the file.
- A label does not have to encrypt. You can label for classification only and add protection later.
- Labels can also be applied to containers such as SharePoint sites and Teams, to control external sharing and access from unmanaged devices.
Put simply: platform encryption protects the building. A label travels with the document.
If you want to start with the licenses you already have, our article on sensitivity labels on Business Premium or E3 covers what to protect first. For sharing settings, see how to enable SharePoint external sharing safely.
Default library labels cover new files, not old ones
SharePoint lets a site admin set a default sensitivity label for a document library. New files uploaded to that library, and existing files that someone edits there, get the label if they have none or have a lower-priority one. A label someone applied by hand is not overridden.
Microsoft lists one limitation that matters most for older libraries: a default label does not apply to existing files at rest in SharePoint. A library with ten years of documents will only pick up the label file by file, as people happen to edit them. The documents nobody touches, often the old ones you are most worried about, stay unlabeled.
Microsoft also documents a newer library option that carries SharePoint permissions with a file when it is downloaded. Its own documentation describes that setting as in preview, so test it before you rely on it.
Labeling existing libraries in bulk
This is where most labeling projects slow down. Designing the labels is a workshop. Applying them to what already exists is the long part.
Data governance and classification was the theme raised most often in our customer meetings in Q3 2026: 59 meetings across 15 customers. The question behind it is rarely "which labels should we have". It is usually "how do we get them onto everything we already have".
We built Sensitivity Label Manager for that job. It bulk updates Microsoft Purview sensitivity labels across large SharePoint environments, right inside SharePoint, with a full audit trail of the changes. That covers both first-time labeling of an existing library and relabeling when your label scheme changes.
A practical order of work:
- 1. Decide the few labels you need and what each one does.
- 2. Set default labels on the libraries that hold sensitive work, so new and edited files are covered.
- 3. Pick the existing libraries that matter most and label them in bulk.
- 4. Keep the audit trail, so you can show what changed and when.
If you would rather have the whole foundation set up for you, our Purview Accelerator is a fixed-scope implementation delivered in five phases over 6 to 8 weeks.
Next step
If your libraries are full of files that predate your labels, see how Sensitivity Label Manager labels them in bulk.
Want a second set of eyes?
Our team works with mid-market IT leaders to capture the upside of AI and the Microsoft cloud without the compounding risk. Start with a focused conversation.
Frequently asked questions
Is SharePoint Online encrypted at rest?
Yes. Microsoft uses BitLocker disk encryption plus per-file encryption, with a separate key for each chunk of each file, using AES 256-bit keys.
Does that encryption stop someone forwarding a downloaded file?
No. It protects storage and connections. Control over who can open a copy that has left the library comes from sensitivity labels that apply encryption.
Will a default library label cover the files already there?
No. Microsoft states that it does not apply to existing files at rest. They are labeled when edited, or you label them in bulk.
Do we have to encrypt with every label?
No. A label can classify content without any protection settings, and you can add protection later.
How CollabPoint can help
Turn this into action — the capability and fixed-scope programs behind it.
More articles
Is SharePoint Online encrypted at rest? What Microsoft encrypts by default, and what it doesn't protect you from
Is SharePoint encrypted at rest? Yes: BitLocker plus per-file AES 256-bit keys. See what Microsoft encrypts, what it doesn't stop, and when Customer Key fits.
Stop Editing PDFs: A Better Way to Manage Documents in Microsoft 365
PDF round-tripping quietly slows teams and breaks version control. Here's how to manage documents in Microsoft 365 natively, and when a PDF still makes sense.
SharePoint Skills: Your Complete Guide to Smarter Automation
The SharePoint automation skills that matter most aren't clicks, they're the patterns that let you automate document-heavy work with Power Automate and Lists.