Home/Integrations/Microsoft Purview
Microsoft 365 integrationMicrosoft Purview governs, M-Files adds the business context
Purview stays your information protection layer. M-Files shows its sensitivity labels on your documents and links them to the client, project or contract they belong to.
Illustrative example
In short
The M-Files Microsoft Purview integration lets Purview and M-Files each do what they do best. Purview remains the authoritative information protection layer: sensitivity labels are defined and governed there and applied through Microsoft Office. M-Files shows those labels on supported documents, including encrypted ones, and adds the business context: client, project, contract and lifecycle. It works for content stored in Microsoft 365 Storage (SharePoint Embedded). Metadata-driven, automated labelling is announced for a future release. SoftAdvice sets up the storage and the metadata structure.
Two systems, each in its own role
M-Files complements Purview; it does not replace it.
Microsoft Purview
The information protection layer: sensitivity labels, protection and the policies across your Microsoft environment.
M-Files
The business context: which client, project or contract a document belongs to, its workflow, version and lifecycle.
Separate controls
M-Files permissions and Purview protections are separate controls. Both apply; neither overrides the other.
What works today, and what is announced
We keep both apart, so you know exactly what you can use now.
Announced for a future release
- Labels applied automatically from M-Files metadata
- Automated labelling
Available today
- Purview sensitivity labels visible in M-Files
- Users see when a file has an encrypted label
- Labels applied through Microsoft Office
- Labels defined and governed in Purview
Requirements
The integration applies to content stored in Microsoft 365 Storage, also known as SharePoint Embedded. Supported file types and the exact scope depend on your configuration; we confirm them for your environment before you rely on them.
Datasheet
- Storage
- Microsoft 365 Storage (SharePoint Embedded)
- Labels
- Defined and governed in Purview
- In M-Files
- Labels visible, also when encrypted
- Automated labelling
- Future release
Questions about M-Files and Purview
Does M-Files replace Microsoft Purview?
No. Purview remains your information protection layer. M-Files complements it with business context, workflows and lifecycle.
Can we apply labels from M-Files?
Labels are applied or changed through supported Microsoft Office experiences. Applying labels automatically from M-Files metadata is announced for a future release.
Does this change our M-Files permissions?
No. M-Files permissions and Purview protections are separate controls; both keep applying.
Which documents does this apply to?
Supported content stored in Microsoft 365 Storage (SharePoint Embedded). We check file types and scope for your environment during the demo.
Purview and M-Files in your environment
In one hour we show how sensitivity labels appear in M-Files and what your storage needs.