Skip to content

Commit 875edd1

Browse files
committed
update code sample to reflect managed identity
1 parent 0e8d253 commit 875edd1

File tree

1 file changed

+10
-12
lines changed

1 file changed

+10
-12
lines changed

articles/cognitive-services/Translator/document-translation/how-to-guides/create-use-managed-identities.md

Lines changed: 10 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,6 @@ ms.author: lajanuar
1313

1414
# Managed identities for Document Translation
1515

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-
2516
Managed identities for Azure resources are service principals that create an Azure Active Directory (Azure AD) identity and specific permissions for Azure managed resources:
2617

2718
* 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.
@@ -30,13 +21,20 @@ Managed identities for Azure resources are service principals that create an Azu
3021

3122
* There's no added cost to use managed identities in Azure.
3223

33-
> [!TIP]
24+
**Create a managed identity for storage access**
25+
26+
:::image type="content" source="../media/managed-identity-rbac-flow.png" alt-text="Screenshot of managed identity flow (RBAC).":::
27+
28+
> [!IMPORTANT]
3429
>
3530
> * When using managed identities, don't include a SAS token URL with your HTTP requests—your requests will fail.
3631
>
32+
> * 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.
33+
>
34+
> * 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/).
35+
>
3736
> * Managed identities are a safer way to grant access to data without having SAS tokens included with your HTTP requests.
3837
39-
4038
## Prerequisites
4139

4240
To get started, you need:
@@ -130,7 +128,7 @@ The **Storage Blob Data Contributor** role gives Translator (represented by the
130128

131129
* With managed identity and `Azure RBAC`, you no longer need to include SAS URLs.
132130

133-
* If successful, the POST method returns a `202 Accepted` response code and the batch request is created by the service.
131+
* If successful, the POST method returns a `202 Accepted` response code and the batch request is created by the service.
134132

135133
* The translated documents appear in your target container.
136134

0 commit comments

Comments
 (0)