Skip to content

Commit 654ef79

Browse files
committed
update managed identities articles
1 parent 757fa97 commit 654ef79

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/applied-ai-services/form-recognizer/managed-identities.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -27,10 +27,6 @@ Managed identities for Azure resources are service principals that create an Azu
2727
2828
## Private storage account access
2929

30-
> [!NOTE]
31-
>
32-
> Form Recognizer only supports system-assigned managed identities today. User-assigned managed identities is on the feature road map and will be enabled in the near future.
33-
3430
Private Azure storage account access and authentication are supported by [managed identities for Azure resources](../../active-directory/managed-identities-azure-resources/overview.md). If you have an Azure storage account, protected by a Virtual Network (VNet) or firewall, Form Recognizer can't directly access your storage account data. However, once a managed identity is enabled, Form Recognizer can access your storage account using an assigned managed identity credential.
3531

3632
> [!NOTE]
@@ -64,7 +60,11 @@ To get started, you'll need:
6460

6561
## Managed identity assignments
6662

67-
There are two types of managed identity: **system-assigned** and **user-assigned**. Currently, Form Recognizer is supported by system-assigned managed identity. A system-assigned managed identity is **enabled** directly on a service instance. It isn't enabled by default; you have to go to your resource and update the identity setting. The system-assigned managed identity is tied to your resource throughout its lifecycle. If you delete your resource, the managed identity will be deleted as well.
63+
There are two types of managed identity: **system-assigned** and **user-assigned**. Currently, Form Recognizer supports system-assigned managed identity:
64+
65+
* 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.
66+
67+
* The system-assigned managed identity is tied to your resource throughout its lifecycle. If you delete your resource, the managed identity will be deleted as well.
6868

6969
In the following steps, we'll enable a system-assigned managed identity and grant Form Recognizer limited access to your Azure blob storage account.
7070

articles/cognitive-services/Translator/document-translation/managed-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ To get started, you'll need:
5454

5555
## Managed identity assignments
5656

57-
There are two types of managed identities: **system-assigned** and **user-assigned**. Currently, Document Translation is supports system-assigned managed identities:
57+
There are two types of managed identities: **system-assigned** and **user-assigned**. Currently, Document Translation supports system-assigned managed identities:
5858

5959
* 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.
6060

0 commit comments

Comments
 (0)