merge studio files

Author: laujan

articles/ai-services/.openpublishing.redirection.ai-services.json

@@ -4,6 +4,13 @@
             "source_path_from_root": "/articles/ai-services/computer-vision/how-to/install-sdk.md",
             "redirect_url": "/articles/ai-services/computer-vision/sdk/install-sdk",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/ai-services/document-intelligence/concept-document-intelligence-studio.md",
+            "redirect_url": "/articles/ai-services/document-intelligence/studio-overview",
+            "redirect_document_id": true
         }
+
+
     ]
 }

articles/ai-services/document-intelligence/concept-document-intelligence-studio.md

@@ -30,86 +30,17 @@ monikerRange: '>=doc-intel-3.0.0'
 **This content applies to:** ![checkmark](media/yes-icon.png) **v3.0 (GA)** | **Latest versions:** ![purple-checkmark](media/purple-yes-icon.png) [**v4.0 (preview)**](?view=doc-intel-4.0.0&preserve-view=true) ![purple-checkmark](media/purple-yes-icon.png) [**v3.1**](?view=doc-intel-3.1.0&preserve-view=true)
 ::: moniker-end
 
-> [!IMPORTANT]
->
-> * There are separate URLs for Document Intelligence Studio sovereign cloud regions.
-> * Azure for US Government: [Document Intelligence Studio (Azure Fairfax cloud)](https://formrecognizer.appliedai.azure.us/studio)
-> * Microsoft Azure operated by 21Vianet: [Document Intelligence Studio (Azure in China)](https://formrecognizer.appliedai.azure.cn/studio)
 
-[Document Intelligence Studio](https://documentintelligence.ai.azure.com/) is an online tool for visually exploring, understanding, and integrating features from the Document Intelligence service into your applications. Use the Document Intelligence Studio to:
 
-* Learn more about the different capabilities in Document Intelligence.
-* Use your Document Intelligence resource to test models on sample documents or upload your own documents.
-* Experiment with different add-on and preview features to adapt the output to your needs.
-* Train custom classification models to classify documents.
-* Train custom extraction models to extract fields from documents.
-* Get sample code for the language-specific `SDKs` to integrate into your applications.
 
-Use the [Document Intelligence Studio quickstart](quickstarts/try-document-intelligence-studio.md) to get started analyzing documents with document analysis or prebuilt models. Build custom models and reference the models in your applications using one of the [language specific `SDKs`](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true) and other quickstarts.
 
 ## Getting started
 
 If you're visiting the Studio for the first time, follow the [getting started guide](studio-overview.md#get-started) to set up the Studio for use.
 
-## Analyze options
 
-* Document Intelligence supports sophisticated analysis capabilities. The Studio allows one entry point (Analyze options button) for configuring the add-on capabilities with ease.
-* Depending on the document extraction scenario, configure the analysis range, document page range, optional detection, and premium detection features.
 
-    :::image type="content" source="media/studio/analyze-options.png" alt-text="Screenshot of the analyze-options dialog window.":::
 
-    > [!NOTE]
-    > 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.
-
-✔️ **Auto labeling documents with prebuilt models or one of your own models**
-
-* 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.
-
-    :::image type="content" source="media/studio/auto-label.gif" alt-text="Animated screenshot showing auto labeling in Studio.":::
-
-* For some documents, duplicate labels after running autolabel are possible. Make sure to modify the labels so that there are no duplicate labels in the labeling page afterwards.
-
-    :::image type="content" source="media/studio/duplicate-labels.png" alt-text="Screenshot showing duplicate label warning after auto labeling.":::
-
-✔️ **Auto labeling tables**
-
-* In custom extraction model labeling page, you can now auto label the tables in the document without having to label the tables manually.
-
-    :::image type="content" source="media/studio/auto-table-label.gif" alt-text="Animated screenshot showing auto table labeling in Studio.":::
-
-✔️ **Add test files directly to your training dataset**
-
-* 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.
-
-* 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.
-
-:::image type="content" source="media/studio/add-from-test.gif" alt-text="Animated screenshot showing how to add test files to training dataset.":::
-
-✔️ **Make use of the document list options and filters in custom projects**
-
-* 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.
-
-* Utilize the grid view to preview documents or use the list view to scroll through the documents more easily.
-
-    :::image type="content" source="media/studio/document-options.png" alt-text="Screenshot of document list view options and filters.":::
-
-✔️ **Project sharing**
-
-* Share custom extraction projects with ease. For more information, see [Project sharing with custom models](how-to-guides/project-share-custom-models.md).
-
-## Document Intelligence model support
-
-* **Read**: Try out Document Intelligence's Read feature to extract text lines, words, detected languages, and handwritten style if detected. Start with the [Studio Read feature](https://documentintelligence.ai.azure.com/studio/read). Explore with sample documents and your documents. Use the interactive visualization and JSON output to understand how the feature works. See the [Read overview](concept-read.md) to learn more and get started with the [Python SDK quickstart for Layout](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true).
-
-* **Layout**: Try out Document Intelligence's Layout feature to extract text, tables, selection marks, and structure information. Start with the [Studio Layout feature](https://documentintelligence.ai.azure.com/studio/layout). Explore with sample documents and your documents. Use the interactive visualization and JSON output to understand how the feature works. See the [Layout overview](concept-layout.md) to learn more and get started with the [Python SDK quickstart for Layout](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true#layout-model).
-
-* **Prebuilt models**: Document Intelligence's prebuilt models enable you to add intelligent document processing to your apps and flows without having to train and build your own models. As an example, start with the [Studio Invoice feature](https://documentintelligence.ai.azure.com/studio/prebuilt?formType=invoice). Explore with sample documents and your documents. Use the interactive visualization, extracted fields list, and JSON output to understand how the feature works. See the [Models overview](concept-model-overview.md) to learn more and get started with the [Python SDK quickstart for Prebuilt Invoice](quickstarts/get-started-sdks-rest-api.md?view=doc-intel-3.0.0&preserve-view=true#prebuilt-model).
-
-* **Custom extraction models**: Document Intelligence's custom models enable you to extract fields and values from models trained with your data, tailored to your forms and documents. To extract data from multiple form types, create standalone custom models or combine two, or more, custom models and create a composed model. Start with the [Studio Custom models feature](https://documentintelligence.ai.azure.com/studio/custommodel/projects). Use the help wizard, labeling interface, training step, and visualizations to understand how the feature works. Test the custom model with your sample documents and iterate to improve the model. To learn more, *see* the [Custom models overview](concept-custom.md) to learn more.
-
-* **Custom classification models**: Document classification is a new scenario supported by Document Intelligence. the document classifier API supports classification and splitting scenarios. Train a classification model to identify the different types of documents your application supports. The input file for the classification model can contain multiple documents and classifies each document within an associated page range. To learn more, *see* [custom classification models](concept-custom-classifier.md).
-
-* **Add-on Capabilities**: Document Intelligence now supports more sophisticated analysis capabilities. These optional capabilities can be enabled and disabled in the studio using the `Analze Options` button in each model page. There are four add-on capabilities available: highResolution, formula, font, and barcode extraction capabilities. To learn more, *see* [Add-on capabilities](concept-add-on-capabilities.md).
 
 ## Next steps
 

articles/ai-services/document-intelligence/faq.yml

@@ -146,58 +146,13 @@ sections:
 
           The labeling experience from Document Intelligence Studio is open sourced in the [Toolkit repo](https://github.com/microsoft/Form-Recognizer-Toolkit).
 
-      - question: |
-          Why am I receiving the error "Form Recognizer Not Found" when opening my custom project?
-        answer: |
-          Your Document Intelligence resource bound to this custom project was deleted or moved to another resource group. There are two ways to resolve this problem:
-
-          - Re-create the Document Intelligence resource under the same subscription and resource group with the same name.
-
-          - Re-create a custom project with the migrated Document Intelligence resource and specify the same storage account.
-
-      - question: |
-          Why an I receiving the error "PermissionDenied" when using prebuilt apps or opening my custom project?
-        answer: |
-          If you received error "PermissionDenied: 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.  Please reference [Azure role assignments](quickstarts/try-document-intelligence-studio.md#azure-role-assignments) to configure your access roles.
-
-      - question: |
-          Why an I receiving the error "AuthorizationPermissionMismatch" when opening my custom project?
-        answer: |
-          If you received error "AuthorizationPermissionMismatch: This request is not authorized to perform this operation using this permission" when opening a custom project, it is likely the local (key-based) authentication is disabled for your storage account and your do not have enough permission to access the blob data.  Please reference [Azure role assignments](quickstarts/try-document-intelligence-studio.md#azure-role-assignments-1) to configure your access roles.
-
-      - question: |
-          Why am I not able to sign in to Document Intelligence Studio and keeps seeing InteractionRequiredAuthError error (AADSTS50058)?
-        answer: |
-          If you received error "InteractionRequiredAuthError: login_required: AADSTS50058: A silent sign-request was sent but no user is signed in.", this is due to 3rd-party cookies are blocked by your browser so we cannot successfully sign in your account.
-
-          For **Edge** users, please:
-          - Go to **Settings** for Edge
-          - Search for "**third-party**"
-          - Go to **Manage and delete cookies and site data**
-          - Turn off the setting of **Block third-party cookies**
-
-          For **Chrome** users, please:
-          - Go to **Settings** for Chrome
-          - Search for "**Third-party**"
-          - Under **Default behavior**, select **Allow third-party cookies**
-
-          For **Firefox** users, please:
-          - Go to **Settings** for Firefox
-          - Search for "**cookies**"
-          - Under **Enhanced Tracking Protection**, select **Manage Exceptions**
-          - Add exception for **https://documentintelligence.ai.azure.com** or the Document Intelligence Studio URL of your environment
-
-          For **Safari** users, please:
-          - Choose **Safari** > **Preferences**
-          - Click **Privacy**
-          - Deselect **Block all cookies**
-
-
       - question: |
          Are there separate URL endpoints for Document Intelligence sovereign cloud regions?
         answer: |
 
-          "Yes. Document Intelligence Studio has separate URL endpoints for sovereign cloud regions:"
+          Yes. 
+          
+          "Document Intelligence Studio has separate URL endpoints for sovereign cloud regions:"
 
           - "URL for the Azure US Government cloud (Azure Fairfax): [Document Intelligence Studio US Government](https://formrecognizer.appliedai.azure.us/studio)."
 

articles/ai-services/document-intelligence/quickstarts/try-document-intelligence-studio.md

@@ -24,27 +24,63 @@ monikerRange: '>=doc-intel-3.0.0'
 
 ## Prerequisites for new users
 
+To use Document Intelligence Studio, you need the following assets and settings:
+
 * An active [**Azure account**](https://azure.microsoft.com/free/cognitive-services/). If you don't have one, you can [**create a free account**](https://azure.microsoft.com/free/).
+
 * A [**Document Intelligence**](https://portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer) or [**multi-service**](https://portal.azure.com/#create/Microsoft.CognitiveServicesAllInOne) resource.
 
 > [!TIP]
 > Create an Azure AI services resource if you plan to access multiple Azure AI services under a single endpoint/key. For Document Intelligence access only, create a Document Intelligence resource. Please note that you'll need a single-service resource if you intend to use [Microsoft Entra authentication](../../../active-directory/authentication/overview-authentication.md).
 >
 > Document Intelligence now supports AAD token authentication additional to local (key-based) authentication when accessing the Document Intelligence resources and storage accounts. Be sure to follow below instructions to setup correct access roles, especially if your resources are applied with `DisableLocalAuth` policy.
 
-#### Azure role assignments
+* **Properly scoped Azure role assignments** For document analysis and prebuilt models, following role assignments are required for different scenarios.
 
-For document analysis and prebuilt models, following role assignments are required for different scenarios.
+  * Basic
+    ✔️ **Cognitive Services User**: you need this role to Document Intelligence or Azure AI services resource to enter the analyze page.
 
-* Basic
-  * **Cognitive Services User**: you need this role to Document Intelligence or Azure AI services resource to enter the analyze page.
-* Advanced
-  * **Contributor**: you need this role to create resource group, Document Intelligence service, or Azure AI services resource.
+  * Advanced
+    ✔️ **Contributor**: you need this role to create resource group, Document Intelligence service, or Azure AI services resource.
 
-For more information on authorization, *see* [Document Intelligence Studio authorization policies](../studio-overview.md#authorization-policies).
+    For more information on authorization, *see* [Document Intelligence Studio authorization policies](../studio-overview.md#authorization-policies).
 
-> [!NOTE]
-> If local (key-based) authentication is disabled for your Document Intelligence service resource, be sure to obtain **Cognitive Services User** role and your AAD token will be used to authenticate requests on Document Intelligence Studio.  The **Contributor** role only allows you to list keys but does not give you permission to use the resource when key-access is disabled.
+    > [!NOTE]
+    > If local (key-based) authentication is disabled for your Document Intelligence service resource, be sure to obtain **Cognitive Services User** role and your AAD token will be used to authenticate requests on Document Intelligence Studio.  The **Contributor** role only allows you to list keys but does not give you permission to use the resource when key-access is disabled.
+
+* 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.
+
+* 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.
+
+* Custom models need to be trained on your documents. See [custom models overview](concept-custom.md) for an overview of custom models.
+
+## Authentication
+
+Navigate to the [Document Intelligence Studio](https://formrecognizer.appliedai.azure.com/). If it's your first time logging in, a popup window appears prompting you to configure your service resource. In accordance with your organization's policy, you have one or two options:
+
+* **Microsoft Entra authentication: access by Resource (recommended)**.
+
+  * Choose your existing subscription.
+  * Select an existing resource group within your subscription or create a new one.
+  * Select your existing Document Intelligence or Azure AI services resource.
+
+    :::image type="content" source="media/studio/configure-service-resource.png" alt-text="Screenshot of configure service resource form from the Document Intelligence Studio.":::
+
+* **Local authentication: access by API endpoint and key**.
+
+  * Retrieve your endpoint and key from the Azure portal.
+  * Go to the overview page for your resource and select **Keys and Endpoint** from the left navigation bar.
+  * Enter the values in the appropriate fields.
+
+      :::image type="content" source="media/studio/keys-and-endpoint.png" alt-text="Screenshot of the keys and endpoint page in the Azure portal.":::
+
+* 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.
+
+To learn more about each model, *see* our concept pages.
+
+### View resource details
+
+ To view resource details such as name and pricing tier, select the **Settings** icon in the top-right corner of the Document Intelligence Studio home page and select the **Resource** tab. If you have access to other resources, you can switch resources as well.
 
 ## Models