Microsoft announced support for Microsoft Planner data in Microsoft Purview eDiscovery Premium in early 2024. On paper, this sounds like an important enhancement—but in practice, the current experience is incomplete, and the official documentation contains technical inaccuracies.
❌ Problem in the Microsoft Documentation
In Microsoft’s documentation, the following KQL query is suggested to filter for Planner tasks:
ItemClass = "IPM.File.Tasks"
However, this syntax is invalid in Purview. The operator = is not supported in KQL queries within Microsoft Purview eDiscovery.
✅ The correct syntax is:
ItemClass:"IPM.File.Tasks"With the corrected syntax, ItemClass:"IPM.File.Tasks" does return results—but only under specific conditions (see below).
✅ Planner Tasks Do Show Up – If You Use Groups Properly
We created a test environment using Microsoft Planner within a Microsoft 365 Group. Each task included meaningful metadata like labels, due dates, buckets, notes, and priorities:
The task board shows structured test data that simulates real-world planning scenarios.
In Microsoft Purview eDiscovery Premium, these tasks successfully appeared in the Review Set view—with full metadata:
The details pane displays all task metadata: title, labels, bucket, progress, and due dates.
This proves: Planner task data is discoverable—but only when properly stored in the background through M365 Group components like SharePoint.
❌ Legal Hold for Planner: Documented, but Not Functional
Microsoft’s documentation further claims that you can place a legal hold on Planner data by selecting the associated SharePoint site and checking an option for „Planner tasks.“
In reality, there is no checkbox for Planner anywhere in the UI:
Only SharePoint and mailbox locations are selectable—there is no Planner-specific hold toggle.
Even when applying a hold to the SharePoint site behind the M365 Group, deleted tasks are not preserved in the Preservation Hold Library. Microsoft’s guidance to verify this by checking the file path in a Review Set (for PreservationHoldLibrary) fails in practice—the tasks are simply gone.
🧪 Summary – What Works and What Doesn’t
| Feature | Result |
|---|---|
ItemClass = "IPM.File.Tasks" from docs | ❌ Invalid syntax |
ItemClass:"IPM.File.Tasks" | ✅ Works, with Group-based tasks |
| Tasks visible in Review Sets | ✅ Yes, with full metadata |
| Legal Hold for Planner (as described) | ❌ Not functional |
| Deleted tasks preserved via Hold | ❌ Not in our testing |
| Searchable notes, labels, buckets | ✅ Yes |
🛠 Practical Recommendations
- Always use Planner within a Microsoft 365 Group context
- Ensure the Group has an associated SharePoint site (storage is required!)
- Use the correct KQL syntax:
ItemClass:"IPM.File.Tasks" - Do not rely on Legal Hold to preserve task content
- For stronger data retention, consider Power Automate flows to export task data to Excel or SharePoint—making it fully discoverable and auditable
📌 Conclusion
Planner data is partially supported in Microsoft Purview eDiscovery Premium. The Review Set view does include real Planner tasks—but only if the task is part of a Microsoft 365 Group and stored via SharePoint.
However, Microsoft’s documentation is misleading:
- The provided KQL example is invalid
- The claim that Planner is protected via Legal Hold is, as of now, not true in practice
If you need defensible eDiscovery or auditing of Planner tasks, you should consider structured data exports and SharePoint-based retention until native support improves.
Schreibe einen Kommentar