Viewing Regex in Built-in Sensitive Info Types
You have a Microsoft 365 E5 tenant that contains a user named User1. User1 is assigned the Compliance Administrator role. User1 cannot view the regular expression in the IP Address sensitive info type. You need to ensure that User1 can view the regular expression. What should you do?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests the limitation of editing Microsoft-predefined sensitive info types; the trap is assuming role assignment grants visibility to internal regex logic.
Built-in sensitive info types in Microsoft Purview DLP hide the underlying regular expressions for security. To view or modify these regex patterns, users must create a copy of the built-in type and edit that instance.
Learners often select assigning higher administrative roles like Global Reader, believing elevated permissions grant access to all configuration details, including hidden regex strings.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Microsoft defines built-in sensitive info types as immutable templates within the compliance center. While a Compliance Administrator can configure policies using these types, the system deliberately hides the complex regular expressions used for detection to prevent accidental misconfiguration. By creating a copy of the built-in type, you generate a custom instance that unlocks the 'Edit' interface, allowing User1 to view and modify the underlying regular expression.Why the Other Options Are Wrong
Assigning the Global Reader role (Option A) provides read-only access to the entire tenant but does not bypass the UI restriction hiding the regex in built-in types. The Reviewer role group (Option B) is typically associated with content review workflows, not DLP policy configuration. Using the Test function (Option C) allows validation of matches against sample data but does not expose the source code or regex pattern itself.Community Comment Notes
Community feedback strongly supports Option D, with users noting that testing in a lab confirmed the inability to view regex in the standard edit screen. As SDiwan noted, "You can only see the regex in edit screen" of a copied instance. Official documentation confirms that while built-ins cannot be edited directly, copying them enables customization and inspection.Official Reference
Exam Strategy
When dealing with Microsoft Purview built-in objects, always consider if they are locked/immutable. If you need to inspect or change internal properties of a built-in template, the standard procedure is usually to duplicate it first.
Frequently Asked Questions
Why can't I view the regex in a built-in sensitive info type?
Built-in types are predefined by Microsoft to ensure stability. The regex is hidden to prevent accidental changes that could break detection accuracy.
Does the Compliance Administrator role allow editing built-in types?
No. This role allows managing policies but cannot modify the core definition of Microsoft's pre-built sensitive info types directly.