Copying Sensitive Information Types in Microsoft Purview
HOTSPOT
You have a Microsoft 365 365 E5 subscription.
You plan to create a new sensitive information type (SIT) by using the Microsoft Purview portal.
You need to copy and modify an existing SIT from which to create the new SIT.
What are two SITs that you can copy and modify? To answer, select the appropriate SITs in the answer area.
NOTE: Each correct selection is worth one point.
Community Insight
The core trap is confusing 'Built-in' Microsoft SITs with 'Custom' tenant-specific SITs; only the latter are editable templates for new SIT creation.
This question tests the ability to identify which Sensitive Information Types (SITs) can be copied and modified in Microsoft Purview. It establishes that custom SITs created by the organization can be cloned, while built-in entity-based SITs cannot.
Candidates often incorrectly select built-in types like 'ABA Routing Number' or 'All Credential Types', assuming all listed patterns are modifiable, failing to distinguish between Microsoft-provided definitions and custom organizational ones.
Community Discussion (10 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
In Microsoft Purview, you can copy and modify a Sensitive Information Type (SIT) only if it was created within your own organization (custom SIT). Built-in SITs provided by Microsoft, even those based on standard entities like ABA Routing Numbers, cannot be directly copied or edited as templates because they are part of the global Microsoft definition set. The correct selections are the custom SITs named 'Adatum routing number' and 'Adatum numbers', as these are specific to the tenant and allow for modification.Why Other Candidate Answers Are Wrong
Options such as 'ABA Routing Number (Entity)', 'All Credential Types', and 'All Full Names' are built-in Microsoft SITs. These are standardized, fingerprinted, or bundled definitions managed by Microsoft. While you can use them in policies, you cannot duplicate them into the 'My Custom Sensitive Information Types' section to create a variant. Attempting to copy them results in an error or is simply not an available action in the UI.Community Comment Notes
Community consensus strongly supports selecting the Adatum options. Users note that 'only repeatable, standardized patterns... can be copied' refers to custom regex/keyword patterns defined by the admin. One commenter clarified that 'Named entity sensitive information types... can't be copied,' reinforcing that built-in entities are off-limits for cloning. Another user emphasized that 'Built-in SITs... cannot be copied or modified,' confirming the distinction between publisher origins.Official Reference
Exam Strategy
When asked about copying or modifying SITs, immediately look for 'Custom' vs. 'Built-in'. If the SIT name includes your company name or a specific project code (like Adatum), it is likely custom and copyable. Generic names like 'Credit Card' or 'SSN' are usually built-in and not copyable.
Frequently Asked Questions
Can I copy built-in SITs like ABA Routing Number?
No. Built-in SITs provided by Microsoft cannot be copied or modified. You must create a new custom SIT from scratch if you need to adjust detection logic for these standards.
What defines a custom SIT that can be copied?
A custom SIT is one created by your organization's admins. It typically has a unique name or includes your tenant domain in the publisher field, distinguishing it from Microsoft's global definitions.