Skip to content

Commit 297e71e

Browse files
committed
update managed identity
1 parent fdb70e1 commit 297e71e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/ai-services/language-service/native-document-support/managed-identities.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,9 @@ ms.date: 11/21/2024
1212

1313
# Managed identities for Language resources
1414

15-
Managed identities for Azure resources are service principals that create a Microsoft Entra identity and specific permissions for Azure managed resources. Managed identities are a safer way to grant access to storage data and replace the requirement for you to include shared access signature tokens (SAS) with your [source and target container URLs](overview.md#create-azure-blob-storage-containers).
15+
Managed identities for Azure resources are service principals that create a Microsoft Entra identity and specific permissions for Azure managed resources. Managed identities are a safer way to grant access to storage data and replace the requirement for you to include shared access signature tokens (SAS) with your source and target container URLs.
1616

17-
:::image type="content" source="media/managed-identity-flow.png" alt-text="Screenshot of managed identity flow (RBAC).":::
17+
:::image type="content" source="media/managed-identity-flow.png" alt-text="Screenshot of managed identity flow (`RBAC`).":::
1818

1919
* You can use managed identities to grant access to any resource that supports Microsoft Entra authentication, including your own applications.
2020

@@ -24,7 +24,7 @@ Managed identities for Azure resources are service principals that create a Micr
2424

2525
> [!IMPORTANT]
2626
>
27-
> * When using managed identities, don't include a SAS token URL with your HTTP requests—your requests will fail. Using managed identities replaces the requirement for you to include shared access signature tokens (SAS) with your [source and target container URLs](overview.md#create-azure-blob-storage-containers).
27+
> * When using managed identities, don't include a SAS token URL with your HTTP requests. Using managed identities replaces the requirement for you to include shared access signature tokens (SAS) with your source and target container URLs.
2828
>
2929
> * To use managed identities for Language operations, you must [create your Language resource](https://ms.portal.azure.com/#create/Microsoft.CognitiveServicesTextAnalytics) in a specific geographic Azure region such as **East US**. If your Language resource region is set to **Global**, then you can't use managed identity authentication. You can, however, still use [Shared Access Signature (SAS) tokens](shared-access-signatures.md).
3030
>
@@ -65,7 +65,7 @@ To get started, you need the following resources:
6565

6666
## Managed identity assignments
6767

68-
There are two types of managed identities: **system-assigned** and **user-assigned**. Currently, Document Translation supports **system-assigned managed identity**:
68+
There are two types of managed identities: **system-assigned** and **user-assigned**. Currently, Document Translation supports **system-assigned managed identity**:
6969

7070
* A system-assigned managed identity is **enabled** directly on a service instance. It isn't enabled by default; you must go to your resource and update the identity setting.
7171

@@ -135,4 +135,4 @@ You must grant the Language resource access to your storage account before it ca
135135
## Next steps
136136

137137
> [!div class="nextstepaction"]
138-
> [Get started with native document support](overview.md#include-native-documents-with-an-http-request)
138+
> [Native document support](overview.md#native-document-support-for-azure-ai-language-preview)

0 commit comments

Comments
 (0)