Runs entirely in your browser The snapshot you load is parsed locally and never sent anywhere (a Content-Security-Policy blocks all outbound connections). A snapshot can contain device and tenant identifiers (Org ID, Device ID, onboarding blob), so treat the .json file as sensitive and share it only as your organization allows.
Load an Endpoint DLP snapshot
Drop a EndpointDlpState_*.json file here, or…
Need the collector? Download Get-EndpointDlpState.ps1, then run it on the device you want to inspect.
How to generate a snapshot on the device
- Download
Get-EndpointDlpState.ps1and copy it to the device you want to inspect. - Open an elevated Windows PowerShell prompt (Run as administrator) in that folder and run:
It prints a pass/fail summary and writes
powershell -ExecutionPolicy Bypass -File .\Get-EndpointDlpState.ps1EndpointDlpState_<host>_<timestamp>.jsonin the current folder. - To decode the actual synced policies, also run the official MDE Client Analyzer, extract its
MDEClientAnalyzerResult_<ID>folder, and point the collector at it:The live on-device policy cache isn't always present in a readable form, so the analyzer output is the reliable source for the policy JSON. Without it, everything except the decoded policy still works.powershell -ExecutionPolicy Bypass -File .\Get-EndpointDlpState.ps1 -AnalyzerResultPath C:\path\to\MDEClientAnalyzerResult_XXXX - Bring the resulting
.jsonhere and load it above.