How does this fit with Microsoft Purview?

The division of responsibility

Purview operates at the tenant level. It applies retention policies across SharePoint, Exchange, Teams, and OneDrive. It runs legal holds that preserve data during litigation. It provides eDiscovery search across tenant content. It enforces DLP policies that prevent sensitive-content exfiltration.

Our layer operates at the governed-document level. Template-driven creation, sequential approval workflows, automatic PDF publication, expiration reminders with human decisions, versioned history, document-specific audit logs.

The two layers see the same documents but focus on different properties. Purview governs how long documents are kept; we govern how they’re created, approved, and reviewed while they’re kept. Purview handles the “records management” scope; we handle the “active governance” scope.

Where they interoperate

• Retention. A document under our governance that falls within a Purview retention policy is preserved per that policy. The policy doesn’t break our versioning; our versioning doesn’t break the policy.
• Legal hold. A Purview legal hold preserves all versions of covered documents regardless of our lifecycle state. The hold continues through our normal approval/revision/archive transitions.
• eDiscovery. Purview eDiscovery searches find our governed documents (they’re SharePoint documents) with full content and metadata included.
• DLP. Purview DLP policies apply to our governed libraries the same way they apply to any SharePoint library.

What they don’t share

Expiration reminders (our active-review mechanism) are distinct from retention deletion (Purview’s mechanism). An expired document whose owner doesn’t re-certify moves to our archive with a documented reason; it’s not deleted. If Purview retention says “delete after 7 years,” that deletion happens when the retention clock runs out, independently of our expiration-reminder cycle.

This separation matters: expiration reminders drive review; retention drives eventual deletion. Customers sometimes conflate them during initial conversations; once the distinction clicks, both layers run comfortably together.

See Microsoft 365 as a compliance platform for deeper detail on the interoperation.