Skip to content

Commit 0826c1f

Browse files
committed
consaf freshness pt 2
1 parent 180de39 commit 0826c1f

File tree

5 files changed

+44
-38
lines changed

5 files changed

+44
-38
lines changed

articles/ai-services/content-safety/how-to/custom-categories-rapid.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,17 @@
11
---
22
title: "Use the custom categories (rapid) API (preview)"
33
titleSuffix: Azure AI services
4-
description: Learn how to use the custom categories (rapid) API to mitigate harmful content incidents quickly.
4+
description: Learn how to use the custom categories (rapid) API to mitigate harmful content incidents quickly and flexibly.
55
#services: cognitive-services
66
author: PatrickFarley
77
manager: nitinme
88
ms.service: azure-ai-content-safety
99
ms.custom: build-2024
1010
ms.topic: how-to
11-
ms.date: 04/11/2024
11+
ms.date: 01/29/2025
1212
ms.author: pafarley
13+
#customer intent: As a developer, I want to use the custom categories (rapid) API so that I can mitigate harmful content incidents quickly and flexibly.
14+
1315
---
1416

1517

articles/ai-services/content-safety/how-to/encrypt-data-at-rest.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: nitinme
77
ms.service: azure-ai-content-safety
88
ms.custom: build-2023
99
ms.topic: conceptual
10-
ms.date: 06/01/2024
10+
ms.date: 01/29/2025
1111
ms.author: pafarley
1212
---
1313

@@ -133,13 +133,15 @@ When you disable customer-managed keys, your Azure AI services resource is then
133133
1. Go to your Azure AI services resource, and then select **Encryption**.
134134
1. Select **Microsoft Managed Keys** > **Save**.
135135

136-
When you previously enabled customer managed keys this also enabled a system assigned managed identity, a feature of Microsoft Entra ID. Once the system assigned managed identity is enabled, this resource will be registered with Microsoft Entra ID. After being registered, the managed identity will be given access to the Key Vault selected during customer managed key setup. You can learn more about [Managed Identities](/azure/active-directory/managed-identities-azure-resources/overview).
136+
When you previously enabled customer managed keys this also enabled a system assigned managed identity, a feature of Microsoft Entra ID. Once the system assigned managed identity is enabled, this resource is registered with Microsoft Entra ID. After being registered, the managed identity will be given access to the Key Vault selected during customer managed key setup. You can learn more about [Managed Identities](/azure/active-directory/managed-identities-azure-resources/overview).
137137

138138
> [!IMPORTANT]
139139
> If you disable system assigned managed identities, access to the key vault will be removed and any data encrypted with the customer keys will no longer be accessible. Any features depended on this data will stop working.
140140
141141
> [!IMPORTANT]
142-
> Managed identities do not currently support cross-directory scenarios. When you configure customer-managed keys in the Azure portal, a managed identity is automatically assigned under the covers. If you subsequently move the subscription, resource group, or resource from one Microsoft Entra directory to another, the managed identity associated with the resource is not transferred to the new tenant, so customer-managed keys may no longer work. For more information, see **Transferring a subscription between Microsoft Entra directories** in [FAQs and known issues with managed identities for Azure resources](/azure/active-directory/managed-identities-azure-resources/known-issues#transferring-a-subscription-between-azure-ad-directories).
142+
> Managed identities do not currently support cross-directory scenarios. When you configure customer-managed keys in the Azure portal, a managed identity is automatically assigned under the covers. If you later move the subscription, resource group, or resource from one Microsoft Entra directory to another, the managed identity associated with the resource is not transferred to the new tenant, so customer-managed keys may no longer work. For more information, see **Transferring a subscription between Microsoft Entra directories** in [FAQs and known issues with managed identities for Azure resources](/azure/active-directory/managed-identities-azure-resources/known-issues#transferring-a-subscription-between-azure-ad-directories).
143143
144-
## Next steps
145-
* [Content Safety overview](../overview.md)
144+
## Next step
145+
146+
> [!div class="nextstepaction"]
147+
> [Content Safety overview](../overview.md)

articles/ai-services/content-safety/how-to/migrate-to-general-availability.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: PatrickFarley
66
manager: nitinme
77
ms.service: azure-ai-content-safety
88
ms.topic: conceptual
9-
ms.date: 09/25/2023
9+
ms.date: 01/29/2025
1010
ms.author: pafarley
1111
---
1212

@@ -20,9 +20,9 @@ In all API calls, be sure to change the _api-version_ parameter in your code:
2020

2121
|old | new |
2222
|--|--|
23-
`api-version=2023-04-30-preview` | `api-version=2023-10-01` |
23+
`api-version=2023-04-30-preview` | `api-version=2023-10-01` (or later version) |
2424

25-
Note the following REST endpoint name changes:
25+
Note the following REST endpoint name changes from the preview API:
2626

2727
| Public preview term | GA term |
2828
|-------------------|---------------------------|
@@ -130,6 +130,8 @@ The **blocklistItems** API call with an item ID (retrieve a single item):
130130
```
131131

132132

133-
## Next steps
133+
## Next step
134134

135-
- [Quickstart: Analyze text content](../quickstart-text.md)
135+
136+
> [!div class="nextstepaction"]
137+
> [Quickstart: Analyze text content](../quickstart-text.md)

articles/ai-services/content-safety/quickstart-custom-categories.md

Lines changed: 23 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,21 @@
11
---
22
title: "Quickstart: Custom categories (preview)"
33
titleSuffix: Azure AI services
4-
description: Use the custom categories API to create your own harmful content categories and train the Content Safety model for your use case.
4+
description: Use the custom categories API to create your own content categories and train the Content Safety model for your use case.
55
#services: cognitive-services
66
author: PatrickFarley
77
manager: nitinme
88
ms.service: azure-ai-content-safety
99
ms.topic: quickstart
10-
ms.date: 07/03/2024
10+
ms.date: 01/29/2025
1111
ms.author: pafarley
12+
#customer intent: As a developer, I want to create custom content categories so that I can train the Content Safety model for specific use cases.
1213
---
1314

1415

1516
# Quickstart: Custom categories (standard mode) (preview)
1617

17-
Follow this guide to use Azure AI Content Safety Custom categories (standard) REST API to create your own content categories for your use case and train Azure AI Content Safety to detect them in new text content.
18+
Follow this guide to use Azure AI Content Safety Custom categories (standard) REST API to create your own content categories for your use case and train Azure AI Content Safety to detect them in new text content.
1819

1920
For more information on Custom categories, see the [Custom categories concept page](./concepts/custom-categories.md). For API input limits, see the [Input requirements](./overview.md#input-requirements) section of the Overview.
2021

@@ -45,7 +46,7 @@ To train a custom category, you need example text data that represents the categ
4546
> For tips on creating your own data set, see the [How-to guide](./how-to/custom-categories.md#prepare-your-training-data).
4647
4748
1. Download the [sample text data file](https://github.com/Azure-Samples/cognitive-services-sample-data-files/blob/master/ContentSafety/survival-advice.jsonl) from the GitHub repository.
48-
2. Upload the _.jsonl_ file to your Azure Storage account blob container. Then copy the blob URL to a temporary location for later use.
49+
1. Upload the _.jsonl_ file to your Azure Storage account blob container. Then copy the blob URL to a temporary location for later use.
4950

5051
> [!IMPORTANT]
5152
> **The user's storage account is set up as a hierarchical namespace account, which cannot be supported by Custom Categories. Please try using a regular storage account instead.**
@@ -77,36 +78,30 @@ curl -X PUT "<your_endpoint>/contentsafety/text/categories/<your_category_name>?
7778
> Every time you change your category name, definition or samples,a new version will be created. You can use the version number to trace back to previous versions. Please remember this version number, as it will be required in the URL for the next step- training custom categories.
7879
7980

80-
8181
#### API Request
8282

83-
84-
| Field | Description | Example Value |
85-
|------------------|--------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
86-
| `categoryName` | The name of the category or topic the request relates to. | survival-advice |
87-
| `definition` | A brief description of the content type for the category. | text prompts about survival advice in camping/wilderness situations |
88-
| `sampleBlobUrl` | URL to access a sample JSONL file containing data examples for the category. | Link |
89-
83+
| Field | Description | Example Value |
84+
|--------|--------------|---------------------|
85+
| `categoryName` | The name of the category or topic the request relates to. | survival-advice |
86+
| `definition` | A brief description of the content type for the category. | text prompts about survival advice in camping/wilderness situations |
87+
| `sampleBlobUrl` | URL to access a sample JSONL file containing data examples for the category. | Link |
9088

9189

9290

9391
#### API Response
9492

95-
| Field | Description | Example Value |
96-
|------------------------|--------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
97-
| `categoryName` | The name of the category or topic the response relates to. | survival-advice |
98-
| `definition` | A brief description of the content type for the category. | text prompts about survival advice in camping/wilderness situations |
93+
| Field | Description | Example Value |
94+
|------------------------|---|---------|
95+
| `categoryName` | The name of the category or topic the response relates to. | survival-advice |
96+
| `definition` | A brief description of the content type for the category. | text prompts about survival advice in camping/wilderness situations |
9997
| `sampleBlobUrl` | URL to access a sample JSONL file containing data examples for the category. | Link |
10098
| `sampleBlobSnapshotUrl`| Snapshot URL of the sample JSONL file, which provides access to a specific version of the data. | Snapshot URL |
101-
| `version` | The version number of the category data. | 1 |
102-
| `createdTime` | Timestamp when the category data was created. | 2024-10-28T22:06:59.4626988Z |
103-
| `status` | Current status of the category data processing. | Succeeded |
104-
105-
106-
99+
| `version` | The version number of the category data. | 1 |
100+
| `createdTime` | Timestamp when the category data was created. | 2024-10-28T22:06:59.4626988Z |
101+
| `status` | Current status of the category data processing. | Succeeded |
107102

108103

109-
### Start the category build process:
104+
### Start the category build process
110105

111106
Replace <your_api_key> and <your_endpoint> with your own values, and also **append the version number in the url you obtained from the last step.** Allow enough time for model training: the end-to-end execution of custom category training can take from around five hours to ten hours. Plan your moderation pipeline accordingly. After you receive the response, store the operation ID (referred to as `id`) in a temporary location. This ID will be necessary for retrieving the build status using the **Get status** API in the next section.
112107

@@ -124,7 +119,7 @@ curl -X POST "<your_endpoint>/contentsafety/text/categories/survival-advice:buil
124119
| `status` | Current status of the request | Succeeded |
125120

126121

127-
### Get the category build status:
122+
### Get the category build status
128123

129124
To retrieve the status, utilize the `id` obtained from the previous API response and place it in the path of the API below.
130125

@@ -133,6 +128,7 @@ curl -X GET "<your_endpoint>/contentsafety/text/categories/operations/<id>?api-v
133128
-H "Ocp-Apim-Subscription-Key: <your_api_key>" \
134129
-H "Content-Type: application/json"
135130
```
131+
136132
#### API Response
137133

138134
| Field | Description | Example Value |
@@ -154,6 +150,7 @@ curl -X POST "<your_endpoint>/contentsafety/text:analyzeCustomCategory?api-versi
154150
\"version\": 1
155151
}"
156152
```
153+
157154
#### API Request
158155
| Field | Description |
159156
|----------------|---------------------------------------------------------|
@@ -274,6 +271,7 @@ print(result)
274271
```
275272
---
276273

274+
277275
## Other custom categories operations
278276

279277
Remember to replace the placeholders below with your actual values for the API key, endpoint, and specific content (category name, definition, and so on). These examples help you to manage the customized categories in your account.
@@ -389,5 +387,6 @@ print(result)
389387
---
390388

391389
## Related content
390+
392391
* [Custom categories concepts](./concepts/custom-categories.md)
393392
* [Moderate content with Content Safety](./quickstart-text.md)

articles/ai-services/content-safety/quickstart-protected-material.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,10 @@ author: PatrickFarley
77
manager: nitinme
88
ms.service: azure-ai-content-safety
99
ms.topic: quickstart
10-
ms.date: 10/30/2023
10+
ms.date: 01/29/2025
1111
ms.author: pafarley
12+
#customer intent: As a developer, I want to detect protected material in AI-generated text so that I can ensure compliance with intellectual property laws.
13+
1214
---
1315

1416
# Quickstart: Protected material detection for text
@@ -24,7 +26,6 @@ The key objectives of the Protected Material Detection for Text feature for AI-g
2426
For more information about protected material detection, see the [Protected material detection concept page](./concepts/protected-material.md). For API input limits, see the [Input requirements](./overview.md#input-requirements) section of the Overview.
2527

2628

27-
2829
## Prerequisites
2930

3031
* An Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-services/)

0 commit comments

Comments
 (0)