Skip to content
All projects
Compliance · GovernanceProduction

Microsoft Purview Records Management

Formal lifecycle governance for financial, legal and HR records — Record Labels, File Plan, Disposition Review and Regulatory Records.

Microsoft PurviewRecords ManagementRecord LabelsDisposition ReviewFile Plan

Difficulty

Advanced

Environment

Microsoft 365 / Purview

Deployment

Production

Est. Implementation

2–4 weeks

Related certifications:MS-102SC-400
GitHub
Overview

Executive Summary

This project deployed Microsoft Purview Records Management for a regulated organisation requiring formal lifecycle governance over financial, legal and HR records, establishing record declaration controls, immutable record protection, structured disposition workflows and centralised records visibility through the File Plan.

Records Management extends standard retention with record-level controls that prevent modification, enforce chain-of-custody, and satisfy regulatory obligations such as ISO 15489, GDPR Article 5 and SEC Rule 17a-4.

Context

Business Problem

Financial records could be modified or deleted before their retention period expired, there was no centralised visibility into retention labels across workloads, legal hold coverage was inadequate for declared records, and content was disposed of without review or approval.

Regulated organisations must be able to prove that financial, legal and HR records were preserved, protected and disposed of correctly. Without record-level controls, the organisation cannot demonstrate this to auditors or in litigation.

Business Risks

  • Financial records modified or deleted before retention period expires
  • No centralised visibility into retention labels across workloads
  • Legal hold inadequate for declared records during litigation
  • Disposition of records without review or approval

Compliance Concerns

  • ISO 15489 records management principles
  • GDPR Article 5 storage limitation and integrity requirements
  • SEC Rule 17a-4 style immutable record-keeping obligations
Approach

Solution Overview

A record label (MS102-Finance-Record) was created with a 7-year retention period and the "Mark items as a record" setting enabled, converting a standard retention label into a Record Label with enhanced governance controls, then published to Exchange Online, SharePoint Online and OneDrive.

The File Plan provides a single, centralised view of all record labels, retention durations and disposition settings, while Disposition Review assigns reviewers who must approve permanent deletion once the retention period lapses — closing the gap where records could previously be deleted without oversight.

Design

Architecture

Architecture Diagram
100%

Architecture diagram placeholder

Record Labels, File Plan and Disposition Review operating together over Exchange Online, SharePoint Online, OneDrive and Teams, giving centralised visibility and reviewer-approved disposition for declared records.
Stack

Technology Stack

Microsoft Purview Records Management

Record declaration, File Plan and disposition workflow

Record Labels

"Mark items as a record" retention labels with enhanced governance

Regulatory Record Labels

Highest-level protection — cannot be removed once applied

Disposition Review

Reviewer approval workflow before permanent deletion

Event-Based Retention

Contract and legal document retention triggered by an event

PowerShell / Microsoft Graph

Record label reporting and File Plan export

Environment

Lab Environment

Tenant
Patchthecloud.onmicrosoft.com
Admin Portal
compliance.microsoft.com
Licensing
Microsoft 365 E5
Workloads
Exchange Online, SharePoint Online, OneDrive, Teams
Scope
Organisation-wide + Finance adaptive scope
Build

Implementation

A phased, expandable walkthrough. Screenshots and evidence can be attached to each phase.

  1. Confirm Records Management is enabled for the tenant.

    • Navigate to compliance.microsoft.com → Solutions → Records Management
    • Confirm the solution is enabled
    • Review existing retention label estate before adding record labels
    Screenshots for this phase can be added here.
Automation

PowerShell

Illustrative example snippets — copy or download each script. Production values are placeholders.

Export all record labels

Get-RecordLabels.ps1
# Illustrative scaffold based on Get-RecordLabels.ps1
Connect-IPPSSession -UserPrincipalName admin@patchthecloud.onmicrosoft.com
.\scripts\Get-RecordLabels.ps1 -OutputPath ".\reports\record-labels.csv"

Export the full File Plan

Export-FilePlan.ps1
# Illustrative scaffold based on Export-FilePlan.ps1
Get-ComplianceTag | Select-Object Name, RetentionDuration, IsRecordLabel, RetentionAction |
  Export-Csv -Path .\reports\file-plan.csv -NoTypeInformation

Audit Records Management configuration

Get-RecordsManagementConfiguration.ps1
# Illustrative scaffold based on Get-RecordsManagementConfiguration.ps1
Get-CompliancePolicy | Where-Object Name -like "*Record*" |
  Select-Object Name, Enabled, Mode
Evidence

Configuration Screenshots

Click any tile to open the lightbox. Real screenshots will replace these placeholders.

Phase 2 · Record Labels

Phase 3 · File Plan

Phase 4 · Event-Based Retention

Phase 5 · Disposition Review

Phase 6 · Regulatory Records & Validation

Proof

Validation

  • Record Visible in File Plan

    MS102-Finance-Record appears with Is Record = Yes.

  • Published to All Workloads

    Record label policy visible across Exchange, SharePoint and OneDrive.

  • Modification Prevented

    Editing is blocked on declared record items.

  • File Plan Completeness

    Duration, action and record type all visible centrally.

  • Disposition Configured

    Reviewer assigned; approval workflow active.

  • Regulatory Record Immutability

    Label removal blocked by administrators once applied.

Reality

Challenges

Publishing is not the same as applying

Publishing a record label makes it available to users; it does not automatically apply the label to existing content — auto-apply policies are required for that.

Regulatory Records cannot be undone

Unlike standard Record Labels, Regulatory Records cannot be removed by administrators once applied, so they were thoroughly tested before any production consideration.

Insight

Lessons Learned

  • Publishing ≠ applying — auto-apply policies are required to label existing content, not just new content.
  • The "Unlock this record by default" option is useful during drafting phases before formally locking a record.
  • The File Plan is read-only in Records Management; configuration changes are made in Data Lifecycle Management.
  • Disposition review workflows require Microsoft 365 E5 or the Compliance add-on.
Outcome

Business Impact

Record Labels enforced

Immutable Records

File Plan

Centralised Visibility

Reviewer approval

Governed Disposition

PowerShell reporting

Administrative Efficiency

Capability

Skills Demonstrated

Microsoft Purview Records ManagementRecord Label & File Plan DesignDisposition Review WorkflowsEvent-Based RetentionRegulatory RecordsPowerShell / Microsoft Graph
Mapping

Related Certifications

Certifications this project maps to are highlighted.

MS-102SC-200SC-300SC-400AZ-900AZ-500SC-100
Reading

Related Blog Articles

Placeholder cards — future TechCertGuide integration.

Source

GitHub Repository

lokeshm-it/Microsoft-Purview-Records-Management

Public

Record Labels, File Plan, Disposition Review and Regulatory Records implementation.

Resources

Download Center

Project Case Study

PDF · Available soon

Architecture Diagram

PDF · Available soon

PowerShell Scripts

ZIP · Available soon

Technical Documentation

PDF · Available soon