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/document-intelligence/studio-overview.md
+19-16Lines changed: 19 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,10 @@ Your organization can opt to disable local authentication and enforce Microsoft
58
58
***Designating role assignments**. Document Intelligence Studio basic access requires the [`Cognitive Services User`](../../role-based-access-control/built-in-roles/ai-machine-learning.md#cognitive-services-user) role. For more information, *see*[Document Intelligence role assignments](quickstarts/try-document-intelligence-studio.md#azure-role-assignments).
59
59
60
60
> [!IMPORTANT]
61
-
> Make sure you have the Cognitive Services User role, and not the Cognitive Services Contributor role when setting up Entra authentication. In Azure concept, Contributor role can only perform actions to control and manage the resource itself, including listing the access keys. Any user accounts with "Contributor" role that is able to access the Document Intelligence service is calling with access keys. However, when setting up access with Entra ID, key-access will be disabled and Cognitive Service User role will be required for an account to use the resources.
61
+
>
62
+
> * Make sure you have the **Cognitive Services User role**, and not the Cognitive Services Contributor role when setting up Entra authentication.
63
+
> * In Azure context, Contributor role can only perform actions to control and manage the resource itself, including listing the access keys.
64
+
> * User accounts with a Contributor are only able to access the Document Intelligence service by calling with access keys. However, when setting up access with Entra ID, key-access will be disabled and **Cognitive Service User** role will be required for an account to use the resources.
62
65
63
66
## Document Intelligence model support
64
67
@@ -78,13 +81,13 @@ Use the help wizard, labeling interface, training step, and interactive visualiz
78
81
79
82
## Try a Document Intelligence model
80
83
81
-
1. Once your resource is configured, you can try the different models offered by Document Intelligence Studio. From the front page, select any Document Intelligence model to try using with a no-code approach.
84
+
* Once your resource is configured, you can try the different models offered by Document Intelligence Studio. From the front page, select any Document Intelligence model to try using with a no-code approach.
82
85
83
-
1. To test any of the document analysis or prebuilt models, select the model and use one of the sample documents or upload your own document to analyze. The analysis result is displayed at the right in the content-result-code window.
86
+
* To test any of the document analysis or prebuilt models, select the model and use one of the sample documents or upload your own document to analyze. The analysis result is displayed at the right in the content-result-code window.
84
87
85
-
1. Custom models need to be trained on your documents. See [custom models overview](concept-custom.md) for an overview of custom models.
88
+
* Custom models need to be trained on your documents. See [custom models overview](concept-custom.md) for an overview of custom models.
86
89
87
-
1. After validating the scenario in the Document Intelligence Studio, use the [**C#**](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true), [**Java**](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true), [**JavaScript**](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true), or [**Python**](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true) client libraries or the [**REST API**](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true) to get started incorporating Document Intelligence models into your own applications.
90
+
* After validating the scenario in the Document Intelligence Studio, use the [**C#**](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true), [**Java**](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true), [**JavaScript**](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true), or [**Python**](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true) client libraries or the [**REST API**](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true) to get started incorporating Document Intelligence models into your own applications.
88
91
89
92
To learn more about each model, *see* our concept pages.
90
93
@@ -106,7 +109,7 @@ With Document Intelligence, you can quickly automate your data processing in app
106
109
> [!NOTE]
107
110
> Font extraction is not visualized in Document Intelligence Studio. However, you can check the styles section of the JSON output for the font detection results.
108
111
109
-
✔️ **Auto labeling documents with prebuilt models or one of your own models**
112
+
### Auto label documents with prebuilt models or one of your own models
110
113
111
114
* In custom extraction model labeling page, you can now auto label your documents using one of Document Intelligent Service prebuilt models or your trained models.
112
115
@@ -116,40 +119,40 @@ With Document Intelligence, you can quickly automate your data processing in app
116
119
117
120
:::image type="content" source="media/studio/duplicate-labels.png" alt-text="Screenshot showing duplicate label warning after auto labeling.":::
118
121
119
-
✔️ **Auto labeling tables**
122
+
### Auto label tables
120
123
121
124
* In custom extraction model labeling page, you can now auto label the tables in the document without having to label the tables manually.
122
125
123
126
:::image type="content" source="media/studio/auto-table-label.gif" alt-text="Animated screenshot showing auto table labeling in Studio.":::
124
127
125
-
✔️ **Add test files directly to your training dataset**
128
+
### Add test files directly to your training dataset
126
129
127
130
* Once you train a custom extraction model, make use of the test page to improve your model quality by uploading test documents to training dataset if needed.
128
131
129
132
* If a low confidence score is returned for some labels, make sure they're correctly labeled. If not, add them to the training dataset and relabel to improve the model quality.
130
133
131
-
:::image type="content" source="media/studio/add-from-test.gif" alt-text="Animated screenshot showing how to add test files to training dataset.":::
134
+
:::image type="content" source="media/studio/add-from-test.gif" alt-text="Animated screenshot showing how to add test files to training dataset.":::
132
135
133
-
✔️ **Make use of the document list options and filters in custom projects**
136
+
### Make use of the document list options and filters in custom projects
134
137
135
138
* Use the custom extraction model labeling page to navigate through your training documents with ease by making use of the search, filter, and sort by feature.
136
139
137
140
* Utilize the grid view to preview documents or use the list view to scroll through the documents more easily.
138
141
139
142
:::image type="content" source="media/studio/document-options.png" alt-text="Screenshot of document list view options and filters.":::
140
143
141
-
✔️ **Project sharing**
144
+
### Project sharing
142
145
143
-
*Share custom extraction projects with ease. For more information, see [Project sharing with custom models](how-to-guides/project-share-custom-models.md).
146
+
Share custom extraction projects with ease. For more information, see [Project sharing with custom models](how-to-guides/project-share-custom-models.md).
144
147
145
148
## Troubleshooting
146
149
147
150
|Scenario |Cause| Resolution|
148
151
|-------------|------|----------|
149
-
|You receive the error message `Form Recognizer Not Found` when opening a custom project.|Your Document Intelligence resource, bound to the custom project was deleted or moved to another resource group.| There are two ways to resolve this problem: </br>• Re-create the Document Intelligence resource under the same subscription and resource group with the same name.</br>• Re-create a custom project with the migrated Document Intelligence resource and specify the same storage account.|
150
-
|You receive the error message `PermissionDenied` when using prebuilt apps or opening a custom project.|The principal does not have access to API/Operation" when analyzing against prebuilt models or opening a custom project, it is likely the local (key-based) authentication is disabled for your Document Intelligence resource and your do not have enough permission to access the resource.|Reference [Azure role assignments](quickstarts/try-document-intelligence-studio.md#azure-role-assignments) to configure your access roles.|
151
-
|You receive the error message `AuthorizationPermissionMismatch` when opening a custom project.|The request is not authorized to perform the operation using the designated permission.It is likely the local (key-based) authentication is disabled for your storage account and your do not have the granted permission to access the blob data.|Reference [Azure role assignments](quickstarts/try-document-intelligence-studio.md#azure-role-assignments) to configure your access roles.|
152
-
|You cannot sign in to Document Intelligence Studio and receive the error message `InteractionRequiredAuthError:login_required:AADSTS50058:A silent sign-request was sent but no user is signed in`|It is likely that third-party cookies are blocked by your browser so you cannot successfully sign in.|To resolve, see [Manage third-party settings](#manage-third-party-settings-for-studio-access) for your browser.|
152
+
|You receive the error message</br>`Form Recognizer Not Found` when opening a custom project.|Your Document Intelligence resource, bound to the custom project was deleted or moved to another resource group.| There are two ways to resolve this problem: </br>• Re-create the Document Intelligence resource under the same subscription and resource group with the same name.</br>• Re-create a custom project with the migrated Document Intelligence resource and specify the same storage account.|
153
+
|You receive the error message</br>`PermissionDenied` when using prebuilt apps or opening a custom project.|The principal does not have access to API/Operation" when analyzing against prebuilt models or opening a custom project, it is likely the local (key-based) authentication is disabled for your Document Intelligence resource and your do not have enough permission to access the resource.|Reference [Azure role assignments](quickstarts/try-document-intelligence-studio.md#azure-role-assignments) to configure your access roles.|
154
+
|You receive the error message</br>`AuthorizationPermissionMismatch` when opening a custom project.|The request is not authorized to perform the operation using the designated permission.It is likely the local (key-based) authentication is disabled for your storage account and your do not have the granted permission to access the blob data.|Reference [Azure role assignments](quickstarts/try-document-intelligence-studio.md#azure-role-assignments) to configure your access roles.|
155
+
|You cannot sign in to Document Intelligence Studio and receive the error message</br>`InteractionRequiredAuthError:login_required:AADSTS50058:A silent sign-request was sent but no user is signed in`|It is likely that third-party cookies are blocked by your browser so you cannot successfully sign in.|To resolve, see [Manage third-party settings](#manage-third-party-settings-for-studio-access) for your browser.|
0 commit comments