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
This reference article provides a version-based description of Document Intelligence feature and capability releases, changes, updates, and enhancements.
@@ -120,7 +169,7 @@ This release includes the following updates:
120
169
121
170
### [**JavaScript**](#tab/javascript)
122
171
123
-
***Version 4.1.0-beta.1 (2023-04-11**)
172
+
*Form Recognizer **4.1.0-beta.1 (2023-04-11**)
124
173
***Targets 2023-02-28-preview by default**
125
174
***No breaking changes**
126
175
@@ -134,7 +183,7 @@ This release includes the following updates:
134
183
135
184
### [**Python**](#tab/python)
136
185
137
-
***Version 3.3.0b1 (2023-04-13**)
186
+
*Form Recognizer **3.3.0b1 (2023-04-13**)
138
187
***Targets 2023-02-28-preview by default**
139
188
***No breaking changes**
140
189
@@ -153,11 +202,11 @@ This release includes the following updates:
153
202
This release includes the following updates:
154
203
155
204
> [!IMPORTANT]
156
-
> The `DocumentAnalysisClient` and `DocumentModelAdministrationClient` now target API version v3.0 GA, released 2022-08-31. These clients are no longer supported by API versions 2020-06-30-preview or earlier.
205
+
> The `DocumentAnalysisClient` and `DocumentModelAdministrationClient` now target API v3.0 GA, released 2022-08-31. These clients are no longer supported by APIs 2020-06-30-preview or earlier.
Copy file name to clipboardExpand all lines: articles/ai-services/document-intelligence/faq.yml
+10-4Lines changed: 10 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -447,9 +447,9 @@ sections:
447
447
448
448
- You need an active [Azure account](https://azure.microsoft.com/free/cognitive-services/) and subscription with at least a **Reader** role to access Document Intelligence Studio.
449
449
450
-
- For **document analysis and prebuilt models**, you need full access—**Contributor** role—to at least one [Document Intelligence](https://portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer) or [multi-service](https://portal.azure.com/#create/Microsoft.CognitiveServicesAllInOne) resource to enter the analyze page. Once you access the model analyze page, you can change the endpoint and key to access other resources, if needed.
450
+
- For **document analysis and prebuilt models**, you need full access—**Cognitive Services User** role—to at least one [Document Intelligence](https://portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer) or [multi-service](https://portal.azure.com/#create/Microsoft.CognitiveServicesAllInOne) resource to enter the analyze page. Once you access the model analyze page, you can change the endpoint and key to access other resources, if needed.
451
451
452
-
- For **custom models**, you can either use a **Contributor** role, or use the endpoint and key of a [Document Intelligence](https://portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer) or [multi-service](https://portal.azure.com/#create/Microsoft.CognitiveServicesAllInOne) resource to create a project. You also need to have **Contributor** role to access to at least one blob storage account.
452
+
- For **custom models**, you can either use a **Cognitive Services User** role, or use the endpoint and key of a [Document Intelligence](https://portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer) or [multi-service](https://portal.azure.com/#create/Microsoft.CognitiveServicesAllInOne) resource to create a project. You also need to have **Storage Blob Data Contributor** role to access to at least one blob storage account.
453
453
454
454
- For more information, *see* [Microsoft Entra built-in roles](../../role-based-access-control/built-in-roles.md).
455
455
@@ -468,10 +468,16 @@ sections:
468
468
- Switching subscriptions or resources can be done under Settings -> Resource tab.
469
469
470
470
- question: |
471
-
Why am I receiving an AuthorizationFailure error on Project Sharing, Auto Label, or OCR Upgrade when my Document Intelligence or Storage Account resource is configured with a firewall?
471
+
Why am I receiving a Storage error on Project Sharing, Auto Label, or OCR Upgrade when my Storage Account resource is configured with a firewall or virtual network?
472
472
answer: |
473
473
474
-
Add our website IP address, 20.3.165.95, to the firewall allowlist for both Document Intelligence and Storage Account resources. This unique address is Document Intelligence Studio's dedicated IP address and can be safely allowed.
474
+
Please refer to [Managed identities for Document Intelligence](managed-identities.md) to set up up your Azure resources.
475
+
476
+
- question: |
477
+
Why am I receiving 'Access denied due to Virtual Network/Firewall rules' on Auto Label or OCR Upgrading when my Document Intelligence resource is configured with a firewall or virtual network?
478
+
answer: |
479
+
480
+
Add our website IP address, 20.3.165.95, to the firewall allowlist for Document Intelligence resource. This is Document Intelligence Studio's dedicated IP address and can be safely allowed.
475
481
476
482
- question: |
477
483
Can I reuse or customize the labeling experience from Studio and build it into my own application?
Copy file name to clipboardExpand all lines: articles/ai-services/document-intelligence/managed-identities.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,7 @@ In the following steps, we enable a system-assigned managed identity and grant D
95
95
96
96
## Grant access to your storage account
97
97
98
-
You need to grant Document Intelligence access to your storage account before it can create, read, or delete blobs. Now that you've enabled Document Intelligence with a system-assigned managed identity, you can use Azure role-based access control (Azure RBAC), to give Document Intelligence access to Azure storage. The **Storage Blob Data Reader** role gives Document Intelligence (represented by the system-assigned managed identity) read and list access to the blob container and data.
98
+
You need to grant Document Intelligence access to your storage account before it can read blobs. Now that you've enabled Document Intelligence with a system-assigned managed identity, you can use Azure role-based access control (Azure RBAC), to give Document Intelligence access to Azure storage. The **Storage Blob Data Reader** role gives Document Intelligence (represented by the system-assigned managed identity) read and list access to the blob container and data.
99
99
100
100
1. Under **Permissions** select **Azure role assignments**:
101
101
@@ -130,6 +130,10 @@ You need to grant Document Intelligence access to your storage account before it
130
130
131
131
That's it! You've completed the steps to enable a system-assigned managed identity. With managed identity and Azure RBAC, you granted Document Intelligence specific access rights to your storage resource without having to manage credentials such as SAS tokens.
132
132
133
+
### Additional role assignment for Document Intelligence Studio
134
+
135
+
If you are going to use Document Intelligence Studio and your storage account is configured with network restriction such as firewall or virtual network, an additional role, **Storage Blob Data Contributor**, needs to be assigned to your Document Intelligence service. Document Intelligence Studio requires this role to write blobs to your storage account when you perform Auto label, OCR upgrade, Human in the loop, or Project sharing operations.
136
+
133
137
## Next steps
134
138
> [!div class="nextstepaction"]
135
139
> [Configure secure access with managed identities and private endpoints](managed-identities-secured-access.md)
0 commit comments