Skip to content

Commit 55b76b6

Browse files
author
Jill Grant
authored
Merge pull request #1679 from renaaliu/patch-4
Update how-to-call.md with redaction policy examples
2 parents 81d614e + 5b98784 commit 55b76b6

File tree

1 file changed

+7
-8
lines changed
  • articles/ai-services/language-service/personally-identifiable-information

1 file changed

+7
-8
lines changed

articles/ai-services/language-service/personally-identifiable-information/how-to-call.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.custom: language-service-pii, ignite-2024
1515

1616
# How to detect and redact Personally Identifying Information (PII)
1717

18-
The PII feature can evaluate unstructured text, extract and redact sensitive information (PII) and health information (PHI) in text across several [pre-defined categories](concepts/entity-categories.md).
18+
The PII feature can evaluate unstructured text, extract, and redact sensitive information (PII) and health information (PHI) in text across several [predefined categories](concepts/entity-categories.md).
1919

2020

2121
## Development options
@@ -30,23 +30,22 @@ By default, this feature uses the latest available AI model on your text. You ca
3030

3131
### Input languages
3232

33-
When you submit documents to be processed, you can specify which of [the supported languages](language-support.md) they're written in. if you don't specify a language, extraction defaults to English. The API may return offsets in the response to support different [multilingual and emoji encodings](../concepts/multilingual-emoji-support.md).
33+
When you submit documents to be processed, you can specify which of [the supported languages](language-support.md) they're written in. If you don't specify a language, extraction defaults to English. The API may return offsets in the response to support different [multilingual and emoji encodings](../concepts/multilingual-emoji-support.md).
3434

3535
### Redaction Policy (version 2024-11-5-preview only)
36-
37-
in version 2024-11-5-preview, you're able to define the `redactionPolicy` parameter to reflect the redaction policy to be used when redacting the document in the response. The policy field supports 3 policy types:
36+
In version 2024-11-5-preview, you're able to define the `redactionPolicy` parameter to reflect the redaction policy to be used when redacting text. The policy field supports three policy types:
3837

3938
- `DoNotRedact`
4039
- `MaskWithCharacter` (default)
4140
- `MaskWithEntityType`
4241

43-
The `DoNotRedact` policy allows the user to return the response without the `redactedText` field.
42+
The `DoNotRedact` policy allows the user to return the response without the `redactedText` field, that is, “John Doe received a call from 424-878-9192”.
4443

45-
The `MaskWithRedactionCharacter` policy allows the `redactedText` to be masked with a character, preserving the length and offset of the original text. This is the existing behavior.
44+
The `MaskWithRedactionCharacter` policy allows the `redactedText` to be masked with a character (such as "*"), preserving the length and offset of the original text, that is, “******** received a call from ************. This is the existing behavior.
4645

47-
There is also an optional field called `redactionCharacter` where you can input the character to be used in redaction if you're using the `MaskWithCharacter` policy
46+
There's also an optional field called `redactionCharacter` where you can input the character to be used in redaction if you're using the `MaskWithCharacter` policy
4847

49-
The `MaskWithEntityType` policy allows you to mask the detected PII entity text with the detected entity type.
48+
The `MaskWithEntityType` policy allows you to mask the detected PII entity text with the detected entity type, that is, “[PERSON_1] received a call from [PHONENUMBER_1].
5049

5150
## Submitting data
5251

0 commit comments

Comments
 (0)