Skip to content

Commit ace1faa

Browse files
Merge pull request #3105 from jinruishao/patch-35
Update overview.md
2 parents 11d2aa5 + 0fb183f commit ace1faa

File tree

1 file changed

+13
-21
lines changed

1 file changed

+13
-21
lines changed

articles/ai-services/content-safety/overview.md

Lines changed: 13 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -159,19 +159,19 @@ To use the Content Safety APIs, you must create your Azure AI Content Safety res
159159
| East US ||||||||||
160160
| East US 2 | ||| ||||||
161161
| France Central | ||| ||||||
162-
| Japan East | | || |||||| |
163-
| North Central US | | | |||||| |
164-
| Poland Central | | || | ||||| |
165-
| South Central US | | || |||||| |
166-
| South India | | || || |||| |
167-
| Sweden Central | ||| |||||| |
168-
| Switzerland North || || |||||| |
169-
| Switzerland West | | || |||||| |
170-
| UAE North | | || |||||| |
171-
| UK South | ||| |||||| |
172-
| West Europe | | |||||||||
173-
| West US | ||| |||||| |
174-
| West US 2 | | || |||||| |
162+
| Japan East | | || ||||||
163+
| North Central US | | | | ||||||
164+
| Poland Central | | || | |||||
165+
| South Central US | | || ||||||
166+
| South India | | || || ||||
167+
| Sweden Central | ||| ||||||
168+
| Switzerland North || || ||||||
169+
| Switzerland West | | || ||||||
170+
| UAE North | | || ||||||
171+
| UK South | ||| ||||||
172+
| West Europe | | ||||||||
173+
| West US | ||| ||||||
174+
| West US 2 | | || ||||||
175175
| West US 3 | | || ||||||
176176
| FairFax - USGovArizona| | || | ||| ||
177177
| FairFax - USGovVirginia| | || | ||| ||
@@ -189,14 +189,6 @@ Content Safety features have query rate limits in requests-per-second (RPS) or r
189189

190190
If you need a faster rate, please [contact us](mailto:[email protected]) to request it.
191191

192-
### Encryption
193-
194-
Content Safety encryption protects your data at rest. It encrypts your data as it is written in our datacenters and automatically decrypts it when you access it.
195-
196-
By default, data in Content Safety is encrypted using Microsoft Managed Keys (MMK). However, Content Safety supports both Microsoft Managed Keys (MMK) and Customer Managed Keys (CMK) for encryption. When CMK is selected, users can choose CMK and have the ability to select either user-assigned managed identities (UMI) or system-assigned managed identities (SMI).
197-
198-
199-
200192

201193
## Contact us
202194

0 commit comments

Comments
 (0)