The email "Incompatible sensitivity label detected" reports a conflict: a file carries a higher-priority sensitivity label than the SharePoint site it sits in. If that combination is intended, as in a typical workflow with external partners, a SharePoint administrator can switch the email off for the whole tenant. If it is not intended, correct the label or the site configuration.
What triggers the email
According to Microsoft's documentation on labels for Teams, groups and sites, SharePoint compares the priority of the file's label with the site's label. When a more highly classified file sits in a lower-classified site, SharePoint records a "Detected document sensitivity mismatch" event and emails the person who uploaded the file and the site owners. This happens when a file is uploaded, copied or moved into the site.
This is not the same as a default label for a document library. Default labels for libraries follow their own rules.
A typical workflow at our customers
Many documents are first created in an internal SharePoint site and receive a label there, for example through the default label of a label policy. They are then copied or moved to a workspace used for collaboration with B2B partners or other external parties. That workspace carries a lower-priority label. As soon as documents arrive there, SharePoint sends the warning email. For users the conflict is expected in this workflow, but the emails lead to questions for the support team.
We consider this workflow good practice: the file keeps its stricter protection even though the workspace for external collaboration is classified lower. If the notice is not needed, it can be switched off.
Check whether the combination is intended
Before making the change, compare the file and site labels, the site's sharing purpose and the permissions of external guests. If the combination is intended, as in the example above, explain the background to users and add an internal help link if useful. If it is not intended, correct the label or the site configuration. Suppressing the email does not fix a classification error.
Switching the email off
Prerequisites:
- The SharePoint Online Management Module for PowerShell is installed.
- The account you use to connect to the tenant has the SharePoint Administrator role activated.
In a PowerShell session connected to the tenant:
Set-SPOTenant -BlockSendLabelMismatchEmail $True # suppress the notification
Set-SPOTenant -BlockSendLabelMismatchEmail $False # switch the notification back onMicrosoft documents the parameter in Set-SPOTenant. It suppresses the email; the mismatch event is still recorded in the audit log.
What to keep in mind
- The setting applies to the whole tenant, not to individual sites. Agree the change with the security and SharePoint teams responsible.
- After the change, check the audit log to confirm that mismatch events still appear in your tenant.

