Create exact data match sensitive information type workflow classic experience

Creating and making an exact data match (EDM) based sensitive information type (SIT) available is a multi-phase process. They can be used in Microsoft Purview data loss prevention policies, auto-labeling, eDiscovery and certain content governance tasks. This article outlines the workflow and links to the procedures for each phase using the classic experience.

Tip

If you're not an E5 customer, you can try all the premium features in Microsoft Purview for free. Use the 90-day Purview solutions trial to explore how robust Purview capabilities can help your organization manage data security and compliance needs. Start now at the Microsoft Purview compliance portal trials hub. Learn details about signing up and trial terms.

Applies to

  • Classic experience

If you want to create an EDM SIT using the new experience see, Create EDM SIT new experience workflow .

Before you begin

Make sure you review:

The work flow at a glance

exact data match workflow phases

Phase What's needed
Phase 1: Export source data for exact data match based sensitive information type - Read access to the sensitive data
Phase 2: Create the schema for exact data match based sensitive information types - Access to the sensitive information type wizard in the compliance portal
- access to the Microsoft 365 admin center via Security & Compliance PowerShell
Phase 3: Hash and upload the sensitive information source table for exact data match sensitive information types - Custom security group and user account
- Hash and upload from one computer: local admin access to a computer with direct internet access and to host the EDM Upload Agent
- Hash and upload from separate computers: local admin access to a computer with direct internet access and host the EDM Upload Agent for the upload and local admin access to a secure computer to host the EDM Upload Agent to hash the sensitive information source table
- Read access to the sensitive information source table file
the schema file
Phase 4: Create exact data match sensitive information type/rule package - Access to the Microsoft Purview compliance portal
Test an exact data match sensitive information type - Access to the Microsoft Purview compliance portal

See also