DLM Diagnostics

Investigate and resolve Microsoft Purview Data Lifecycle Management issues in Exchange Online. Follow the decision tree below to identify the correct troubleshooting guide, then load the matching reference file for step-by-step diagnostic instructions.

Prerequisites

Before running any diagnostic commands, ensure both PowerShell sessions are connected:

Connect-ExchangeOnline -UserPrincipalName '<admin@contoso.com>' -ShowBanner:$false
Connect-IPPSSession -UserPrincipalName '<admin@contoso.com>' -ShowBanner:$false

Safety Rules

Only execute read-only commands. Allowed cmdlet verbs: Get-*, Test-*, Export-*.

Never execute mutating commands — Set-*, New-*, Remove-*, Enable-*, Start-*, Invoke-* cmdlets must only be returned as text recommendations for the admin to review and run manually.

Decision Tree

Identify the reported symptom and load the matching reference:

If the issue does not match a specific symptom above, or for ad-hoc investigations, see diagnostic-commands.md for a quick-reference of common diagnostic commands. For adaptive scope validation commands, see adaptive-scope.md.

Workflow

1. Identify the symptom from the user's description using the decision tree above.
2. Load the matching reference file — read it fully before starting the investigation.
3. Execute diagnostic commands step by step using the run_powershell MCP tool, following the reference guide's sequence.
4. Interpret results at each step — the reference guide explains what to look for and how each finding maps to a root cause.
5. Cross-reference — some guides link to sibling references (e.g., policy distribution failures link to policy-stuck-error.md). Load those when directed.
6. Report findings — summarize the root cause, present the root-cause confirmation table, and provide the recommended remediation actions as text for the admin to review.
7. Review the execution log — use the get_execution_log MCP tool to include a full audit trail of all commands run during the investigation.

Output Format

Present findings to the user in this structure:

## Investigation Summary

**Symptom:** <what was reported>
**Mailbox/Policy:** <target>

## Diagnostic Steps

✅/❌ Step N — <step name>
   Finding: <what was found>
   Command: <command that was run>

## Root Cause

<identified root cause from the reference guide's root-cause table>

## Recommended Actions

⚠️ These commands are NOT executed automatically. Review and run manually:
- <remediation command 1>
- <remediation command 2>