All Full Names
Catalogue reference for the Microsoft Purview built-in All Full Names named-entity SIT. This YAML-only record supplies supplementary name-field vocabulary for registry search and testing; it does not reproduce Microsoft's opaque name-recognition resources.
- Type
- keyword_list
- Confidence
- low
- Confidence justification
- Low confidence: broad keyword matching on name-related terms requires additional context. Name keywords appear frequently in forms, directories, and general documents without constituting sensitive personal information.
- Jurisdictions
- global
- Regulations
- CCPA/CPRA, GDPR
- Frameworks
- ISO 27001, ISO 27701, PCI-DSS, SOC 2
- Data categories
- pii
- Scope
- wide
- Risk rating
- 3
Should match
given name— Exact 65 supplementary discovery probe - one name-field term without person-record contextapplicant full name on identity record— Exact 75 supplementary probe - name-field term with person-record context but no additional fieldsidentity record for applicant: full name, given name, surname— Exact 85 supplementary probe - person-record context with two additional distinct name fields
Should not match
quarterly financial report for fiscal year 2024— Financial text with no name-related keywordsthe server configuration has been updated successfully— Technical text with no personal name terminology
Known false positives
- Form labels, headers, or templates that reference name fields without containing actual names Mitigation: Layer with named entity recognition to confirm keyword matches co-occur with actual personal name values rather than field labels.
- Software documentation referencing name-related variables or database columns Mitigation: Use document classification to distinguish personnel records from technical documentation.