Template family: Purview
Applies to: Microsoft Purview (compliance)
Where to find it: Secure → Purview
There are no Augmentt Default templates for Purview
Conditional Access, Defender and Intune all ship with pre-built Augmentt Default templates you can deploy as-is. Purview does not. The product declares two Purview policy types — PURVIEW_DLP and PURVIEW_RETENTION — but no default templates are seeded for either.
That is deliberate rather than an omission. Retention schedules and DLP rules encode a customer's own legal, regulatory and records-management obligations. A retention period that is correct for a Canadian accounting firm is wrong for a US healthcare provider, and a DLP rule that blocks credit card numbers would break a payments business. There is no safe default to ship, so Augmentt gives you the management surface and you author the policy.
What you can manage
Augmentt drives Purview through the Security & Compliance PowerShell cmdlets. The objects it can create, update and delete are:
| Object | What it is | Cmdlets used |
| Retention policy | The container that says where retention applies — which workloads, sites, or mailboxes are in scope | New-/Set-/Remove-RetentionCompliancePolicy |
| Retention rule | The container's actual behaviour — how long content is kept, and what happens at the end of the period | New-/Set-/Remove-RetentionComplianceRule |
| Retention label | A label users and policies can apply to individual items, carrying its own retention behaviour | New-/Set-/Remove-ComplianceTag |
| DLP policy | The container that says where data loss prevention applies | New-/Set-/Remove-DlpCompliancePolicy |
| DLP rule | The conditions and actions — what sensitive information types to detect, and what to do about them | New-/Set-/Remove-DlpComplianceRule |
A retention policy on its own does nothing. It needs at least one rule to define the actual retention behaviour, which is why the two are always created together.
Before you start
Licensing. Purview management is a separately-licensed module in Augmentt. Retention and DLP also carry their own Microsoft licensing requirements in the customer tenant.
Retention is difficult to reverse. Deleting a retention policy does not delete content that is already preserved, and content under retention cannot be permanently removed until the period lapses. Confirm the schedule with the customer before you deploy it.
Start in test mode for DLP. Microsoft lets a DLP policy run in test mode with or without policy tips. Use it. A DLP rule that blocks in production on day one generates helpdesk volume and erodes trust in the control.
Related
Teams policies in Augmentt — the other family with no default templates
All Augmentt Default templates
This article documents a management surface rather than a template. If Augmentt Default Purview templates are added to the product later, this page should be replaced with one article per template.