Manage your exact data match schema

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.

Editing the schema for EDM-based classification manually

If you want to make changes to your EDM schema, for example the edm.xml file, such as changing which fields are used for EDM-based classification, follow these steps:

Tip

You can change your EDM schema and sensitive information table source file to take advantage of configurable match. When configured, EDM will ignore case differences and some delimiters when it evaluates an item. This makes defining your xml schema and your sensitive data files easier. To learn more see, Using the caseInsensitive and ignoredDelimiters fields.

  1. Edit your edm.xml file (this is the file discussed in the Create the schema for exact data match based sensitive information types.

  2. Connect to Security & Compliance PowerShell.

  3. To update your database schema, run the following command:

    Set-DlpEdmSchema -FileData ([System.IO.File]::ReadAllBytes('.\\edm.xml')) -Confirm:$true
    

    You will be prompted to confirm, as follows:

    Confirm

    Are you sure you want to perform this action?

    EDM Schema for the data store 'patientrecords' will be updated.

    [Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):

    Tip

    If you want your changes to occur without confirmation, don't use -Confirm:$true in Step 3.

    Note

    It can take between 10-60 minutes to update the EDMSchema with additions. The update must complete before you execute steps that use the additions.

Removing the schema for EDM-based classification manually

If you want to remove the schema you're using for EDM-based classification, follow these steps:

  1. Connect to Security & Compliance PowerShell.

  2. Run the following command, substituting the data store name of "patient records" with the one you want to remove (using the patientrecords store as an example):

    Remove-DlpEdmSchema -Identity 'patientrecords'
    

    You will be prompted to confirm:

    Confirm

    Are you sure you want to perform this action?

    EDM Schema for the data store 'patientrecords' will be removed.

    [Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):

    Tip

    If you want your changes to occur without confirmation, don't use -Confirm:$true in Step 2.

Edit or delete the EDM schema with the wizard

  1. Open Compliance center > Data classification > Exact data matches.

  2. Choose EDM schemas.

  3. Choose the EDM SIT you want to edit.

  4. Choose Edit EDM schema or Delete EDM schema from the flyout.

Important

If you want to remove a schema, and it is already associated with an EDM sensitive info type, you must first delete the EDM sensitive info type, then you can delete the schema.