Share via


Microsoft Planner support in Microsoft Purview

This documentation is focused on considerations unique to Planner. For general usage of Microsoft Purview, consult the resources available here, Microsoft Purview.

Data and capabilities available in Microsoft Purview

  • eDiscovery content search and legal hold.
  • Supported Planner content: Tasks in Plans that are shared with groups.
  • Includes Tasks, comments, and attachments.

Unsupported: Personal (roster) plans, plans in Loop components, premium plans (formerly projects)

eDiscovery for Planner Data

Applying a hold

A hold is a way to preserve content that is relevant to a case and prevents data from being deleted or modified in the tenant. End users of Planner won't be aware that a hold is placed on their tasks and plans. To apply a hold in Microsoft Purview eDiscovery, go to the Holds tab of the case and select New hold. Select the locations where you want to apply the hold. You can select from Exchange mailboxes, SharePoint sites, OneDrive accounts, Teams messages, and Planner plans. For Planner data, select the SharePoint site associated with the plan and check the box for Planner tasks. Review the summary of the hold and select Create this hold to apply it to the selected locations and content.

When a hold is applied, the task won't be deleted and is copied to the Preservation Hold Library of the SharePoint site. To validate that the hold is working, you can try to delete a Planner task that matches the hold conditions and then run a new collection and add it to the review set. The compound path of the task in the review set should include PreservationHoldLibrary in the path.

Note

Attachments on tasks are stored in SharePoint and comments are stored in Exchange. To apply holds to this content, Exchange and SharePoint locations need to be included as part of the hold.

Creating a collection

Collections in eDiscovery help you quickly scope a search for content across email, documents, and other content in Microsoft 365. Select New Collection and provide a name and description for the collection. Select from custodial data sources or choose any additional locations not set up as custodial or noncustodial data sources for the case. To filter for Planner tasks, use the KQL query to filter ItemClass = “IPM.File.Tasks”.

Note

Do not use the Tasks item type in the Query Builder. This will only return tasks created in Outlook. This type does not include tasks created in Planner.

Screenshot of the wrong task type selected in the Purview query builder.

Committing to a Review Set

Once the collection settings are reviewed and submitted, the collection will be added to a review set as a draft collection. You should be able to see a collection estimate and a preview of the collected items so you can validate the size and scope of the results before committing to a review set. Once a review set is created, Planner Tasks will appear as Documents. The source view of the document is designed to mimic the formatting of Planner Tasks. All data for the task is visible in the Metadata tab.

Screenshot of the task being rendered in Purview.

Exporting data

To export data from the review set, select export, give the export a name, and then select export.

Screenshot of the task being exported in Purview.

Exit the review set, select the export tab within the case and monitor the export job. After the export job is finished, select download. In the downloaded file, the basic rendering should be json files and the content should be the same as the source tab you see in the review set. If rich rendering and the exportModel settings are configured as exportModel: "Meta", then the files should export as the file extension you set in export model. Otherwise it will export as plain text with json.