Implement and manage data classification
From a business requirement to a detection requirement
A privacy officer asks you to make sure nobody emails a completed patient intake form outside the company. Before you open any policy, split that sentence into two decisions: what Microsoft Purview must recognize (the form, the identifiers on it) and what must happen when it does (a label, a block, a retention action). This topic covers the first decision, the detection side of Microsoft Purview Information Protection, and the classification taxonomy it serves. For handling, the Microsoft SC-401 study guide skills measured[1] lists 'Define and create sensitivity labels for items and containers' under Implement and manage sensitivity labels in Microsoft Purview and 'Create and manage data loss prevention policies' under Create and configure data loss prevention policies.
Know your data, then protect it
Purview presents its information protection capabilities as tools to know your data, protect your data, and prevent data loss[2]; classification is the know-your-data step. Purview identifies items in three ways[3]: manually by users, by automated pattern recognition with sensitive information types (SITs), and by machine learning with trainable classifiers. Classifier is the umbrella term: the Classifiers page[4] of the Microsoft Purview portal (formerly the Microsoft Purview compliance portal) brings SITs, named entities, exact data match, trainable classifiers, credentials, and fingerprinting together, and you reach it under Information Protection, Data Loss Prevention, or Data Security Posture Management (DSPM).
Requirements become categories people understand
Classification has a second sense: your organization's classification taxonomy of sensitivity levels, which falls under this skill's first bullet[1], 'Identify sensitive information requirements for an organization's data'. Microsoft's guidance is to name sensitivity labels according to your organization's classification taxonomy[5] for different sensitivity levels, using terms that make sense to users (for example Personal, Public, General, Confidential, and Highly Confidential), to give each label a tooltip with specific examples, and to always test and tailor label names and tooltips with the people who need to apply them. The same guidance recommends a working virtual team that identifies the business and technical requirements. Because the taxonomy describes sensitivity levels, a scheme that only names departments (Finance, HR) leaves users without the handling decision a label is meant to carry.
Detection and handling are separate settings
A classifier supplies evidence about content; it never lists who may read it. SITs are consumed by data loss prevention (DLP) policies, sensitivity labels, retention labels, insider risk management, communication compliance, and auto-labeling policies[3], and each consumer decides the action. The label side can also stop at identification: you can apply a label without any protection settings[6], which gives users a visual mapping of data sensitivity and produces usage reports and activity data, and add protection settings later.
The figure below traces the classification loop: a business requirement selects a classifier, a label or policy acts on the classifier's matches, the explorers (Data explorer and Content explorer below) show what was classified, and Match and Not a Match feedback[7] is used to tune the classifier.
Write the detection requirement and the handling requirement as two separate lines: a classifier answers the first, a label or policy answers the second.
Classifier types and what each compares content against
Choosing a classifier is easier once you see that each type compares content with something different. This section sorts the types on the Classifiers page by that comparison and covers the ones Microsoft supplies ready-made.
All types except trainable classifiers are SITs. SITs are pattern-based classifiers[3] that detect information such as social security, credit card, or bank account numbers, and Microsoft groups them as built-in, named entity, custom, and exact data match SITs; document fingerprinting[8] also creates a SIT, from a standard form. Microsoft's pattern-based there describes every SIT, EDM included. Within SITs, this guide's narrower pattern-based SIT (a grouping for this guide, not a Purview menu name) means built-in, named entity, credential, and custom SITs matching a regular expression, keyword list, or function, beside the two SIT types that compare content with something you upload, EDM SITs and fingerprint SITs created from a standard form:
| Classifier type | Compares content against | Where this topic covers it |
|---|---|---|
| Pattern-based SIT | A regular expression, keyword list, keyword dictionary, or function, plus supporting evidence | This section and the four custom SIT sections that follow |
| Fingerprint SIT | The word pattern of a blank form | Document fingerprinting |
| EDM SIT | Hashed values from your own source table | The two exact data match sections |
| Trainable classifier | What it learned from example items | Trainable classifiers |
Built-in SITs: use as-is or copy
Microsoft-created SITs show up in the portal by default; they can't be edited, but you can copy them as templates[3] for custom SITs. When a built-in pattern meets the requirement, use it and avoid maintaining a detector of your own; when it needs organization-specific keywords, proximity, or checks, copy it and edit the copy. A few built-in SITs can't be copied[9]: Canada driver's license number, EU driver's license number, EU national identification number, EU passport number, EU social security number or equivalent identification, EU tax identification number, International classification of diseases (ICD-10-CM), International classification of diseases (ICD-9-CM), and U.S. driver's license number. A SIT with 10 text processors or restricted text processors (such as keyword lists, regex, keyword dictionaries, or functions) can't be copied from the UI directly; copy it with PowerShell instead.
Named entity SITs: bundled or unbundled
Named entity SITs[10] are dictionary- and pattern-based classifiers that detect person names, physical addresses, and medical terms and conditions, and they can't be edited or copied[3]. They come in two forms:
- A bundled named entity SIT, such as All full names or All physical addresses, detects all possible matches in its class; use it as broad criteria.
- An unbundled named entity SIT, such as Australia Physical Addresses or Blood Test Terms, has a narrower focus, such as a single country or region or a single class of terms; use it when a policy needs a narrower detection scope.
They suit open-ended requirements such as recognizing names you have never seen; a keyword list of known customer names only matches the names on it. Two prerequisites apply: Entity Match and other advanced classifiers are offered only to users with E5 licenses[10], and using a bundled SIT in an Endpoint DLP policy requires the Endpoint DLP setting Advanced classification scanning and protection[3].
Credential SITs: the bundle or one member
The All credentials SIT contains all the credential scanning SITs available in the portal[3], and each member is a credential scanning SIT that can be used standalone. Choose All credentials when any credential counts; choose the single member when only one credential type is in scope, because the bundle also matches every other credential type. Credential scanning SITs require an E5 license.
The figure below shows the classifier types as nested groups: SITs (pattern-based, fingerprint, and EDM) beside trainable classifiers (pretrained and custom).
Start from what the requirement must compare content against, check whether a built-in, named entity, or credential SIT already does it, and build something custom only when none does.
Anatomy of a custom SIT pattern
Every custom SIT, whether built from scratch or copied from a built-in one, is assembled from the same parts; this section defines them before the next sections refine them. A SIT entity has a name, a description, and a pattern[3], and each pattern consists of four components:
| Pattern component | What it is |
|---|---|
| Primary element | What the SIT looks for: a regular expression with or without checksum validation, a keyword list, a keyword dictionary, or a function |
| Supporting element | Corroborative evidence, such as the keyword Social Security Number near a nine-digit number, that raises confidence that a match is real |
| Confidence level | High, medium, or low, reflecting how much supporting evidence was found with the primary element |
| Proximity | The number of characters allowed between a supporting element and the primary element |
Choose the primary element by the kind of requirement: a regular expression for a structured identifier, a keyword list or keyword dictionary for known terms, or one of the preconfigured functions[9]. A SIT can hold several patterns, each with different elements and confidence levels, which is how one SIT returns a high-confidence match when strong evidence is present and a lower-confidence match when little is. Custom SITs created in the portal are added to the Microsoft.SCCManaged.CustomRulePack rule package. A rule package[11] is the XML container for SIT rules, identified, like each rule in it, by a unique GUID (Microsoft's procedures also say rule pack, and rule collection for an exported set); Creating a custom SIT in Security & Compliance PowerShell shows its skeleton. A deterministic format, such as a document ID shaped like a timestamp, needs a regular expression rather than a trainable classifier, because the format can be written down exactly.
Confidence levels
The three levels have values: low is 65, medium is 75, and high is 85[3]. High confidence returns the fewest false positives but might return more false negatives; low or medium returns more false positives but few to zero false negatives. Each selection includes the levels above it: low returns low, medium, and high matches; medium returns medium and high; high returns only high. An instance count, also called the occurrence or match-count threshold, sets how many matches a policy needs, and Microsoft suggests high-confidence patterns with low instance counts (say five to 10) and low-confidence patterns with higher counts (20 or more). The count and the confidence level do different jobs: the level reflects the evidence behind each match, so raising the count never repairs an overbroad primary pattern.
Proximity needs the whole supporting value
Proximity counts characters, and a supporting element must fall entirely inside the window. In Microsoft's example a nine-digit primary element needs an AccountNumber, Name, or DateOfBirth value within 250 characters, and a window that extends into the Name value without including the entire value doesn't match[3]. Proximity and confidence are separate settings: picking a higher confidence level never widens the window, so evidence that legitimately sits farther away needs a larger proximity value, and a wider window is worth testing so that unrelated records nearby don't supply accidental corroboration.
Regular expression rules
Purview SITs use the Boost.RegEx 5.1.3 engine[9], and custom SIT regex patterns must follow three rules:
- Don't use positional anchors such as
^and$; scanning gives no guarantee where content starts or ends. - Use one primary capturing group, the only capturing group, with noncapturing groups
(?:...)for any other grouping. - Put every match variant inside that single group with
|; top-level alternation between separate capturing groups is blocked during validation.
A valid pattern: three ID formats as alternatives inside one capturing group (Microsoft's example)
(?:[\s,;])([A-Z]{2}[0-9]{3}|[A-Z]{2}[A-Z]{4}[0-9]|[A-Z]{2}[0-9]{5})(?:[\s,;])
How the parts decide a match
The figure below follows one candidate through the four pattern components in the table above: the primary element matches, supporting evidence is sought inside the proximity window, the evidence found sets the confidence level, and a policy keeps the match only if that level meets the policy's own confidence setting; otherwise the match is dropped.
A pattern's accuracy therefore rests on three separate controls: the primary element decides what is a candidate, proximity decides which nearby evidence counts, and the confidence level decides how much evidence a policy demands.
Refining what a SIT pattern matches
Once a pattern's parts exist, accuracy comes from refining them, and each refinement fixes a different kind of error: a vocabulary that is too small or changes often, an identifier with the right shape that is still invalid, a known value that should never match, or Chinese or Japanese mixed with single-byte text, which Purview's added word spacing splits.
Keyword lists and keyword dictionaries
Both supply vocabulary, as a primary or a supporting element. Keyword lists are limited in size[12] and, in SITs created with PowerShell, need XML edits to change. Keyword dictionaries are simpler to manage at larger scale and support any language; all dictionaries in a tenant share a combined limit of 1 MB after compression, close to one million characters. A changing vocabulary, such as a list of project code names, therefore belongs in a dictionary rather than in a regular expression that hard-codes every value. In the portal you add a dictionary while creating or editing a SIT pattern: upload a dictionary file in TXT or CSV format, choose from existing dictionaries, or enter keywords manually and name a new dictionary. In Security & Compliance PowerShell, put each keyword on a separate line in a text file saved with Unicode encoding, then import it:
Creating a keyword dictionary from a Unicode text file (Microsoft's procedure)
# Read the Unicode-encoded file (one keyword per line) as bytes
$fileData = [System.IO.File]::ReadAllBytes('<filename>')
# Create the dictionary from those bytes
New-DlpKeywordDictionary -Name <name> -Description <description> -FileData $fileData
Validators: is a well-shaped identifier valid?
A regular expression checks only shape; regular expression validators[13] test meaning:
- The checksum validator multiplies each digit by a weight, applies a modulus, and compares the result with the check digit at a set position; give the check digit weight 0 if it isn't part of the calculation.
- The date validator checks a date embedded in the identifier, in a chosen date format, starting at an offset; a date that occupies the first six digits has offset
0. - The Luhn check validator requires the match to pass the Luhn algorithm.
- Function processors such as
Func_India_Aadharvalidate your own regular expression with the logic a built-in SIT requires.
A supporting keyword can't do a validator's job: an employee keyword next to a nine-digit number says nothing about whether its first six digits are a valid hire date.
Additional checks: drop known false positives
Additional checks[13] change which matches count without rewriting the primary pattern:
| Additional check | What it does |
|---|---|
| Exclude specific matches | Ignores listed values, such as the test card number 4111111111111111 |
| Starts or doesn't start with characters | Requires or rejects given leading characters |
| Ends or doesn't end with characters | Requires or rejects given trailing characters |
| Exclude duplicate characters | Ignores matches whose digits are all the same, such as 111111 |
| Include or exclude prefixes | Requires or rejects keywords immediately before the match |
| Include or exclude suffixes | Requires or rejects keywords immediately after the match |
Prefix and suffix checks look only at text immediately next to the match, whereas a supporting element only has to fall inside the proximity window. To stop a known test value matching, exclude it; raising the confidence level doesn't help, because the test value can still appear beside convincing evidence.
Chinese or Japanese mixed with single-byte text
Purview adds a space between each word in languages that use double-byte characters and removes special characters such as punctuation[9], so a keyword or regex that mixes Chinese or Japanese with English or other single-byte characters needs two variants. To detect 机密的document, add both 机密的document and 机密的 document. Keep keywords that contain double-byte characters in a separate dictionary or keyword list from English-only keywords, and use string match rather than word match in such a keyword list, as Microsoft recommends.
Pick the refinement by the error you see: a large or changing vocabulary goes in a dictionary, invalid identifiers fall to a validator, known noise falls to an additional check, and mixed-language terms need both spacing variants.
Creating a custom SIT in Security & Compliance PowerShell
The portal covers most custom SITs, but Security & Compliance PowerShell offers more configuration options[3] and is the route for a SIT the portal can't copy, such as one with 10 text processors (see Classifier types and what each compares content against). Microsoft's walkthrough customizes the built-in Credit Card Number rule[11], and the same approach applies to other built-in SITs. You can't modify the default rules directly, so the procedure always produces a new SIT:
- Export the rule package. Run
Get-DlpSensitiveInformationTypeRulePackage, store the result in a variable, and write itsSerializedClassificationRuleCollectionproperty to an XML file with[System.IO.File]::WriteAllBytes. - Extract the rule. In the exported file, find the rule under
<Rules>(the credit card rule referencesFunc_credit_card) and paste it into the rule package template shown below. - Give it new identities. Rule packages and rules are identified by unique GUIDs, so generate two: one for the
RulePack id, and one to replace the built-in rule'sEntity id. TheResource idRefunderLocalizedStringsmust equal the newEntity id, because that resource carries the rule's localized name and description. - Edit the pattern, for example by removing the corroborative evidence, changing
patternsProximity, or adding your ownKeywordlist. - Save with Unicode encoding. Save the file as XML with Unicode encoding; the rule won't work if the file is saved with a different encoding. The template's XML declaration is
encoding="utf-16". - Import and verify. Run
New-DlpSensitiveInformationTypeRulePackage -FileData ([System.IO.File]::ReadAllBytes('C:\custompath\MyNewRulePack.xml')), type Y to confirm, then runGet-DlpSensitiveInformationTypeto check the upload and the display name before you add the SIT to a policy.
Changing only the display name while keeping the exported Entity id doesn't produce a distinct SIT: the GUID, not the localized name, identifies the rule.
Skeleton of a custom rule package, abridged from Microsoft's template (quoted placeholder text marks values you supply; ... marks removed lines)
<?xml version="1.0" encoding="utf-16"?>
<RulePackage xmlns="https://schemas.microsoft.com/office/2011/mce">
<RulePack id="new GUID for the package">
...
</RulePack>
<Rules>
<Entity id="new GUID for the rule" patternsProximity="300" recommendedConfidence="85">
<Pattern confidenceLevel="85">
<IdMatch idRef="Func_credit_card" />
...
</Pattern>
</Entity>
<LocalizedStrings>
<Resource idRef="same GUID as the new Entity id">
...
</Resource>
</LocalizedStrings>
</Rules>
</RulePackage>
The figure below lists the six steps in order.
Identity and encoding are the two details this procedure insists on: two new GUIDs with a Resource idRef that matches the new Entity id, and a file saved with Unicode encoding.
Testing and safely changing custom SITs
A custom SIT that saves without errors can still misbehave in production. This section covers how to test it, why results differ between workloads, how existing content picks up a change, and what to check before you edit or delete a classifier.
Test with sample files
You can test a SIT by uploading a sample file[3]; the results show the number of matches for each confidence level, and testing works for built-in SITs, custom SITs, trainable classifiers, and exact data match. Test files that should match and files that shouldn't. The tenant needs at least one Exchange Online license, or the Test SIT option is greyed out. A test evaluates only the file you upload: a successful uploaded-file test doesn't establish that historical files have the same classification results[14].
Validate in every workload
The same SIT can produce different results depending on where content is evaluated[3]: email in transit in Exchange, files at rest in SharePoint and OneDrive, and files on managed devices in Endpoint DLP. Content-extraction limits such as maximum file size and the number of characters scanned also affect detection. Validate a custom SIT in each workload where you plan to use it (for example a mail flow rule, a SharePoint or OneDrive policy, and an endpoint policy) and tune it against the false positives and false negatives you find there.
Endpoint DLP evaluates every SIT in the tenant
Endpoint DLP classifies files based on all SITs available in the tenant, including custom SITs, regardless of their use in any DLP policy[3]. An untuned custom SIT that matches many files therefore causes excessive classification traffic even when no policy references it. Microsoft's remedy is to remove unused SITs and redesign SITs that match most of your organization's files; deleting a SIT's policy reference leaves the SIT, and its classification traffic, in place.
Existing files keep their earlier results
SharePoint and OneDrive content is classified by the search crawler, so a new custom SIT is identified in existing content only after that content is recrawled[9]; crawling runs on a schedule, and you can manually request a recrawl of a site collection, list, or library. In the same way, changing a custom SIT definition doesn't by itself reclassify unchanged historical files[14], and restarting an auto-labeling simulation only reevaluates policy matches without reclassifying the underlying content. On-demand classification, covered in On-demand classification, classifies such files again within the scan's scope.
Before you edit or delete a classifier
Check authority and dependencies first. The Information Protection Admin role can create, edit, and delete DLP policies, sensitivity labels and their policies, and all classifier types[15]; it is assigned through role groups such as Information Protection Admins and Compliance Administrator, so managing classifiers doesn't require Global Administrator. Compliance Administrator names both a Microsoft Entra role and the Microsoft Purview role group mapped to it[16]: here, for on-demand scans, and for OCR it means the role group, while page access to the explorers uses the Microsoft Entra role. Information Protection Analyst and Information Protection Investigator have view-only access to all classifier types. On the Classifiers page you can see how many policies use a classifier and inspect those dependencies[4] before changing it. The page's Classified items count shows how many items were found with that classification, which says nothing about which policies would lose their detector.
Test with files, validate in each workload, keep the tenant's SIT inventory lean for endpoints, refresh historical results deliberately, and confirm both the role and the dependent policies before you edit or delete.
Document fingerprinting
Many organizations move sensitive information on standard forms: a patent template, an employee information form for Human Resources, a government or HIPAA compliance form. Document fingerprinting[8] takes such a form and creates a fingerprint SIT that detects documents created from the same template.
How a fingerprint is built
Everyone who fills in a form starts from the same original words, so the form's word pattern identifies its copies. You upload the blank form, and Purview converts its word pattern into a document fingerprint: a small Unicode XML file containing a hash value that represents the original text. Only the hash is stored, and the original document can't be reconstructed from it. In the portal, choose Create Fingerprint based SIT on the Sensitive info types page, enter a name and description, upload the template, and optionally adjust the requirements for each confidence level. The template has rules of its own:
- Its extracted text must be between 256 and 204,800 characters.
- Text in embedded documents isn't used, so supply templates without embedded documents.
- Fingerprints are stored in a separate rule pack (a rule package of its own) with a 300 KB maximum size, which allows approximately 100 fingerprints per tenant.
- Creating a new fingerprint from a template that already has a fingerprint isn't supported.
Partial or exact matching
With partial matching[8] you give each confidence level (low, medium, high) the percentage of text, between 30% and 90%, that a file must share with the fingerprint. With exact matching you set the high confidence level to Exact: only files with exactly the same text as the fingerprint are detected, and even a small deviation means no match. Use partial thresholds when completed or altered forms must be caught, and Exact when only unchanged copies count. A list of file hashes can't do the partial job, because filling in a form changes the file. In PowerShell, New-DlpSensitiveInformationType creates a fingerprint SIT and Set-DlpSensitiveInformationType edits one, with the same settings as parameters:
Creating a fingerprint SIT with partial-match thresholds (Microsoft's example)
# Read the blank template as bytes
$Employee_Form = ([System.IO.File]::ReadAllBytes('C:\My Documents\Contoso Customer Form.docx'))
# -ThresholdConfig sets the low, medium, and high match percentages; -IsExact $false keeps partial matching
New-DlpSensitiveInformationType -Name "Contoso Customer Confidential" -FileData $Employee_Form -ThresholdConfig @{low=40;medium=60;high=80} -IsExact $false -Description "Message contains Contoso customer information."
Licensing, file eligibility, and locations
E5 is the licensing line for managing fingerprints: Microsoft recommends that E5 customers update existing fingerprints to the full feature set, and E3 customers who don't upgrade can't modify existing fingerprints or create new ones after April 2023[8]. Existing fingerprints and the policies that use them should continue to work. To move an existing fingerprint to the newer features, edit its SIT and upload the same fingerprint file again[8]: that re-uploads the template into the existing fingerprint SIT, unlike creating a new fingerprint from a template that already has one, the unsupported case under How a fingerprint is built.
Fingerprint SITs work in DLP policies scoped to Exchange, SharePoint, OneDrive, Teams, and devices, and in auto-labeling for Exchange, SharePoint, and OneDrive[8]; devices also need Advanced classification scanning and protection turned on. Fingerprinting doesn't detect sensitive information in password-protected files, files that contain only images, documents that don't contain all the text from the original form, or files larger than 4 MB. The missing-text limitation is quoted as Microsoft's limitations list states it, while the same page documents partial matching from 30%; test altered forms against your thresholds rather than assume either reading. A fingerprint SIT can also be used in Exchange mail flow rules, but mail transport never sees a file copied to a USB drive; protecting that path needs a DLP policy scoped to devices.
The figure below shows the path from blank form to policy.
Fingerprint the blank form, set thresholds for filled-in copies, and confirm the license, the file's eligibility, and the target location before relying on the policy.
Exact data match: detecting your own records
A national ID SIT matches numbers that meet its pattern requirements. When only your own records count, such as the IDs of current customers, exact data match (EDM) based classification[17] creates a custom SIT that refers to exact values in a database of sensitive information. All EDM SITs are created from scratch[3]. The database can contain up to 100 million rows of data and can be refreshed daily, so the SIT stays current as employees, patients, and clients come and go, and matching compares one-way cryptographic hashes rather than clear-text values.
The three parts of an EDM SIT
- Sensitive information source table: your data. Column headers are the field names, and each row is one record.
- Schema: an XML file that names the DataStore and the fields, with a one-to-one mapping between schema field names and source table column names. It also marks which fields are searchable, which corroborative evidence fields require multi-token match mode, and which fields support configurable matches, such as ignoring delimiters and case. Field meaning comes from the schema, so a column-mapping error is fixed in the schema, never by renaming the SIT.
- Rule package: the primary element (the data field used in exact lookup), the classification (the SIT match that triggers an EDM lookup), supporting elements, confidence levels, and proximity.
The primary field: discover first, then look up
EDM doesn't scan content for table values directly. Primary elements must be discoverable through an existing SIT[17]: for a U.S. social security number field you associate the U.S. Social Security Number (SSN) SIT. When that SIT finds a candidate, EDM compares its hash with the source table, then looks for the record's supporting fields within proximity, individually and in combination, and the supporting evidence found sets the confidence level as it does for any SIT. Multi-token matching lets supporting fields such as full names or street addresses match when associating them with a SIT isn't easy. The primary field's SIT matters: the new experience (one of the two portal ways to create EDM SITs, compared in New experience or classic experience below) warns when a primary field is mapped to a loosely defined SIT[18], which causes lookups on large numbers of unrelated strings, and when the primary field's values repeat across many rows, which can cause timeouts; both can result in missed detections and poor performance. Prefer a strongly defined SIT such as U.S. Social Security Number and a field with distinctive values, not a common surname.
New experience or classic experience
You can create EDM SITs in the new experience, the classic experience, or PowerShell. The new experience creates the schema and SIT together[18], one schema per SIT. It can infer the schema from a sample file with the same headers and 10 to 20 rows of representative data, which must not be sensitive because the sample isn't hashed. It generates high and medium confidence rules for each primary field and reports status from Data not yet uploaded to Indexing complete. A tenant can have at most 10 EDM schemas. Choose the classic experience when several EDM SITs must share one schema, when you need more than 10 EDM SITs, or when you need a custom schema name (the new experience names the schema after the SIT, for example PatientNumberschema). Schemas created in the classic experience or uploaded as XML with PowerShell aren't viewable or manageable in the new experience.
Where EDM SITs work
| Service | Locations |
|---|---|
| Microsoft Purview Data Loss Prevention | SharePoint, OneDrive, Teams chat, Exchange Online, devices |
| Microsoft Defender for Cloud Apps | SharePoint, OneDrive |
| Auto-labeling (service side) | SharePoint, OneDrive, Exchange Online |
| Auto-labeling (client side) | Word, Excel, PowerPoint, Exchange desktop clients |
The same services table[17] also lists Customer Managed Key, eDiscovery, and Insider Risk Management locations.
The figure below traces how an EDM SIT evaluates content.
EDM narrows detection to your own records, but only after the primary field's SIT finds a candidate; the schema and the authoring experience then decide how many EDM SITs you can build on one table.
Hashing and uploading EDM source data
Creating an EDM SIT is a multiphase process[18], and a SIT that exists isn't yet a working detector: the new experience reports status values such as Data not yet uploaded, Data upload complete, Indexing complete, Data upload failed, and Data indexing failed. Check that status before testing the SIT or relying on a policy that depends on it. This section covers the upload phase, done with the EDM Upload Agent[19].
Who may upload
The upload account is a Microsoft 365 work or school account that belongs to the EDM_DataUploaders security group; a Groups Administrator (the best least-privilege option) or a User Administrator creates the group and adds members. On the upload computer you authorize the agent from its installation folder with the /Authorize command and sign in with that account. Upload rights come from this group membership; publishing a sensitivity label to someone grants nothing here.
Validate before you hash
Download the schema with EdmUploadAgent.exe /SaveSchema, then validate the data file against it with EdmUploadAgent.exe /ValidateData /DataFile [data file] /Schema [schema file]. The agent expects CSV by default and also accepts tab- or pipe-separated data when you indicate the separator. The common failure is a mismatched number of columns, caused by commas or quote characters inside values; fix the export instead (surround such values with double quotes, or use the tab-delimited format, which Microsoft recommends as less susceptible to these issues), because a detection setting such as a confidence level can't correct a parsing error.
Two computers or one
The agent hashes the table with a salt value, added automatically unless you provide your own with /Salt, and uploads only the hashes; custom hashing isn't supported. Microsoft's best practice is the two-computer method, which keeps the clear-text table off any computer with a direct connection to the internet:
- On a computer in a secure environment, validate the data file and run
/CreateHash, which outputs anEdmHashfile and anEdmSaltfile. - Securely copy both files to a computer that can connect directly to your Microsoft 365 tenant. Both computers must run the same version of the EDM Upload Agent.
- On that computer, authorize the agent and run
/UploadHash. - Confirm with
/GetDataStore(the data stores and when each was last updated) and/GetSession(the uploads to one store).
The single-computer method runs /UploadData, which hashes and uploads in one step, so the clear-text source table must reside on the computer connected to the tenant. The new experience's schema sample file is a separate upload that isn't hashed, which is why it must hold nonsensitive values. A spreadsheet protected with a document password is no substitute for any of this, because only the agent's two documented methods can be used to hash and upload the data.
The figure below shows the two-computer method.
The reference data must be uploaded and indexed before an EDM SIT can match it.
Trainable classifiers
Some content has no pattern to match: a legal agreement, a press release, a price quote. A trainable classifier[20] learns how to identify a type of content by looking at examples, which suits content that can't easily be identified with manual or automated pattern-matching methods. There are two kinds: pretrained classifiers, created by Microsoft and shown with the status Ready to use, and custom trainable classifiers, which you train when the pretrained ones don't cover your content. Document fingerprinting is no alternative for agreements written independently of each other, because without a shared template there is no word pattern to fingerprint.
Check the consumers and limits before training
Classifiers can be conditions for auto-labeling with sensitivity labels, auto-applying retention labels, DLP, and communication compliance, among other uses (insider risk management also considers trainable classifiers in images, as Turning on OCR for existing classifiers notes), but communication compliance supports Microsoft-provided trainable classifiers only[20], so a custom classifier can't meet a communication compliance requirement. Support for custom classifiers is limited to English, and classifiers only work with items that aren't encrypted.
Seed content
Seeding means a person selects two sets of samples[21]: at least 50 and up to 500 positive samples that strongly represent the category, and at least 150 and up to 1,500 negative samples that clearly don't belong. Positive samples alone aren't enough, because the negative set is what shows the classifier where the category ends. The seed rules:
- Only text-based files are supported; image files and image-only PDFs can't be used.
- Put the positive and negative samples in separate SharePoint folders, each holding only seed content, on a communication site or another SharePoint site type, but not in a Teams folder type or a OneDrive folder.
- Allow at least an hour for a newly created seed site and folder to be indexed before creating the classifier.
- The account you use must have access to both seed folders.
- The classifier processes up to the 2,000 most recently created samples, by file creation timestamp, so keep the folders controlled: newer stray files can displace the samples you chose.
Train, review, publish
Microsoft's procedure[21] says to sign in "with either Compliance admin or Security admin role access"; Compliance Administrator and Security Administrator each exist as a Microsoft Entra role and as the Purview role group mapped to it[16] (see Before you edit or delete a classifier). Then select Create trainable classifier and point it at the positive and negative folders. Within 24 hours or less[21] it builds a prediction model, and its status moves from In progress to Training is complete and items have been tested. Review its predictions, sorting out true positives, true negatives, false positives, and false negatives; if they aren't accurate enough, add data and retrain before publishing, then choose Publish for use. By default only the user who created a custom classifier can train it and review its predictions.
Improving a classifier
An unpublished classifier is improved by reviewing the test results, adding data, and restarting the training. Retraining a published custom classifier isn't supported[20]: remove the classifier and start over with larger sample sets. Changing a policy's settings never retrains a classifier, because policy conditions don't rebuild the learned model.
Display in Content explorer (preview)
In preview, trainable classifiers in Content explorer automatically display the number of incidents found in SharePoint and Teams[20] without requiring any labeling. Despite the word incidents, this is a Content explorer display of what the classifiers found: a request to Microsoft Support disables the display of your sensitive data that isn't used in any labeling policies[20] within Content explorer. Scanning can also be disabled by request, but then sensitivity labeling and DLP policies that use those classifiers don't work, so review dependent policies before asking.
The figure below shows the custom classifier lifecycle, including the retraining loop that ends at publication.
Check the consumer first, seed balanced and controlled folders, review predictions before publishing, and remember that publishing ends retraining.
Data explorer and Content explorer
Once classifiers and labels are in use, the explorers answer one question: where is classified content right now? Data explorer[22] sits under Information Protection > Explorers, and Microsoft's Classifiers documentation[4] directs you to it to review items with classification matches and see where those items are located. Content explorer[7] sits under Data Lifecycle Management > Explorers, and Microsoft Learn titles its page Get started with Content Explorer (classic), marking it as the classic experience. Both show a current snapshot of the items that have a sensitivity label or a retention label or have been classified as a SIT, and both can show trainable classifier results too. Each lets you natively view the items summarized on the overview page[7], and the access and timing rules that follow hold for both unless a sentence names one.
Finding items
Type a label, classifier, or SIT name into the filter box or browse for it, select a data source or location, and drill down to the item. After you drill into a location, a Filter tool appears: for Exchange or Teams you search on the mailbox's full email address, and for SharePoint or OneDrive on site names, folders, and files (a full site name, a file name, the start of a file name, text after an underscore, or a file extension). Export creates a CSV file listing whatever the pane is focused on, which is not the same as a tenant-wide report. Content explorer can also save customized views.
Three layers of access
Access is split on purpose, because the explorers let you read the contents of scanned files and their permissions supersede permissions assigned locally to items:
| What the user can do | What grants it |
|---|---|
| Open the explorer page | The Microsoft Entra Compliance Administrator, Security Administrator, or Compliance Data Administrator role (Data explorer also lists Global Administrator); Information Protection roles and role groups also apply |
| List items and their locations | Data Explorer List viewer or Content Explorer List viewer role group (the data classification list viewer role) |
| View item contents, and item names in list view | Data Explorer Content viewer or Content Explorer Content viewer role group (the data classification content viewer role) |
Membership in the page-access roles doesn't allow you to view the list of items or the contents of the items[22], so the Microsoft Entra Compliance Administrator role alone doesn't let an investigator preview a document. The list viewer and content viewer role groups are independent and not cumulative; a user who must list locations and read files needs both. Both explorers support administrative units for scoping these roles, and Role management role holders assign the role group memberships.
Timing and encrypted items
Counts can take up to seven days to update, and 14 days for files in SharePoint[7], so a count taken right after a change isn't a completeness check. Document preview and download are disabled for encrypted documents, a product restriction that extra explorer permissions don't lift. Sensitivity labels must be enabled for files in SharePoint and OneDrive[23] for that data to surface (see Implement and manage sensitivity labels in Microsoft Purview), and encrypted sensitivity labels aren't surfaced on content explorer for SharePoint and OneDrive[22].
A snapshot, not a history
The explorers don't record who did what, or when. Activity explorer[24] provides a historical view of activities on labeled content, built from the Microsoft 365 unified audit logs, reports on up to 30 days of data, and includes a filter set for sensitivity labels applied, changed, or removed. A label publishing policy isn't an inventory either: its scope determines which users can see and apply the label[6], not which content carries it.
Use the explorers for what is classified where, grant list and content access separately, allow for update delays, and go to activity explorer for history.
Match and Not a Match feedback
Classifiers produce false positives and false negatives, and the feedback experience is how you confirm which matches are right before you change anything. In Data explorer, Content explorer, and the matched items pages for a SIT or trainable classifier, you can confirm whether a matched item is a true positive (Match) or a false positive (Not a match)[25] for SharePoint and OneDrive items, using the Contextual Summary tab where the classifier supports it; the DLP alerts page extends this to Exchange email. If you choose the wrong option, select Withdraw feedback.
Not every classifier supports this feedback:
| Classifier | Match and Not a Match |
|---|---|
| Built-in SIT | Yes |
| Custom SIT | Yes |
| Fingerprint SIT | Yes |
| EDM SIT | No |
| Named entity SIT | No |
| Credential SIT | No |
| Pretrained trainable classifier | Yes |
| Custom trainable classifier | Yes |
Two limits apply: the experience is only available for items created or updated after it was enabled for the tenant, and DLP policies that use the SITs or trainable classifiers must already be deployed and have matched items.
Feedback records a verdict; it doesn't edit the classifier. You act on it by tuning, and Microsoft lists options such as increasing the thresholds of SITs found, pairing a low confidence level with a high instance count (or a higher confidence level with a low count), cloning built-in SITs to add conditions, excluding known prefixes, suffixes, or patterns (for example your organization's own phone numbers in email signatures), adding dictionary-based SITs as conditions, and, for named entity SITs like All Full Names, setting a higher instance count threshold such as 10 or 50. A custom trainable classifier that keeps failing is rebuilt rather than retrained once published, as Trainable classifiers explains. Raising a policy's instance count before reviewing disputed items changes how many detections trigger the policy, not whether those detections are correct.
Review the disputed matches first, then tune the SIT or rebuild the classifier; the verdicts themselves change no rule.
On-demand classification
Existing files keep the classification results they already have, as Testing and safely changing custom SITs explains. On-demand classification[26] identifies and classifies sensitive content in historical data stored in SharePoint, OneDrive, and endpoints: files that were never classified, files not classified or modified for a long time, and files that need updated classification.
What a scan changes
On-demand classification updates classification results, and matching policies determine any resulting actions. For SharePoint and OneDrive, updated results can trigger active policies, including policies that apply or remove sensitivity labels, so an auto-labeling policy you're testing can stay in simulation while other active policies act on the same files. On-demand classification isn't an auto-labeling simulation. For SharePoint and OneDrive, each scanned file is evaluated against Data Loss Prevention, Information Protection, Data Lifecycle Management, and Insider Risk Management policies.
Running a scan
- Review active policies that could act on the refreshed results.
- Create the scan. Go to Information Protection > Classifiers > On-demand classification (also available under Data loss prevention), select New scan, and define the name and description, the scope and locations, the classifiers to scan for, the file last-modified date range, and the file extensions. By default a scan includes all items created or modified within the past year, all supported file extensions, and every classifier configured in the tenant; you can choose up to 50 specific classifiers at a time.
- View the estimation to review items found and estimated cost, and use Edit scan to narrow or expand the scope.
- Start classification. Classification can start up to 30 days after estimation, though a shorter gap gives more accurate final counts and costs.
Permissions, cost, and limits
Running a scan requires membership in the Compliance Administrator role group; viewing classification results requires Content Explorer Content Viewer or Content Explorer List Viewer. The feature uses pay-as-you-go billing, per-user licensing, or both. Scan cost follows the total number of files scanned, not the number of classifiers, and EDM classifiers cause previously classified files to be rescanned, which raises cost unless you exclude the EDM classifier from the scope. If you select specific classifiers, only those classifiers have their results updated. For SharePoint and OneDrive a scan can process up to 150,000 locations and 100 million files, and Content explorer updates within seven days of scanning.
The figure below shows the scan sequence.
Review active policies, scope the dates and classifiers to the files you actually mean, check the estimate, and only then start classification.
Turning on OCR for existing classifiers
A screenshot of a spreadsheet or a scanned ID card holds text that a text-based classifier can't read. Optical character recognition (OCR)[27] lets Purview scan images for sensitive information; it is an optional feature that you enable at the tenant level and then point at locations.
Billing comes first
- Azure pay-as-you-go subscription. The Global admin verifies that one exists for the tenant, or creates it.
- Estimate OCR charges with the OCR cost estimator.
- Microsoft Syntex billing. A Global or SharePoint admin follows Set up Microsoft Syntex billing in Azure to add a subscription for OCR. You don't need to set up Microsoft Syntex itself.
- Configure OCR. In the Microsoft Purview portal, select Settings > Optical character recognition (OCR), select the locations where you want to scan images, select the groups to include in or exclude from OCR scans, and select Done. OCR settings generally take effect about an hour after you turn them on.
Configuring OCR[27] requires membership in one of these role groups: Compliance Administrator, Compliance Data Administrator, Global Administrator, Information Protection, or Information Protection Admins. Microsoft's roles reference[15] lists Information Protection Admin, singular, as a role held by role groups including that last entry, Information Protection Admins; Before you edit or delete a classifier explains the distinction.
No new classifiers
You don't create separate classifiers for images. Once OCR is configured, existing SITs, EDM SITs, trainable classifiers, and fingerprint SITs scan images as well as documents and emails[27], so a second credit card SIT for screenshots is unnecessary. Only images uploaded after OCR is enabled are scanned, so turning it on gives no retroactive coverage of images already stored.
Locations and the solutions that act on image text
| Location | Supported solutions |
|---|---|
| Exchange | Data loss prevention, auto-labeling policies, auto-apply retention label policies |
| SharePoint sites | Data loss prevention, insider risk management, auto-apply retention label policies |
| OneDrive accounts | Data loss prevention, auto-apply retention label policies |
| Teams chat and channel messages | Data loss prevention, insider risk management |
| Devices | Data loss prevention, insider risk management |
In this locations table[27], auto-apply retention label policies support keywords and SITs, and insider risk management considers SITs and trainable classifiers present in images for risk scoring.
The figure below shows the four enablement steps and their result.
Set up billing, choose locations and groups, and your existing classifiers can then evaluate the text in eligible new images within that scope after the settings take effect.
OCR coverage by location
What OCR scans differs by location, so check the location's limits before you design a policy around image text. The limits below come from the OCR documentation[27].
Size, resolution, and format
| Requirement | Limit |
|---|---|
| File size, Exchange and Teams | 20 MB maximum |
| File size, SharePoint, OneDrive, and Windows and macOS endpoints | 50 MB maximum |
| Image resolution | 50 × 50 pixels minimum, 16,000 × 16,000 pixels maximum |
| Text extracted | The first 2 million characters |
For formats, Exchange scans JPEG, JPG, PNG, BMP, TIFF, and scanned PDFs[27], plus embedded images in DOCX, PPTX, XLSX, RAR, TAR, ZIP, 7z, and hybrid PDFs, with a limit of 20 embedded images scanned per file. Teams and Windows and macOS endpoints scan JPEG, JPG, PNG, BMP, TIFF, and image-only PDFs. SharePoint and OneDrive support a much longer list that includes camera raw formats, HEIC and HEIF, scanned and hybrid PDFs, and embedded images in DOCX, PPTX, and XLSX.
Exchange: direction scope and policy tips
By default, OCR scans incoming email (from outside the organization), internal email, and outgoing email (sent outside the organization)[27]. To exclude incoming mail, change the OCR scope from All sender groups to Specific sender groups and specify the internal groups to scan. To scan only mail sent outside the organization, select the option under Advanced Setting (Only Exchange); then neither incoming mail nor internal communications are scanned. DLP policy tips aren't supported for images in Exchange. OCR scope is set in these OCR settings (locations, groups, and the Exchange option), not by a sensitivity label's publishing audience.
Windows and macOS endpoints
When OCR is on for devices, the devices send images to the cloud for scanning[27], subject to a default bandwidth limit of 1,024 MB of data per device per day. OCR stops scanning images once a device reaches that daily limit, so if coverage must continue you increase the bandwidth limit; adding SITs to a policy doesn't change it. If you exclude a path in the Endpoint DLP settings, OCR doesn't scan images in that folder either, and network settings must not obstruct OCR: a wildcard allowing blob.core.windows.net endpoints should be present.
Besides arriving before OCR was enabled, an image can fall outside OCR coverage through its size or format, the Exchange direction scope, or a device's bandwidth limit and excluded paths.
How OCR is charged
OCR bills by images scanned, not by the policies that use the results. Each image scanned counts as one transaction[27]: a standalone JPEG, JPG, PNG, BMP, or TIFF image is one transaction, and each page of a PDF file is charged separately, so a 10-page PDF counts as 10 separate scans. Each scanned image can be used in any number of policies across data loss prevention, insider risk management, auto-labeling, and records management at no extra charge.
Caching reduces repeat charges:
| Location | Caching |
|---|---|
| Exchange | Small images such as logos and signatures are scanned and billed only once per unique image across all users of the tenant, for a moving window of five days |
| Endpoints | A cache local to each device, kept for 30 days, storing only the classifiers identified on the image and the image hash |
| SharePoint and OneDrive | No caching for standalone images; in embedded file types, images aren't scanned again if only text is updated |
Before reusing a cached result, the service checks parameters such as the image stream hash and image size, and it scans the image again if any parameter doesn't match.
Budget per image and per PDF page; the number of policies that consume the results doesn't add cost.
Telling look-alike answers apart
Several classifiers and settings can look interchangeable for one requirement, so the table below separates each such pair by the mechanism that tells them apart. Each row below restates a rule taught earlier in this topic, with the section that explains it.
| Requirement in the scenario | Fits | Tempting wrong answer, and why it fails |
|---|---|---|
| Only current customers' account numbers | EDM SIT[17] (Exact data match: detecting your own records) | A built-in ID SIT alone: a valid format doesn't prove membership in your table |
| Filled-in copies of the HR onboarding form | Fingerprint SIT[8] (Document fingerprinting) | EDM against an employee list: it matches supplied values, not the form's wording |
| Independently written contracts | Trainable classifier[20] (Trainable classifiers) | Document fingerprinting: there is no shared template to fingerprint |
| A fixed-format internal document ID | Custom SIT with a regular expression[9] (Anatomy of a custom SIT pattern) | A trainable classifier: a deterministic format needs no learned model |
| Names of people never seen before | Named entity SIT[10] (Classifier types and what each compares content against) | A keyword dictionary of known customers: it matches only the listed terms |
| Ignore a known test card number | Exclude specific matches[13] (Refining what a SIT pattern matches) | A higher confidence level: the test value can still appear with strong evidence |
| Corroborating evidence sits outside the window | Larger proximity value[3] (Anatomy of a custom SIT pattern) | A higher confidence level: it never widens the window |
| Improve a published custom classifier | Remove and recreate it[20] (Trainable classifiers) | Retraining it: unsupported after publication |
| Who removed a label last week | Activity explorer[24] (Data explorer and Content explorer) | Data explorer: it shows a current snapshot, not history |
| An investigator must preview documents | Content viewer role group[22] (Data explorer and Content explorer) | The Microsoft Entra Compliance Administrator role alone: it opens the page but lists no items |
| Screenshots that contain card numbers | Enable OCR[27] (Turning on OCR for existing classifiers) | A second SIT for images: OCR feeds existing classifiers |
| Device OCR stops after heavy use | Raise the device bandwidth limit[27] (OCR coverage by location) | Adding SITs: the daily bandwidth limit is unchanged |
When two answers both sound right, ask what each one compares content against, or which permission or setting it actually changes; the right answer is the one whose mechanism matches the requirement.
Pattern-based SIT vs fingerprint SIT vs EDM SIT vs trainable classifier
| Criterion | Pattern-based SIT | Fingerprint SIT | EDM SIT | Trainable classifier |
|---|---|---|---|---|
| Compares content against | A pattern: regular expression, keyword list, keyword dictionary, or function, plus corroborating evidence | The word pattern of a blank form or template you upload | Hashed values from your own sensitive information source table | What it learned from example items |
| Fits a requirement like | Credit card or national ID numbers, person names, addresses, credentials, or your own ID format | Filled-in copies of a patent template or an HR form | Only the IDs of your current customers, patients, or employees | Contracts, strategic plans, or other categories with no fixed format |
| What you supply | Nothing for a built-in SIT; patterns and evidence for a custom SIT | A template with 256 to 204,800 characters of extracted text | An EDM schema and a source table of up to 100 million rows, hashed by the EDM Upload Agent | Nothing for a pretrained classifier; positive and negative samples in SharePoint for a custom one |
| How you change it | Built-in SITs can't be edited but most can be copied; named entity SITs can be neither edited nor copied | Edit the SIT and upload the template again | Refresh the source table, as often as daily | Retrain while unpublished; once published, remove it and create a new one |
| Match and Not a Match feedback | Supported for built-in and custom SITs; not for named entity or credential SITs | Supported | Not supported | Supported for pretrained and custom classifiers |
Decision tree
Sharp facts the exam loves — give these one last read before exam day.
Cheat sheet
Sharp facts the exam loves — scan these before test day.
- A classification taxonomy must express business sensitivity in terms users understand
A sensitivity taxonomy translates business and regulatory requirements into recognizable categories and handling expectations. Define label names and descriptions with business stakeholders, include concrete examples in tooltips, and test the terminology with the people who will classify content. Configure the protection required for each category after establishing what belongs in it.
Trap Using department names as the entire sensitivity hierarchy when the same department handles both public and restricted information, because ownership alone does not identify handling requirements.
4 questions test this
- You have a Microsoft 365 E5 subscription. You are defining sensitivity labels for 5,000 users. Draft names from the security team include CL-3-RESTRICT and DPA-ART9. Pilot users often pick the wrong l
- You have a Microsoft 365 E5 subscription. The compliance team finalized label names and tooltips in a workshop with legal and IT stakeholders. You plan to publish the labels to the whole organization
- You have a Microsoft 365 E5 subscription. A project team wants to create sensitivity labels with encryption and watermarks right away. No classification categories have been agreed with business owner
- You have a Microsoft 365 E5 subscription. Users can't tell whether a project budget belongs under General or Confidential. You plan to update each label so users see guidance when hovering over it in
- Recognizing sensitive information and enforcing its handling are separate configuration decisions
Microsoft Purview classifiers identify sensitive content, while sensitivity labels and policies determine how that content is classified and protected. A sensitivity label can deliberately identify a category without adding encryption or markings, allowing an organization to measure usage before introducing protection. Choose the detection requirement and the required handling action separately rather than treating a match as an automatic grant or restriction of access.
Trap Using a custom sensitive information type as the access-control policy, because a detector supplies classification evidence rather than a set of authorized readers.
5 questions test this
- You have a Microsoft 365 E5 subscription. Leadership wants to know how much content is sensitive and where it's used before deciding on any restrictions. Users must be able to label documents now with
- You have a Microsoft 365 E5 subscription. Compliance requires two outcomes for documents that contain U.S. Social Security numbers. The content must be identified, and each document must display a CON
- You have a Microsoft 365 E5 subscription. You created a custom sensitive information type named HRSIT that detects employee review files. A manager expects that once HRSIT matches a file, only HR memb
- You have a Microsoft 365 E5 subscription. A custom sensitive information type named PayrollSIT detects payroll files. Only members of the Payroll group must be able to open matching files, wherever th
- You have a Microsoft 365 E5 subscription. A custom sensitive information type named SIT1 detects merger documents in SharePoint, and Content explorer shows thousands of matches. None of the matching f
- Classifier changes require management permission and review of dependent policies
Before editing or deleting a classifier, use an account with classifier-management permission and inspect the policies that depend on it. The Information Protection Admin role, available through Information Protection Admins, permits classifier creation, editing, and deletion without requiring Global Administrator; Information Protection Analyst and Investigator provide view-only classifier access rather than classifier-management authority. On the Classifiers page, inspect the policy-usage count and dependencies so you can assess the effect on consuming policies before changing their detector. The Classified items count measures detected items, not how many policies depend on the classifier.
Trap Using the Classified items count as the safety check before deleting a detector, because content prevalence does not reveal which configured policies still reference it.
3 questions test this
- You have a Microsoft 365 E5 subscription. User1 investigates DLP incidents. User1 must manage DLP alerts, use Activity explorer and Content explorer, and open file contents. User1 must have view-only
- You have a Microsoft 365 E5 subscription. User1 must create, edit and delete trainable classifiers and sensitive information types. User1 must not manage eDiscovery or insider risk. The solution must
- You have a Microsoft 365 E5 subscription. You plan to delete a custom sensitive information type named ProjCodes. Data explorer shows 12,000 classified items for ProjCodes. Before deleting it, you mus
- A supported built-in sensitive information type can be copied when its detection needs customization
When a Microsoft-provided pattern already meets the requirement, use its built-in sensitive information type to avoid maintaining a separate detector. For organization-specific changes, copy a supported built-in type and edit the custom copy, or define a custom type from scratch. Built-in definitions themselves are not editable, and the portal documents exceptions that cannot be copied, including several bundled identification types. Named-entity SITs cannot be edited or copied. For an otherwise copyable SIT with 10 text processors or restricted text processors, use PowerShell because the portal cannot copy it directly.
Trap Using a named-entity SIT as an editable template, because its definition supports neither copying nor editing.
6 questions test this
- You have a Microsoft 365 E5 subscription. You copied the built-in Credit Card Number type, named the copy Contoso CC, and added keywords to it. An existing DLP policy that references Credit Card Numbe
- You have a Microsoft 365 E5 subscription. Coders need detection of International classification of diseases (ICD-10-CM) codes that also requires the keyword Claim nearby. The ICD-10-CM overview page i
- You have a Microsoft 365 E5 subscription. You need to create customized detection based on the following built-in sensitive information types: - Canada driver's license number - U.S. / U.K. passport n
- You have a Microsoft 365 E5 subscription. A DLP policy must detect any U.S. Social Security number in email, not only employee numbers. A consultant proposes building a custom regex type. The Microsof
- You have a Microsoft 365 E5 subscription. You want to narrow the All physical addresses type by adding exclusions for your office addresses. In the Microsoft Purview portal, neither a Copy option nor
- You have a Microsoft 365 E5 subscription. You plan to customize a built-in sensitive information type named SIT1 that has 10 text processors, including keyword lists, regular expressions and functions
- Bundled and unbundled named entities offer different detection breadth
Choose a bundled named-entity SIT such as All physical addresses for broad recognition, or an unbundled entity for a particular country, region, or class of terms. Named-entity sensitive information types recognize person names, physical addresses, and medical terms and conditions. Verify E5 licensing before choosing advanced named-entity detection. For a bundled SIT in Endpoint DLP, also verify that Advanced classification scanning and protection is enabled.
Trap Using a keyword dictionary of known customers for an open-ended requirement to identify previously unseen personal names, because a vocabulary list only matches its supplied terms.
4 questions test this
- You have a Microsoft 365 E5 subscription. A DLP policy must detect customer full names in emails sent to external recipients. New customers are added daily, and many names that must be detected will n
- You have a Microsoft 365 E5 subscription. A health insurer needs a DLP policy for Exchange that detects any medical condition, test or medication term in outgoing email. The compliance team wants the
- You have a Microsoft 365 E5 subscription. A DLP policy for an Australian subsidiary must detect physical addresses in Australia, including addresses that aren't already known. Matches on addresses fro
- You have a Microsoft 365 E5 subscription. A pharmacy chain needs an auto-labeling policy that labels documents mentioning brand-name medicines such as Tylenol. Documents that mention only blood tests
- All credentials detects the credential family while individual members narrow the requirement
Select the All credentials sensitive information type when the requirement is to detect the full set of credential-scanning types available in the portal. Each member can also be used as a standalone SIT when only a particular credential type belongs in the detection scope. Credential-scanning SITs require an E5 license, so verify that entitlement before choosing this built-in detector family.
Trap Using All credentials for a rule limited to one credential type, because the bundle includes the other credential detectors and broadens the matching population.
5 questions test this
- You have a Microsoft 365 E5 subscription. A DLP rule named Rule1 must block Teams messages that contain GitHub personal access tokens only. Rule1 currently uses All credentials and also blocks message
- You have a Microsoft 365 E5 subscription. A DLP rule for a database team's SharePoint site must detect Azure SQL connection strings only. Other credential types in that site are expected and must not
- You have a Microsoft 365 E5 subscription. You create a DLP policy named DLP1 for SharePoint sites used by the DevOps team. DLP1 must detect Azure DevOps personal access tokens, Azure SQL connection st
- You have a Microsoft 365 E3 subscription. You plan a DLP policy for SharePoint sites that uses the All credentials sensitive information type. Before you design the policy rules, you need to confirm t
- You have a Microsoft 365 E5 subscription. Rule1 must block Exchange email that contains GitHub personal access tokens. Rule2 must audit email that contains any other credential type that the portal ca
- A custom sensitive information pattern combines a primary match with corroborating evidence
A custom sensitive information type contains one or more patterns, each defining a primary element, confidence level, character proximity, and any supporting elements. Use a regular expression for a structured identifier, a keyword list or dictionary for known terms, or an available function for supported detection logic. Supporting elements provide contextual corroboration, and multiple patterns let the same information type recognize different evidence combinations.
Trap Using a trainable classifier to implement an exact timestamp-shaped document ID, because learning a document category is unnecessary for a deterministic format requirement.
5 questions test this
- You have a Microsoft 365 E5 subscription. Order IDs at your company combine an eight-digit date stamp, a hyphen and a six-digit sequence, such as 20261108-004512. A DLP policy named DLP1 must detect t
- You have a Microsoft 365 E5 subscription. You are creating a custom sensitive information type named SIT1 whose primary element is a regex for member IDs. Matches must be corroborated by a nearby date
- You have a Microsoft 365 E5 subscription. You are defining a pattern in a custom sensitive information type. The primary element must match any of 12 fixed project names, such as Falcon and Osprey, wh
- You have a Microsoft 365 E5 subscription. You define a custom sensitive information type named SIT1 for contract numbers. Matches that have the keyword Contract nearby must be reported at high confide
- You have a Microsoft 365 E5 subscription. A custom sensitive information type named SIT1 detects nine-digit policy numbers by using a regular expression. SIT1 matches many unrelated nine-digit values.
- Sensitive information confidence thresholds trade false positives against false negatives
Sensitive information types use low, medium, and high confidence values of 65, 75, and 85. Selecting low includes low, medium, and high matches; medium includes medium and high; high selects only high-confidence matches. Higher-confidence patterns generally require stronger corroboration and reduce false positives at the cost of potentially missing sensitive content, so choose confidence and occurrence thresholds together for the intended protection.
Trap Increasing a rule's occurrence threshold to repair an overbroad primary pattern, because the threshold changes how many detections are needed rather than improving each detection's evidence.
4 questions test this
- You have a Microsoft 365 E5 subscription. A legacy custom sensitive information type named SIT1 was created with a pattern confidence value of 70. You review SIT1 in the Microsoft Purview portal, whic
- You have a Microsoft 365 E5 subscription. A DLP rule named Rule1 is configured with medium confidence for a custom sensitive information type named SIT1. A file contains a SIT1 match that SIT1 rates a
- You have a Microsoft 365 E5 subscription. For a legal hold review, the compliance team wants a DLP rule named Rule1 to return every possible match of a custom type, accepting many false positives. SIT
- You have a Microsoft 365 E5 subscription. You define a custom sensitive information type in rule package XML. The Entity element sets recommendedConfidence, and one Pattern element sets confidenceLeve
- Character proximity determines which supporting evidence belongs to a primary match
Character proximity defines how close supporting evidence must be to the primary element of a sensitive information pattern. The complete supporting value must fit within the configured proximity window; a window that reaches only the beginning of the value is insufficient. Set a narrow window for tightly formatted records and a wider one when legitimate context is farther away, validating that unrelated records do not supply accidental corroboration.
Trap Selecting a higher pattern confidence level to connect a distant customer name with an identifier, because confidence selection does not extend the character window.
6 questions test this
- You have a Microsoft 365 E5 subscription. A custom sensitive information type named SIT1 has a regex primary element and two supporting elements. The keyword Invoice must be within 50 characters of th
- You have a Microsoft 365 E5 subscription. You customize a copy of the Credit Card Number entity in rule package XML. Its keywords must count as corroborative evidence when they appear up to 600 charac
- You have a Microsoft 365 E5 subscription. A custom type named SIT1 requires Name or DateOfBirth within 250 characters of each SSN value. In a file, a Name value and a DateOfBirth value sit next to eac
- You have a Microsoft 365 E5 subscription. You widened the proximity of SIT1 from 300 to 2,000 characters so that contract numbers match customer names in a letter's signature block. Before production,
- You have a Microsoft 365 E5 subscription. A custom type named SIT1 uses an account number regex as its primary element and one supporting element: CustomerName within 200 characters. In invoices, each
- You have a Microsoft 365 E5 subscription. A custom type named SIT1 detects eight-digit member IDs and uses the keyword Member within 1,000 characters as supporting evidence. In exported lists, unlabel
- Custom sensitive information regex patterns require one primary capturing group
Microsoft Purview custom sensitive information regex patterns use one primary capturing group, with noncapturing groups for any additional grouping. Put alternative formats inside that single capturing group rather than using separate top-level captures. Avoid positional anchors such as ^ and $, because the content-scanning process does not guarantee a stable document start or end for matching.
4 questions test this
- You have a Microsoft 365 E5 subscription. A custom type named SIT1 uses one primary capturing group, noncapturing delimiters and no anchors. A new ID variant, two letters plus four letters plus one di
- You have a Microsoft 365 E5 subscription. You create a custom type named SIT1 with the primary regex ^CT[0-9]{8}$. The Test option shows matches when a file contains only a contract number, but docume
- You have a Microsoft 365 E5 subscription. You try to save a custom type that uses this primary regex: (?:\s)([A-Z]{2}[0-9]{3})(?:\s)|(?:\s)([A-Z]{2}[0-9]{5})(?:\s) Validation blocks the pattern. You n
- You have a Microsoft 365 E5 subscription. You need a custom type named SIT1 to detect employee IDs in the format EMP plus six digits or the legacy format CT plus eight digits, separated from text by w
- An XML-based custom SIT needs distinct identifiers and a Unicode rule-package import
When creating a custom SIT from an exported definition, give the RulePack and Entity new GUIDs and make each localized Resource idRef match the corresponding Entity id. In Security & Compliance PowerShell, export definitions with Get-DlpSensitiveInformationTypeRulePackage and write the SerializedClassificationRuleCollection bytes to an XML file before extracting and modifying the required rule. Save the custom rule XML with Unicode encoding matching its utf-16 declaration, then import its bytes with New-DlpSensitiveInformationTypeRulePackage -FileData ([System.IO.File]::ReadAllBytes('C:\Rules\Custom.xml')). Verify the resulting SIT and its display name with Get-DlpSensitiveInformationType before adding it to a consuming policy.
Trap Reusing the exported Entity GUID while changing only its display name, because the GUID identifies the rule independently of the localized name.
5 questions test this
- You have a Microsoft 365 E5 subscription. You pasted the built-in Credit Card Number Entity element, with GUID 50842eb7-edc8-4019-85dd-5a5c1f2bb085, into a new rule package for a customized version. Y
- You have a Microsoft 365 E5 subscription. You plan to customize the XML definition of the built-in Credit Card Number type. You connect to Security & Compliance PowerShell. You need to store the organ
- You have a Microsoft 365 E5 subscription. You uploaded a custom rule package that defines a new type named Contoso Card. Before you add Contoso Card to a DLP policy, you need to confirm in Security &
- You have a Microsoft 365 E5 subscription. In Security & Compliance PowerShell, you ran $ruleCollections = Get-DlpSensitiveInformationTypeRulePackage. You now need an XML file of the rules that you can
- You have a Microsoft 365 E5 subscription. You edited an exported rule package in a text editor and saved it as MyNewRulePack.xml with UTF-8 encoding. The XML declaration specifies encoding="utf-16". A
- Keyword dictionaries provide reusable vocabulary matching at larger scale than keyword lists
When the sensitive content is defined by a maintained vocabulary, use a keyword dictionary as a primary or supporting element in a custom sensitive information type. In the portal, create or edit the type and its pattern before uploading a TXT or CSV dictionary, reusing an existing dictionary, or entering terms. Dictionaries support any language and share a combined tenant limit of 1 MB after compression. For Security & Compliance PowerShell imports, save one keyword per line in a Unicode-encoded text file, read it with [System.IO.File]::ReadAllBytes, and pass those bytes to New-DlpKeywordDictionary -FileData.
Trap Using a regular expression that enumerates every changing project code, because a managed vocabulary is easier to update and reuse than embedding the entire inventory in pattern logic.
4 questions test this
- You have a Microsoft 365 E5 subscription. In the Microsoft Purview portal, you are creating a custom sensitive information type and choose Keyword dictionary as the primary element. Your terms are in
- You have a Microsoft 365 E5 subscription. Legal maintains about 4,000 matter code names that change monthly and appear in English, French, and Japanese documents. Several custom sensitive information
- You have a Microsoft 365 E5 subscription. Three departments plan keyword dictionaries of 400 KB, 350 KB and 450 KB after compression for their own custom types. You need to determine whether the plan
- You have a Microsoft 365 E5 subscription. You exported 3,000 project code names to codes.txt, one name per line, saved with Unicode encoding. In Security & Compliance PowerShell, you read the file int
- Regex validators test whether a well-shaped identifier is actually valid
A regex validator supplements a format match with checks such as a checksum, Luhn validation, or a date embedded in the identifier. Configure checksum weights, modulus, and check-digit position for the identifier's algorithm, or choose the date format and the starting offset of its date substring. Use these validators when format alone accepts invalid values; a date beginning at the first character has offset 0.
Trap Adding a nearby employee keyword to validate an embedded hire date, because contextual evidence does not verify that the identifier contains an acceptable date.
3 questions test this
- You have a Microsoft 365 E5 subscription. You configure a checksum validator for an eight-digit account number. The algorithm multiplies digits 1 through 7 by weights and takes the result modulo 9. Th
- You have a Microsoft 365 E5 subscription. Employee IDs are nine digits: the first six digits are the hire date in DDMMYY format, and the last three are random. You define the primary element as \d{9}
- You have a Microsoft 365 E5 subscription. You are creating a custom type for eight-digit license numbers. The eighth digit is a check digit equal to the weighted sum of the digits modulo 9. Random eig
- Additional checks refine a sensitive information match without replacing its primary pattern
Sensitive information type additional checks can exclude specified test values, reject repeated identical characters, constrain starting or ending characters, and include or exclude immediate prefixes and suffixes. Choose the check that expresses the known false-positive rule instead of weakening all detection. Prefix and suffix checks concern adjacent text, while a supporting element uses a proximity relationship.
Trap Raising the confidence requirement to remove a known test identifier, because the same test value can still appear with convincing contextual evidence.
4 questions test this
- You have a Microsoft 365 E5 subscription. A custom type named OrderSIT detects 10-digit order numbers. QA logs contain test orders written as 4820019375:TEST, which trigger DLP alerts. Real order numb
- You have a Microsoft 365 E5 subscription. A custom type named SIT1 matches 32-character hexadecimal tokens. Log files contain many identifiers written as GUID: followed by a matching value, which must
- You have a Microsoft 365 E5 subscription. A custom type must detect only card numbers that start with 41, 42 or 43. Numbers with any other leading digits must be ignored. You need to configure the res
- You have a Microsoft 365 E5 subscription. A custom type named SIT1 detects six-digit employee IDs. Placeholder values such as 111111 and 000000 in templates cause false positives. No valid employee ID
- Custom sensitive information types require workload-specific testing and tuning
Testing a sensitive information type evaluates the uploaded file rather than refreshing historical classification: test representative matching and nonmatching files and review the number of matches at each confidence level; an Exchange Online license must exist in the tenant for the portal's SIT test option to be available. Also validate the custom detector in each consuming workload, such as Exchange, SharePoint or OneDrive, and endpoints, because extraction and processing limits can change results, and tune against representative false positives and false negatives there. Endpoint DLP evaluates all tenant SITs, including custom types unused by any DLP policy, so reduce excessive classification traffic by removing unused detectors or redesigning overbroad definitions rather than just removing their policy references. After changing a custom definition, unchanged SharePoint and OneDrive files do not automatically acquire updated classification results; use the documented recrawl or on-demand classification process as appropriate, then evaluate policy matches separately.
Trap Restarting an auto-labeling simulation as the mechanism for refreshing old classifier results, because simulation evaluates available classification rather than rescanning all file content.
3 questions test this
- You have a Microsoft 365 E5 subscription. You changed the regex of a custom type named SIT1. A SharePoint auto-labeling policy in simulation misses older unchanged files that contain the new format. R
- You have a Microsoft 365 E5 subscription. You built a custom type named SIT1 that will be used in an Exchange mail flow rule, a SharePoint DLP policy and an Endpoint DLP policy. A test with one sample
- You have a Microsoft 365 E5 subscription that has 50 custom sensitive information types, 40 of which no DLP policy references. After onboarding to Endpoint DLP, devices show excessive classification t
- Mixed Chinese or Japanese patterns need spaced and unspaced variants
Define both spaced and unspaced keyword or regex variants when Chinese or Japanese text is combined with English or single-byte characters. Purview normalizes double-byte text by inserting spaces between words and removing special characters, so a keyword such as 机密的document needs both 机密的document and 机密的 document. Keep double-byte and mixed-language vocabulary in a separate dictionary or keyword list from English-only terms. For these keyword lists, prefer string matching over word matching as Microsoft recommends, rather than relying on English-style word boundaries.
Trap Using only the visually identical unspaced mixed-language keyword with word matching, because token normalization can insert a boundary absent from that literal form.
4 questions test this
- You have a Microsoft 365 E5 subscription. A custom sensitive information type uses a keyword dictionary that contains the mixed term 秘密plan, entered without a space. Some documents that contain 秘密plan
- You have a Microsoft 365 E5 subscription. You are creating a custom sensitive information type with a new keyword list. It must detect the mixed Japanese and English phrase 極秘report. Users type it wit
- You have a Microsoft 365 E5 subscription. A keyword list for a custom type contains Japanese and Chinese phrases. Some phrases aren't detected when they appear inside longer runs of text without space
- You have a Microsoft 365 E5 subscription. You need a custom type that detects the phrases Highly confidential, 機密性が高い and 机密的document in documents. You will use keyword lists for the primary element.
- Document fingerprinting identifies documents derived from a standard textual form
When employees fill in a standard business form, create a fingerprint-based sensitive information type by uploading the blank form or template. Purview derives a word-pattern fingerprint and stores its hash rather than the original document, so the template cannot be reconstructed from the stored value. The template must provide between 256 and 204,800 extracted text characters, and text inside embedded documents is not used to build the fingerprint. Fingerprint definitions share a separate rule pack with a 300 KB maximum size, supporting approximately 100 fingerprints per tenant. To adopt expanded matching capabilities for an existing fingerprint, edit its SIT and upload the same template again rather than creating another fingerprint from an already-used template, which is unsupported.
Trap Using exact data match against a list of employees to recognize the organization's blank HR form, because reference-record matching identifies supplied values rather than the form's stable textual structure.
4 questions test this
- You have a Microsoft 365 E5 subscription. You plan to create a fingerprint-based sensitive information type from the blank merger term sheet that deal teams fill in. Security reviewers worry that a re
- You have a Microsoft 365 E5 subscription. The HR department uses a Word form named NewHire.docx to collect employee details. Completed forms must be detected when they're emailed outside the organizat
- You have a Microsoft 365 E5 subscription. Over several years, departments have created about 100 fingerprint-based sensitive information types, and many are no longer used. Creating a new fingerprint
- You have a Microsoft 365 E5 subscription. You try to create a fingerprint-based sensitive information type from a short cover sheet template named Cover.docx. The template's extracted text is only abo
- Fingerprint matching can tolerate partial similarity or require identical text
Fingerprint-based sensitive information types can assign low, medium, and high confidence thresholds for partial matching using text-match percentages from 30% to 90%. For a strict unchanged-document requirement, set the high-confidence match to Exact, which accepts only identical text and rejects even a small deviation. In Security & Compliance PowerShell, create the fingerprint SIT with New-DlpSensitiveInformationType or modify an existing one with Set-DlpSensitiveInformationType -Identity, passing the blank template's bytes from [System.IO.File]::ReadAllBytes to -FileData. Configure -ThresholdConfig @{low=40;medium=60;high=80} with -IsExact $false when completed or altered forms must still be recognized, or use -IsExact $true for identical-text matching.
Trap Using an exact file hash inventory to recognize filled-in versions of a template, because inserting field values changes file identity even when the form's shared wording remains.
4 questions test this
- You have a Microsoft 365 E5 subscription. You need to create a fingerprint named Patent SIT from C:\Docs\patent.docx by using Security & Compliance PowerShell, with partial-match thresholds of 40, 60
- You have a Microsoft 365 E5 subscription. You are uploading a template to create a fingerprint named FormFP. Low confidence must flag documents that contain at least 40 percent of the template's text,
- You have a Microsoft 365 E5 subscription. You create a document fingerprint from a blank contract template. A DLP rule must detect only files whose text is exactly the same as the fingerprint, and fil
- You have a Microsoft 365 E5 subscription. You run New-DlpSensitiveInformationType -Name "Contract SIT" -FileData $form -ThresholdConfig @{low=40;medium=60;high=80} to create a fingerprint. Contract SI
- Fingerprint protection depends on licensing, readable content, and workload support
Verify E5 licensing before creating or modifying fingerprint SITs or adopting the expanded fingerprint feature set; existing E3 fingerprints and their policies can continue working without granting those management rights. Fingerprint SITs can be used by DLP for Exchange, SharePoint, OneDrive, Teams, and devices, and by auto-labeling for Exchange, SharePoint, and OneDrive. Document fingerprinting excludes password-protected files, image-only files, and files larger than 4 MB. Device use additionally requires Advanced classification scanning and protection, so validate both content eligibility and the destination workload before relying on a fingerprint policy.
Trap Using only an Exchange mail flow rule to protect local USB transfers with a fingerprint, because mail transport does not evaluate endpoint copy activities.
3 questions test this
- You have a Microsoft 365 E5 subscription. You plan to use a fingerprint SIT named NDAFP in an auto-labeling policy that applies the Confidential sensitivity label. You need to identify which location
- You have a Microsoft 365 E5 subscription. A DLP policy for Exchange uses a fingerprint SIT built from the blank claims form. It detects completed 300 KB claims forms sent by email, except when users p
- You have a Microsoft 365 E5 subscription. A DLP policy named DLP1 applies to the Devices location and uses a fingerprint SIT for a tax form. DLP1 detects the form in Exchange and SharePoint, but not w
- Exact data match narrows detection to sensitive values in an organization's reference table
When generic identifiers produce too many unrelated matches, use an EDM sensitive information type to compare detected content against an authoritative structured dataset. EDM checks one-way cryptographic hashes of the supplied values and can use associated fields to strengthen recognition. The source database can contain up to 100 million rows and can be refreshed daily, allowing detection to follow changes in employees, customers, or patients. EDM supports Purview DLP in Exchange Online, SharePoint, OneDrive, Teams chat, and devices, but its documented Defender for Cloud Apps locations are SharePoint and OneDrive. For EDM auto-labeling, supported client-side locations are Word, Excel, PowerPoint, and Exchange desktop clients, while service-side locations are Exchange Online, SharePoint, and OneDrive.
Trap Using a generic national-ID detector alone for a requirement limited to current customers, because format recognition does not establish membership in the customer dataset.
4 questions test this
- You have a Microsoft 365 E5 subscription. You plan to use an EDM-based type named PatientEDM in a sensitivity label's client-side auto-labeling condition so that users get a recommendation while editi
- You have a Microsoft 365 E5 subscription. A bank wants DLP to detect its own account numbers. The account table has 80 million rows and changes every night. An administrator proposes a keyword diction
- You have a Microsoft 365 E5 subscription. You plan to use an EDM-based sensitive information type named CustomerEDM in a Microsoft Defender for Cloud Apps file policy. You need to identify which apps
- You have a Microsoft 365 E5 subscription. You propose an EDM type for the customer table. Legal objects because the table's values must not be shared with anyone, including Microsoft. You need to expl
- An EDM schema defines the reference fields and their matching behavior
The EDM XML schema identifies the DataStore and maps its field names one-to-one to the source table's column headers. It also identifies searchable fields, multi-token corroborative fields, and configurable matching behavior such as ignoring case or delimiters. Keep the exported schema aligned with the data used for hashing and uploading so that the service interprets each column as intended.
Trap Changing the display name of a sensitive information type to repair a source-column mapping error, because field interpretation comes from the EDM schema rather than the display label.
4 questions test this
- You have a Microsoft 365 E5 subscription. An EDM source table stores the LastName corroborative field in uppercase, such as LANGER. Documents write names in mixed case, such as Langer, so expected sup
- You have a Microsoft 365 E5 subscription. An EDM source table includes an Address field with values such as 1 Microsoft Way, Redmond, WA, used as corroborating evidence for patient numbers. No existin
- You have a Microsoft 365 E5 subscription. An EDM schema for employee records has the fields EmployeeID and LastName. EDM must run exact lookups on EmployeeID values found in content. LastName must ser
- You have a Microsoft 365 E5 subscription. Your EDM schema defines the fields PatientID, FirstName, LastName and DateOfBirth. The exported source table uses the column header DOB instead of DateOfBirth
- An EDM primary field needs a detector before exact lookup can validate the record
An EDM rule associates its primary field with an existing sensitive information type that discovers candidate values, then performs exact lookup and checks nearby corroboration. Prefer a strongly defined primary detector and a field with discriminating values, because very broad matches or many repeated primary values increase lookup work and can miss detections through processing timeouts. For supporting values such as full names or addresses, configure multi-token matching when an appropriate pattern detector is impractical.
Trap Selecting a common surname as the primary lookup field to maximize the number of candidates, because frequent repeated values make exact lookup less selective and more expensive.
3 questions test this
- You have a Microsoft 365 E5 subscription. You are designing an EDM type from a 5-million-row orders table. The candidate primary field CountryCode has about 40 distinct values repeated across all rows
- You have a Microsoft 365 E5 subscription. In the new EDM experience, you map the primary field CustomerNumber to a type that matches any eight-digit number, and the system warns about a loosely define
- You have a Microsoft 365 E5 subscription. An EDM source table contains MedicalRecordNumber, which follows a fixed pattern, and PatientName, which is free-form text with first and last names. You need
- The classic EDM experience is required when multiple sensitive information types must share a schema
Use the classic EDM experience when multiple SITs must share a schema, more than 10 SITs are needed, or custom schema naming is required. A tenant supports at most 10 EDM schemas, and the new experience creates a schema and SIT together with a one-to-one relationship. The new experience can infer structure from 10 to 20 representative nonsensitive sample rows. Classic-created and PowerShell-uploaded schemas are not manageable in the new experience.
Trap Creating a separate new-experience schema for every departmental rule over the same customer table, because each creation consumes another of the tenant's schema slots.
4 questions test this
- You have a Microsoft 365 E5 subscription. Your organization needs 14 EDM-based sensitive information types for different regional customer tables. Several of the types should share one schema. You nee
- You have a Microsoft 365 E5 subscription. You create an EDM sensitive information type named PatientNumber in the new experience, which creates the schema automatically. You need the schema name to do
- You have a Microsoft 365 E5 subscription. You create an EDM type in the new experience and choose to provide a sample data file so that the system builds the schema from its headers. The file isn't ha
- You have a Microsoft 365 E5 subscription. Two years ago, an administrator uploaded an EDM schema as an XML file by using PowerShell. You switch to the new EDM experience to add a field. The schema doe
- EDM can separate sensitive-data hashing from the internet-connected upload computer
Use the EDM Upload Agent to hash source data with a salt before uploading it. For stronger separation, create the hash on a secure computer and copy the resulting hash and salt files to the upload computer; both computers must run the same Upload Agent version. The single-computer method requires the clear-text source table on the internet-connected machine, while a schema-inference sample file is a separate upload that must contain nonsensitive representative values.
Trap Uploading a spreadsheet encrypted with a document password as the EDM reference dataset, because the ingestion workflow requires the agent's schema-aware salted hashes.
5 questions test this
- You have a Microsoft 365 E5 subscription. You plan to hash and upload a patient records table for an exact data match type. Security policy forbids the clear-text table from ever residing on a compute
- You have a Microsoft 365 E5 subscription. On an isolated computer, you run EdmUploadAgent.exe /CreateHash for a table named PatientRecords without specifying /Salt. You now need to move the output to
- You have a Microsoft 365 E5 subscription. Using the two-computer method, you copied PatientRecords.EdmHash and its salt file to the internet-connected computer and authorized the EDM Upload Agent. You
- You have a Microsoft 365 E5 subscription. A small company approves hashing and uploading an employee table from one computer named Computer1. Computer1 connects directly to the tenant and stores the c
- You have a Microsoft 365 E5 subscription. You use the two-computer method for an exact data match upload. Computer1 is isolated and creates the hash. Computer2 connects to the internet and uploads it.
- EDM data upload uses a dedicated security group and agent authorization
Add the Microsoft 365 work or school account used for EDM uploads to the EDM_DataUploaders security group, then authorize the Upload Agent with that account. Schema authoring, data ingestion, and policy use are separate phases, so creating the SIT is not evidence that its reference values have been uploaded and indexed. Review upload and indexing status before validating the resulting detector or activating dependent protection.
Trap Publishing a sensitivity label to the upload operator as the authorization for EDM ingestion, because label availability does not assign data-uploader rights.
4 questions test this
- You have a Microsoft 365 E5 subscription. User1 will run the EDM Upload Agent to upload hashed data for an exact data match type. User1 signs in after running /Authorize, but the upload is refused. Yo
- You have a Microsoft 365 E5 subscription. You installed the EDM Upload Agent in C:\EDM\Data on Computer2. User1 is a member of EDM_DataUploaders. Before User1 runs /UploadHash for the first time, the
- You have a Microsoft 365 E5 subscription. You created an EDM sensitive information type named PatientEDM, and its schema appears in the Microsoft Purview portal. User1 then ran the upload. Before you
- You have a Microsoft 365 E5 subscription. Your exact data match data store named PatientRecords is refreshed daily by a scheduled upload. You need to display all the data uploads to PatientRecords and
- EDM source data must be validated against the exact schema before ingestion
Validate an EDM source file with EdmUploadAgent.exe /ValidateData using its /DataFile and /Schema values before hashing and uploading. CSV is the default input format; tab-separated and pipe-separated data are also supported when the delimiter is specified. Embedded delimiters and inconsistent quoting can change the parsed column count, so correct the export format rather than modifying detection confidence to compensate for an ingestion error.
4 questions test this
- You have a Microsoft 365 E5 subscription. A daily EDM upload of 2 million rows fails whenever a handful of rows are malformed. The data owner accepts skipping up to 5 percent of rows. You need the upl
- You have a Microsoft 365 E5 subscription. A vendor system exports a CSV source table for EDM with fields such as "Title, Role" in double quotes and inconsistent single quoting. You can't change the ex
- You have a Microsoft 365 E5 subscription. /ValidateData reports mismatched column counts for an EDM customer table exported as CSV. The affected rows contain names with apostrophes, such as Tom O'Neil
- You have a Microsoft 365 E5 subscription. Before uploading an employee table for an exact data match type, you want to catch formatting and column-mapping problems. You have the data file and the sche
- Trainable classifiers recognize content categories that are difficult to express as deterministic patterns
Use a trainable classifier when the meaning and structure of examples identify a category such as contracts or strategic plans. A Microsoft-provided pretrained classifier is ready to use without your own training, while a custom classifier requires representative organizational examples. Custom classifier language support is limited to English, and classifier processing requires unencrypted items. Check the consuming solution before investing in custom training: Communication Compliance accepts Microsoft-provided trainable classifiers only, so a custom classifier cannot satisfy that consumer's requirement.
Trap Using document fingerprinting for a collection of independently written legal agreements with no shared template, because a common form's text is not available as a stable fingerprint.
4 questions test this
- You have a Microsoft 365 E5 subscription. The pretrained Source code classifier detects code files in a SharePoint site, except for files protected by a sensitivity label that applies encryption. You
- You have a Microsoft 365 E5 subscription. You published a custom trainable classifier named Contracts that you seeded with English-language contracts. An auto-labeling policy that uses Contracts label
- You have a Microsoft 365 E5 subscription. Legal stores thousands of nondisclosure agreements drafted by different outside firms. Each firm uses its own structure and wording, and there's no shared tem
- You have a Microsoft 365 E5 subscription. You built and published a custom trainable classifier named Harassment that performs well in auto-labeling. When creating a Communication Compliance policy, y
Prepare 50 to 500 positive samples and 150 to 1,500 negative samples for a custom trainable classifier, placing the collections in separate dedicated SharePoint folders. Use text-based supported files, including suitable Office files and text-bearing PDFs, and allow at least an hour for a newly created seed location to be indexed. The training account needs access to both folders; OneDrive folders, Teams folder types, images, and image-only PDFs are unsuitable seed locations or content. Processing uses up to the 2,000 most recently created samples by file creation timestamp, so keep the seed folders controlled to prevent unintended newer files from displacing the examples you selected.
Trap Using only highly representative positive examples to accelerate training, because the model also needs content that establishes what falls outside the category.
4 questions test this
- You have a Microsoft 365 E5 subscription. The positive seed folder for a custom classifier named Policies holds 450 curated policy documents. An automated job also saves about 2,000 new meeting notes
- You have a Microsoft 365 E5 subscription. You seed a custom classifier with 200 scanned contracts saved as image-only PDF files and 300 Word documents as negative samples. The classifier fails to lear
- You have a Microsoft 365 E5 subscription. User1 uploaded positive and negative seed documents for a custom classifier to two folders in User1's OneDrive. The creation wizard can't use the folders. You
- You have a Microsoft 365 E5 subscription. You plan a custom trainable classifier named Reviews for engineering design review documents. You collected 30 positive samples and 400 negative samples. You
- Trainable-classifier lifecycle changes require validation and policy-impact review
Review a custom classifier's predictions and verify true positives, true negatives, false positives, and false negatives before publishing it for policy use. By default, the creator is the person who can train it and review its predictions. Improve an unpublished classifier by updating samples and restarting training; a published custom classifier must be removed and recreated to improve its accuracy because retraining it is unsupported. To suppress automatic Content explorer display of trainable-classifier detections not used in labeling policies, request the display change through Microsoft Support rather than disabling classifier scanning. Disabling scanning is a separate support request that stops sensitivity-labeling and DLP policies using those classifiers from working, so review dependent protection before requesting it.
Trap Editing a sensitivity label's confidence threshold to retrain a published classifier, because policy evaluation settings do not rebuild the learned model.
4 questions test this
- You have a Microsoft 365 E5 subscription. Testing of an unpublished custom classifier named Specs, seeded from engineering specification documents, shows many incorrect predictions. Specs hasn't been
- You have a Microsoft 365 E5 subscription. A custom classifier named Invoices shows the status Training is complete and items have been tested. Policies will use Invoices next month. You need to follow
- You have a Microsoft 365 E5 subscription. A published custom classifier named Specs is used by an auto-labeling policy and mislabels many files. A colleague suggests editing the sensitivity label's se
- You have a Microsoft 365 E5 subscription. User1 created a custom classifier named Payroll. User2, a Compliance Administrator, must review Payroll's test predictions while User1 is on leave. User2 can'
- Data explorer and Content explorer provide an inventory of classified and labeled items
Use Data explorer or Content explorer to locate items associated with sensitive information types, sensitivity labels, retention labels, and supported trainable classifiers. Start with the classifier or label, choose the data source, and drill into the repository to inspect matching items. Filter Exchange or Teams by a full mailbox address, and SharePoint or OneDrive by site, folder, or file information; CSV export reflects the current focus of the pane rather than an automatically complete tenant report. These views describe the classified-content inventory; use activity or audit records when the requirement is to establish who changed a label and when.
Trap Using a label publishing policy's target-user list as the inventory of labeled files, because publication records eligibility to apply a label rather than which content carries it.
4 questions test this
- You have a Microsoft 365 E5 subscription. The legal team asks how many SharePoint and OneDrive documents currently match the built-in Resumes trainable classifier, and where they are stored. You need
- You have a Microsoft 365 E5 subscription. Each morning, User1 opens Content explorer and must find the same three sensitive information types, two sensitivity labels and one retention label among hund
- You have a Microsoft 365 E5 subscription. A file named Budget.xlsx in Site1 had the Confidential sensitivity label last week but has no label today. Data explorer shows the file's current state only.
- You have a Microsoft 365 E5 subscription. In Content explorer, you select a sensitive information type and drill into the Exchange location to review items for one mailbox that belongs to User1. You n
- Explorer navigation, item listing, and content viewing require different permissions
An administrative role that exposes an explorer page does not by itself grant access to its item list or content. Data Explorer List viewer and Data Explorer Content viewer grant independent permissions through Data Classification List Viewer and Data Classification Content Viewer; Content explorer uses the corresponding Content Explorer role groups. Grant both capabilities when a user must list locations and read content, and apply administrative-unit restrictions when access must be scoped; content-view permission is also needed to reveal potentially sensitive item names.
Trap Assigning Compliance Administrator alone to an investigator who needs document previews, because portal administration and direct access to classified content are separate permissions.
4 questions test this
- You have a Microsoft 365 E5 subscription. User1 is a member of the Data Explorer List viewer role group. In Data explorer, User1 sees each item and its location, but item names that might contain sens
- You have a Microsoft 365 E5 subscription. The security team wants to manage one role group for investigators. It must include the data classification list viewer role together with other Purview roles
- You have a Microsoft 365 E5 subscription that uses administrative units for regions. User1 manages data classification for the Europe region only. User1 must see only Europe items in Content explorer.
- You have a Microsoft 365 E5 subscription. User1 must review sensitive files in Content explorer, which includes seeing each file's location and opening its contents. User1 has the Security Administrat
- Explorer investigations must account for indexing delays and encrypted-content restrictions
Explorer counts can take up to seven days to update, and SharePoint file results can take up to fourteen days, so an immediate count is not a real-time completeness check. Preview and download are disabled for encrypted documents.
Trap Granting broader explorer content permissions to solve an encrypted document's unavailable preview, because the preview restriction is a product boundary rather than missing list access.
5 questions test this
- You have a Microsoft 365 E5 subscription. Users started applying the Internal label to Exchange email three days ago. In Content explorer, the Exchange count for Internal is still lower than expected,
- You have a Microsoft 365 E5 subscription. Nine days ago, users uploaded 5,000 files to a SharePoint site, and some files are encrypted by a label. Content explorer counts don't include the new files y
- You have a Microsoft 365 E5 subscription. Five days ago, an auto-labeling policy applied the Confidential label to many files in SharePoint Online. Content explorer doesn't yet show the new counts for
- You have a Microsoft 365 E5 subscription. Ten days ago, a retention label was auto-applied to Exchange mailboxes and SharePoint sites. Content explorer now shows current counts for Exchange but not fo
- You have a Microsoft 365 E5 subscription. User1 is a member of Content Explorer List viewer and Content Explorer Content viewer. User1 can open most documents in Content explorer, but documents labele
- Explorer match feedback identifies classification errors to guide detector tuning
In Content explorer, review a supported SIT or trainable-classifier match for a SharePoint or OneDrive item and record Match for a true positive or Not a Match for a false positive. Use the classifier's matched-items view or the item's available contextual summary to inspect the detection, and use Withdraw feedback to correct a mistaken submission. Apply the findings to detector tuning rather than treating a feedback selection as an immediate change to its rules. EDM, named-entity, and credential-scanning SITs do not support Match and Not a Match feedback, so check the classifier's feedback capability before choosing this workflow.
Trap Raising the policy's match-count threshold before reviewing disputed items, because changing how many detections trigger a policy does not establish whether those detections are correct.
5 questions test this
- You have a Microsoft 365 E5 subscription. A custom sensitive information type named SIT1 matched a OneDrive file that contains no sensitive data. You open the file in Content explorer and review it on
- You have a Microsoft 365 E5 subscription. You plan to collect Match and Not a match feedback in Content explorer to tune the classifiers used in your DLP policies for SharePoint. You need to identify
- You have a Microsoft 365 E5 subscription. Over a week, analysts mark 200 SharePoint matches of a custom type named SIT1 as Not a match. A DLP rule still blocks the same kinds of files. A manager expec
- You have a Microsoft 365 E5 subscription. You review OneDrive matches for an exact data match sensitive information type named EDM1 in Content explorer. The Match and Not a match options don't appear
- You have a Microsoft 365 E5 subscription. A DLP policy uses a custom sensitive information type and matches both Exchange email and SharePoint files. You need to give Match or Not a match feedback on
- On-demand classification requires a scope and policy-impact review before execution
Before starting on-demand classification for SharePoint or OneDrive, review active policies that could act on refreshed results: apply-label or label-removal policies can change files even while the policy being investigated remains in simulation. Under Information Protection > Classifiers > On-demand classification, create a scan and select locations, classifiers, file extensions, and the file last-modified date range to include the intended historical files. Review View estimation and estimated charges, adjust scope if necessary, and only then select Start classification. Running the scan requires Compliance Administrator membership; inspecting classification results separately requires Content Explorer List Viewer or Content Explorer Content Viewer permissions for the intended view.
Trap Using one auto-labeling policy's simulation state as tenant-wide change isolation during an on-demand scan, because other active policies can act on the refreshed classification.
5 questions test this
- You have a Microsoft 365 E5 subscription. You run an on-demand classification scan of SharePoint that selects only the Credit Card Number classifier. Afterward, a DLP policy based on the U.S. Social S
- You have a Microsoft 365 E5 subscription. You are testing an auto-labeling policy in simulation mode. A separate active policy removes a label from files that match a sensitive information type. You p
- You have a Microsoft 365 E5 subscription. You finished the on-demand classification wizard for a scan named Scan1 that covers 300 SharePoint sites. Finance must approve the expected cost before any fi
- You have a Microsoft 365 E5 subscription that uses several EDM classifiers. An on-demand classification estimate for OneDrive is far higher than expected because previously classified files are rescan
- You have a Microsoft 365 E5 subscription. You create an on-demand classification scan to classify SharePoint files that were last modified in 2022 and 2023. You keep the wizard defaults. The estimatio
- OCR adds image text to existing Purview detection after billing and locations are configured
Enable OCR at tenant level after connecting an Azure pay-as-you-go subscription through Microsoft Syntex billing; deploying Microsoft Syntex itself is not required. In Microsoft Purview Settings, select Optical character recognition and configure the locations and included or excluded groups. Existing sensitive information types, EDM, trainable classifiers, and fingerprint SITs can then recognize extracted image content, with each workload limited to its supported solutions. Only images uploaded after OCR is enabled are scanned, so activation does not provide retrospective coverage of existing images.
Trap Creating a second credit-card SIT specifically for screenshots before enabling image scanning, because OCR supplies extracted text to existing detectors.
4 questions test this
- You have a Microsoft 365 E5 subscription. Yesterday, you enabled OCR for SharePoint. Today, a DLP policy detects SSNs in newly uploaded scanned forms but not in thousands of scanned forms uploaded las
- You have a Microsoft 365 E5 subscription. You enabled OCR for SharePoint sites. A DLP policy uses the built-in Credit Card Number type. A team proposes creating a second credit card type specifically
- You have a Microsoft 365 E5 subscription with Microsoft Syntex pay-as-you-go billing configured. You need OCR to scan images in Exchange and on Windows devices for members of the Finance group only. Y
- You have a Microsoft 365 E5 subscription and an Azure pay-as-you-go subscription. You plan to have DLP policies detect credit card numbers in scanned images in SharePoint and Exchange. You need to com
- OCR eligibility depends on workload-specific size, format, and image dimensions
OCR permits images up to 20 MB in Exchange and Teams and up to 50 MB in SharePoint, OneDrive, and Windows or macOS endpoints. Supported image dimensions range from 50 by 50 to 16,000 by 16,000 pixels, and extraction is limited to the first 2 million characters. Exchange supports selected embedded-image formats with at most 20 embedded images scanned per file, while Teams and endpoints support JPEG, JPG, PNG, BMP, TIFF, and image-only PDFs; check the location's format support before choosing the policy design.
4 questions test this
- You have a Microsoft 365 E5 subscription with OCR enabled for SharePoint. A site contains small JPG thumbnails of ID cards that are 40 × 40 pixels, and larger 1,200 × 800 pixel images. DLP detects IDs
- You have a Microsoft 365 E5 subscription with OCR enabled for Exchange. A user sends a ZIP file that contains 30 scanned invoice images. Only some of the images trigger the DLP policy that should matc
- You have a Microsoft 365 E5 subscription with OCR enabled for SharePoint and Windows devices. Users store screenshots as GIF files in SharePoint and in local folders on Windows 11 devices. DLP detects
- You have a Microsoft 365 E5 subscription with OCR enabled for Exchange. A user emails a 25 MB high-resolution PNG scan of a passport to an external recipient. A DLP policy that detects passport number
- Exchange OCR scope controls scanning but does not provide image policy tips
Exchange OCR scans incoming, internal, and outgoing email by default, but Exchange DLP policy tips are not supported for images. Select Specific sender groups to limit the sender population, or the Exchange advanced option for only externally sent mail to exclude both incoming and internal traffic.
Trap Changing a sensitivity label's publishing audience to reduce Exchange OCR scanning, because label publication does not set the OCR sender or direction scope.
4 questions test this
- You have a Microsoft 365 E5 subscription with OCR enabled for Exchange using the default scope. Costs are high because of images in email from external senders. You need to exclude incoming email from
- You have a Microsoft 365 E5 subscription. OCR must scan images only in email sent by members of the Legal and HR groups, including their internal and outgoing mail. Email from other users and from ext
- You have a Microsoft 365 E5 subscription. You enable OCR for Exchange and keep the default sender scope. Before estimating costs, the finance team asks which email messages will have their images scan
- You have a Microsoft 365 E5 subscription. OCR is enabled for Exchange. A DLP policy detects credit card numbers in PNG attachments and in message text. Users see a policy tip when the number is in the
- Endpoint OCR depends on cloud connectivity, bandwidth, and file-path coverage
Windows and macOS endpoints send images to the cloud for OCR, with a default advanced-classification bandwidth limit of 1,024 MB per device per day. OCR stops scanning images after the device reaches that limit; increase it when the required coverage justifies the additional traffic. Endpoint DLP file-path exclusions also exclude those folders from OCR, and network controls must permit the required blob.core.windows.net endpoints.
Trap Adding another sensitive information type to a policy when image classification stops after heavy device use, because detector selection does not increase the device's cloud-scanning bandwidth.
4 questions test this
- You have a Microsoft 365 E5 subscription. You plan to enable OCR for 2,000 Windows 11 devices and must estimate upload traffic. The default device settings will be kept. You need to identify the defau
- You have a Microsoft 365 E5 subscription. Endpoint OCR is enabled for Windows devices that use a corporate proxy. DLP detects sensitive text in documents, but images are never classified. Devices are
- You have a Microsoft 365 E5 subscription with OCR enabled for Windows devices. Endpoint DLP settings exclude the path C:\Scans to reduce scanning of scanner output. A new policy must detect SSNs in im
- You have a Microsoft 365 E5 subscription with OCR enabled for Windows devices. Engineers on Device1 copy hundreds of screenshots daily. By midafternoon, OCR stops detecting sensitive data in new image
- OCR charges per scanned image rather than per policy that uses its results
Each scanned standalone image is an OCR transaction, and each PDF page is charged separately. The same extracted result can be used by multiple supported Purview policies without an additional scan charge for each policy. Exchange caches eligible repeated small images across the tenant for a moving five-day window, and endpoints maintain a local thirty-day cache; standalone SharePoint and OneDrive images do not use that caching mechanism.
4 questions test this
- You have a Microsoft 365 E5 subscription with OCR enabled for Exchange. All 8,000 users include the same company logo image in their email signatures, sending thousands of messages each day. You need
- You have a Microsoft 365 E5 subscription that uses Endpoint OCR. Over two weeks, Endpoint DLP evaluates the same unchanged screenshot on one Windows device many times. Finance asks how repeated OCR ch
- You have a Microsoft 365 E5 subscription. OCR is enabled for SharePoint. A user uploads a 12-page scanned PDF file. Two DLP policies and one auto-apply retention label policy evaluate the extracted te
- You have a Microsoft 365 E5 subscription with OCR enabled. An image in Exchange is scanned and is evaluated by a DLP policy, an auto-labeling policy and an auto-apply retention label policy. The finan
References
- https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/sc-401
- https://learn.microsoft.com/en-us/purview/information-protection
- https://learn.microsoft.com/en-us/purview/sit-sensitive-information-type-learn-about
- https://learn.microsoft.com/en-us/purview/data-classification-overview
- https://learn.microsoft.com/en-us/purview/get-started-with-sensitivity-labels
- https://learn.microsoft.com/en-us/purview/sensitivity-labels
- https://learn.microsoft.com/en-us/purview/data-classification-content-explorer
- https://learn.microsoft.com/en-us/purview/sit-document-fingerprinting
- https://learn.microsoft.com/en-us/purview/sit-create-a-custom-sensitive-information-type
- https://learn.microsoft.com/en-us/purview/sit-named-entities-learn
- https://learn.microsoft.com/en-us/purview/sit-customize-a-built-in-sensitive-information-type
- https://learn.microsoft.com/en-us/purview/sit-create-a-keyword-dictionary
- https://learn.microsoft.com/en-us/purview/sit-regex-validators-additional-checks
- https://learn.microsoft.com/en-us/purview/auto-label-classification-simulation
- https://learn.microsoft.com/en-us/defender-office-365/scc-permissions
- https://learn.microsoft.com/en-us/purview/purview-permissions
- https://learn.microsoft.com/en-us/purview/sit-learn-about-exact-data-match-based-sits
- https://learn.microsoft.com/en-us/purview/sit-get-started-exact-data-match-based-sits-overview
- https://learn.microsoft.com/en-us/purview/sit-get-started-exact-data-match-hash-upload
- https://learn.microsoft.com/en-us/purview/trainable-classifiers-learn-about
- https://learn.microsoft.com/en-us/purview/trainable-classifiers-get-started-with
- https://learn.microsoft.com/en-us/purview/data-classification-data-explorer
- https://learn.microsoft.com/en-us/purview/sensitivity-labels-sharepoint-onedrive-files
- https://learn.microsoft.com/en-us/purview/data-classification-activity-explorer
- https://learn.microsoft.com/en-us/purview/data-classification-increase-accuracy
- https://learn.microsoft.com/en-us/purview/on-demand-classification
- https://learn.microsoft.com/en-us/purview/ocr-learn-about