You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cognitive-services/Translator/document-translation/how-to-guides/create-use-glossaries.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ ms.topic: how-to
5
5
manager: nitinme
6
6
ms.author: lajanuar
7
7
author: laujan
8
-
ms.date: 03/14/2023
8
+
ms.date: 03/16/2023
9
9
---
10
10
11
11
# Use glossaries with Document Translation
@@ -20,6 +20,9 @@ A glossary is a list of terms with definitions that you create for the Document
20
20
21
21
## Create, upload, and use a glossary file
22
22
23
+
> [!NOTE]
24
+
> The following example uses an enabled [**system-assigned managed identity**](create-use-managed-identities.md#enable-a-system-assigned-managed-identity) and a [**Storage Blob Data Contributor**](create-use-managed-identities.md#grant-access-to-your-storage-account) role assignment for authentication. For more information, *see*[**Managed identities for Document Translation**](./create-use-managed-identities.md).
25
+
23
26
1.**Create your glossary file.** Create a file in a supported format (preferably tab-separated values) that contains all the terms and phrases you want to use in your translation.
24
27
25
28
To check if your file format is supported, *see*[Get supported glossary formats](../reference/get-supported-glossary-formats.md).
@@ -43,7 +46,7 @@ A glossary is a list of terms with definitions that you create for the Document
43
46
44
47
1.**Specify your glossary in the translation request.** Include the **`glossary URL`**, **`format`**, and **`version`** in your **`POST`** request:
Copy file name to clipboardExpand all lines: articles/cognitive-services/Translator/document-translation/how-to-guides/create-use-managed-identities.md
+12-13Lines changed: 12 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,36 +7,35 @@ manager: nitinme
7
7
ms.service: cognitive-services
8
8
ms.subservice: translator-text
9
9
ms.topic: how-to
10
-
ms.date: 02/09/2023
10
+
ms.date: 03/16/2023
11
11
ms.author: lajanuar
12
12
---
13
13
14
14
# Managed identities for Document Translation
15
15
16
-
:::image type="content" source="../media/managed-identity-rbac-flow.png" alt-text="Screenshot of managed identity flow (RBAC).":::
17
-
18
-
> [!IMPORTANT]
19
-
>
20
-
> * Currently, Document Translation doesn't support managed identity in the global region. If you intend to use managed identities for Document Translation operations, [create your Translator resource](https://portal.azure.com/#create/Microsoft.CognitiveServicesTextTranslation) in a non-global Azure region.
21
-
>
22
-
> * Document Translation is **only** available in the S1 Standard Service Plan (Pay-as-you-go) or in the D3 Volume Discount Plan. _See_[Cognitive Services pricing—Translator](https://azure.microsoft.com/pricing/details/cognitive-services/translator/).
23
-
>
24
-
25
16
Managed identities for Azure resources are service principals that create an Azure Active Directory (Azure AD) identity and specific permissions for Azure managed resources:
26
17
18
+
:::image type="content" source="../media/managed-identity-rbac-flow.png" alt-text="Screenshot of managed identity flow (RBAC).":::
19
+
27
20
* You can use managed identities to grant access to any resource that supports Azure AD authentication, including your own applications. Managed identities eliminate the need for you to include shared access signature tokens (SAS) with your HTTP requests.
28
21
29
22
* To grant access to an Azure resource, assign an Azure role to a managed identity using [Azure role-based access control (`Azure RBAC`)](../../../../role-based-access-control/overview.md).
30
23
31
24
* There's no added cost to use managed identities in Azure.
32
25
33
-
> [!TIP]
26
+
27
+
28
+
29
+
> [!IMPORTANT]
34
30
>
35
31
> * When using managed identities, don't include a SAS token URL with your HTTP requests—your requests will fail.
36
32
>
33
+
> * Currently, Document Translation doesn't support managed identity in the global region. If you intend to use managed identities for Document Translation operations, [create your Translator resource](https://portal.azure.com/#create/Microsoft.CognitiveServicesTextTranslation) in a non-global Azure region.
34
+
>
35
+
> * Document Translation is **only** available in the S1 Standard Service Plan (Pay-as-you-go) or in the D3 Volume Discount Plan. _See_[Cognitive Services pricing—Translator](https://azure.microsoft.com/pricing/details/cognitive-services/translator/).
36
+
>
37
37
> * Managed identities are a safer way to grant access to data without having SAS tokens included with your HTTP requests.
38
38
39
-
40
39
## Prerequisites
41
40
42
41
To get started, you need:
@@ -130,7 +129,7 @@ The **Storage Blob Data Contributor** role gives Translator (represented by the
130
129
131
130
* With managed identity and `Azure RBAC`, you no longer need to include SAS URLs.
132
131
133
-
* If successful, the POST method returns a `202 Accepted`response code and the batch request is created by the service.
132
+
* If successful, the POST method returns a `202 Accepted` response code and the service creates a batch request.
134
133
135
134
* The translated documents appear in your target container.
0 commit comments