AI Navigate

PII detection

Azure OpenAI Service ドキュメント / 3/21/2026

💬 OpinionIdeas & Deep AnalysisTools & Practical Usage

Key Points

  • PII detection is about identifying personally identifiable information in text and data pipelines to support privacy and regulatory compliance.
  • The article suggests practical methods for detecting PII, potentially combining rule-based and machine learning approaches.
  • It highlights key challenges such as accuracy, false positives/negatives, and balancing privacy with data utility across different jurisdictions.
  • Practical applications include data redaction, access control, and auditability in organizational data workflows.
Table of contents Exit editor mode
Ask Learn Ask Learn Focus mode
Table of contents Read in English Add Add to plan Edit

Share via

Facebook x.com LinkedIn Email
Copy Markdown Print

Note

Access to this page requires authorization. You can try signing in or changing directories.

Access to this page requires authorization. You can try changing directories.

Personally identifiable information (PII) filter (classic)

Feedback
Summarize this article for me

Currently viewing: Foundry (classic) portal version - Switch to version for the new Foundry portal

Personally identifiable information (personal data) refers to any information that can be used to identify a particular individual, such as a name, address, phone number, email address, social security number, driver's license number, passport number, or similar information.

Personal data detection is used to help prevent personal data from being exposed or shared, protecting users from identity theft, financial fraud, or other types of privacy violations.

In the context of large language models (LLMs), personal data detection involves analyzing text content in LLM completions. When personal data has been identified, it can be flagged for further review, or the output can be blocked. The personal data filter scans the output of LLMs to identify and flag known personal information. It's designed to help organizations prevent the generation of content that closely matches sensitive personal information.

For example, if a model generates "Contact me at john@example.com or call 555-0123", the personal data filter can detect and flag the email address and phone number before the content reaches the user.

Tip

Use personal data filtering to meet compliance requirements (HIPAA, CCPA), prevent data leaks in customer-facing applications, and audit sensitive information exposure in model outputs.

Personal data types

There are many different types of personal data, and you can specify which types you want to filter. Common personal data categories include:

  • Personal information: Email, PhoneNumber, Address, Person, IPAddress, Date of Birth, Drivers License Number, Passport Number
  • Financial information: Credit Card Number, Bank Account Number, SWIFT Code, IBAN
  • Government IDs: Social Security Number (US), National ID numbers (50+ countries), Tax IDs, Passport numbers
  • Azure-related: Connection strings, storage account keys, authentication keys
  • Geolocation: Airport, City, State, specific locations

For the complete list of supported personal data entity types, see personal data entity categories.

Filtering modes

The personal data filter can be configured to operate in two modes:

  • Annotate mode flags personal data that's returned in the model output.
  • Annotate and Block mode blocks the entire output if personal data is detected.

The filtering mode can be set for each personal data category individually.

Next steps


Feedback

Was this page helpful?

Yes No
No

Need help with this topic?

Want to try using Ask Learn to clarify or guide you through this topic?

Ask Learn Ask Learn
Suggest a fix?

Additional resources


  • Last updated on 2026-03-20