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/ai-services/language-service/native-document-support/managed-identities.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,9 @@ ms.date: 11/21/2024
12
12
13
13
# Managed identities for Language resources
14
14
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.
16
16
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`).":::
18
18
19
19
* You can use managed identities to grant access to any resource that supports Microsoft Entra authentication, including your own applications.
20
20
@@ -24,7 +24,7 @@ Managed identities for Azure resources are service principals that create a Micr
24
24
25
25
> [!IMPORTANT]
26
26
>
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.
28
28
>
29
29
> * 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).
30
30
>
@@ -65,7 +65,7 @@ To get started, you need the following resources:
65
65
66
66
## Managed identity assignments
67
67
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**:
69
69
70
70
* 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.
71
71
@@ -135,4 +135,4 @@ You must grant the Language resource access to your storage account before it ca
135
135
## Next steps
136
136
137
137
> [!div class="nextstepaction"]
138
-
> [Get started with native document support](overview.md#include-native-documents-with-an-http-request)
0 commit comments