Skip to content

Commit d66e720

Browse files
Merge pull request #4292 from laujan/424126-rag-updates-3557-tonye
424126 rag updates 3557 tonye
2 parents 51039ad + 321aaf3 commit d66e720

File tree

10 files changed

+1364
-16
lines changed

10 files changed

+1364
-16
lines changed

articles/ai-services/content-understanding/concepts/capabilities.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -156,7 +156,7 @@ Developers using Content Understanding should review Microsoft's policies on cus
156156

157157
## Next steps
158158

159-
* Try processing your document content using Content Understanding in [Azure ](https://ai.azure.com/).
159+
* Try processing your document content using Content Understanding in [**Azure AI Foundry**](https://ai.azure.com/).
160160
* Learn to analyze content [**analyzer templates**](../quickstart/use-ai-foundry.md).
161161
* Review code sample: [**analyzer templates**](https://github.com/Azure-Samples/azure-ai-content-understanding-python/tree/main/analyzer_templates).
162162
* Take a look at our [**glossary**](../glossary.md)

articles/ai-services/content-understanding/concepts/retrieval-augmented-generation.md

Lines changed: 541 additions & 0 deletions
Large diffs are not rendered by default.
170 KB
Loading
156 KB
Loading

articles/ai-services/content-understanding/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Content Understanding offers a streamlined process to reason over large amounts
4141

4242
* **Automation**. Content Understanding supports automation scenarios by converting unstructured content into structured data, which can be integrated into various workflows and applications. Confidence scores minimize human review and lower costs. For example, automate procurement and payment processes by extracting fields from invoices.
4343

44-
* **Search and retrieval augmented generation (RAG)**. Content Understanding enables ingestion of content of any modality into the search index. The structured output representation improves the relevance for RAG scenarios.
44+
* **Search and retrieval-augmented generation (RAG)**. Content Understanding enables ingestion of content of any modality into the search index. The structured output representation improves the relevance for RAG scenarios.
4545

4646
* **Analytics and reporting**: Content Understanding's extracted field outputs enhance analytics and reporting, allowing businesses to gain valuable insights, conduct deeper analysis, and make informed decisions based on accurate reports.
4747

articles/ai-services/content-understanding/toc.yml

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,9 @@ items:
5454
- name: Video
5555
href: video/overview.md
5656
displayName: video, audio, voice, recognition, synthesis, speaker, identification, verification, diarization, transcription, translation, language, understanding, sentiment, analysis, emotion, detection, pronunciation, model
57+
- name: Best practices
58+
displayName: best practices, analyzers, optimization, fields
59+
href: concepts/best-practices.md
5760
- name: Concepts
5861
items:
5962
- name: Best practices
@@ -62,6 +65,14 @@ items:
6265
- name: Accuracy and confidence
6366
displayName: accuracy, confidence, analyzers, optimization, fields, scores
6467
href: concepts/accuracy-confidence.md
68+
- name: Retrieval-augmented generation (RAG)
69+
displayName: RAG, retrieval, augmented, generation, knowledge, base, search, index, vector
70+
href: concepts/retrieval-augmented-generation.md
71+
- name: Tutorials
72+
items:
73+
- name: Build a retrieval-augmented solution
74+
displayName: RAG, retrieval, augmented, generation, knowledge, base, search, index, vector
75+
href: tutorial/build-rag-solution.md
6576
- name: Responsible AI
6677
items:
6778
- name: Transparency note

articles/ai-services/content-understanding/tutorial/build-rag-solution.md

Lines changed: 796 additions & 0 deletions
Large diffs are not rendered by default.

articles/ai-services/document-intelligence/concept/analyze-document-response.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: laujan
66
manager: nitinme
77
ms.service: azure-ai-document-intelligence
88
ms.topic: conceptual
9-
ms.date: 11/19/2024
9+
ms.date: 04/23/2025
1010
ms.author: vikurpad
1111
ms.custom:
1212
- references_regions
@@ -34,7 +34,7 @@ The Document Intelligence APIs analyze images, PDFs, and other document files to
3434
All content elements are grouped according to pages, specified by page number (`1`-indexed). They're also sorted by reading order that arranges semantically contiguous elements together, even if they cross line or column boundaries. When the reading order among paragraphs and other layout elements is ambiguous, the service generally returns the content in a left-to-right, top-to-bottom order.
3535

3636
> [!NOTE]
37-
> Currently, Document Intelligence does not support reading order across page boundaries. Selection marks are not positioned within the surrounding words.
37+
> Currently, Document Intelligence doesn't support reading order across page boundaries. Selection marks aren't positioned within the surrounding words.
3838
3939
The top-level content property contains a concatenation of all content elements in reading order. All elements specify their position in the reader order via spans within this content string. The content of some elements isn't always contiguous.
4040

@@ -71,7 +71,7 @@ Bounding regions describe the visual position of each element in the file. When
7171
:::image type="content" source="../media/bounding-regions.png" alt-text="Screenshot of detected bounding regions example.":::
7272

7373
> [!NOTE]
74-
> Currently, Document Intelligence only returns 4-vertex quadrilaterals as bounding polygons. Future versions may return different number of points to describe more complex shapes, such as curved lines or non-rectangular images. Bounding regions applied only to rendered files, if the file is not rendered, bounding regions are not returned. Currently files of docx/xlsx/pptx/html format are not rendered.
74+
> Currently, Document Intelligence only returns `4-vertex` quadrilaterals as bounding polygons. Future versions may return different number of points to describe more complex shapes, such as curved lines or nonrectangular images. Bounding regions are applied only to rendered files, if the file isn't rendered, bounding regions aren't returned. Currently files of docx/xlsx/pptx/html format aren't rendered.
7575
7676
### Content elements
7777

@@ -107,7 +107,7 @@ Select paragraphs can also be associated with a functional role in the document.
107107
A page is a grouping of content that typically corresponds to one side of a sheet of paper. A rendered page is characterized via width and height in the specified unit. In general, images use pixel while PDFs use inch. The angle property describes the overall text angle in degrees for pages that can be rotated.
108108

109109
> [!NOTE]
110-
> For spreadsheets like Excel, each sheet is mapped to a page. For presentations, like PowerPoint, each slide is mapped to a page. For file formats without a native concept of pages without rendering like HTML or Word documents, the main content of the file is considered a single page.
110+
> For spreadsheets like Excel, each sheet is mapped to a page. For presentations, like PowerPoint, each slide is mapped to a page. For file formats like HTML or Word documents, which lack a native page concept without rendering, the entire main content is treated as a single page.
111111
112112
#### Table
113113

@@ -167,7 +167,7 @@ When *output=figures* is specified during the initial `Analyze` operation, the s
167167

168168
#### Sections
169169

170-
Hierarchical document structure analysis is pivotal in organizing, comprehending, and processing extensive documents. This approach is vital for semantically segmenting long documents to boost comprehension, facilitate navigation, and improve information retrieval. The advent of [Retrieval Augmented Generation (RAG)](../concept/retrieval-augmented-generation.md) in document generative AI underscores the significance of hierarchical document structure analysis. The Layout model supports sections and subsections in the output, which identifies the relationship of sections and object within each section. The hierarchical structure is maintained in `elements` of each section.
170+
Hierarchical document structure analysis is pivotal in organizing, comprehending, and processing extensive documents. This approach is vital for semantically segmenting long documents to boost comprehension, facilitate navigation, and improve information retrieval. The advent of [retrieval-augmented generation (RAG)](../concept/retrieval-augmented-generation.md) in document generative AI underscores the significance of hierarchical document structure analysis. The Layout model supports sections and subsections in the output, which identifies the relationship of sections and object within each section. The hierarchical structure is maintained in `elements` of each section.
171171

172172
```json
173173
{
@@ -221,14 +221,14 @@ A language element describes the detected language for content specified via spa
221221
### Semantic elements
222222

223223
> [!NOTE]
224-
> The semantic elements discussed here apply to Document Intelligence prebuilt models. Your custom models may return different data representations. For example, date and time returned by a custom model may be represented in a pattern that differs from standard ISO 8601 formatting.
224+
> The mentioned semantic elements apply to Document Intelligence prebuilt models. Your custom models may return different data representations. For example, date and time returned by a custom model may be represented in a pattern that differs from standard ISO 8601 formatting.
225225

226226
#### Document
227227

228228
A document is a semantically complete unit. A file can contain multiple documents, such as multiple tax forms within a PDF file, or multiple receipts within a single page. However, the ordering of documents within the file doesn't fundamentally affect the information it conveys.
229229

230230
> [!NOTE]
231-
> Currently, Document Intelligence does not support multiple documents on a single page.
231+
> Currently, Document Intelligence doesn't support multiple documents on a single page.
232232

233233
The document type describes documents sharing a common set of semantic fields, represented by a structured schema, independent of its visual template or layout. For example, all documents of type "receipt" can contain the merchant name, transaction date, and transaction total, although restaurant and hotel receipts often differ in appearance.
234234

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ metadata:
77
ms.service: azure-ai-document-intelligence
88
ms.custom: references_regions
99
ms.topic: faq
10-
ms.date: 01/14/2025
10+
ms.date: 04/23/2025
1111
ms.author: lajanuar
1212
title: Frequently asked questions
1313
summary: |
@@ -56,7 +56,7 @@ sections:
5656
5757
- With Azure AI Document Intelligence and Azure OpenAI combined, you can build an enterprise application to seamlessly interact with your documents using natural language. You can easily find answers, gain valuable insights, and generate new and engaging content from existing documents.
5858
59-
- You can find more details on the [retrieval augmented generation pattern here](concept/retrieval-augmented-generation.md).
59+
- You can find more details on the [retrieval-augmented generation pattern here](concept/retrieval-augmented-generation.md).
6060
6161
- question: |
6262
Can Document Intelligence help with semantic chunking within documents for retrieval-augmented generation?

articles/ai-services/document-intelligence/prebuilt/layout.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: laujan
66
manager: nitinme
77
ms.service: azure-ai-document-intelligence
88
ms.topic: conceptual
9-
ms.date: 03/27/2025
9+
ms.date: 04/23/2025
1010
ms.author: lajanuar
1111
---
1212

@@ -120,7 +120,7 @@ The layout model extracts structural elements from your documents. To follow are
120120
* [**Figures**](#figures)
121121
* [**Sections**](#sections)
122122

123-
Run the sample layout document analysis within [Document Intelligence Studio](https://documentintelligence.ai.azure.com/studio), then navigate to the results tab to access the full JSON output.
123+
Run the sample layout document analysis within [Document Intelligence Studio](https://documentintelligence.ai.azure.com/studio), then navigate to the results tab and access the full JSON output.
124124

125125
:::image type="content" source="../media/studio/json-output-tab.png" alt-text="Screenshot of results JSON output tab in the Document Intelligence Studio.":::
126126

@@ -526,7 +526,7 @@ if result.figures:
526526

527527
### Sections
528528

529-
Hierarchical document structure analysis is pivotal in organizing, comprehending, and processing extensive documents. This approach is vital for semantically segmenting long documents to boost comprehension, facilitate navigation, and improve information retrieval. The advent of [Retrieval Augmented Generation (RAG)](../concept/retrieval-augmented-generation.md) in document generative AI underscores the significance of hierarchical document structure analysis. The Layout model supports sections and subsections in the output, which identifies the relationship of sections and object within each section. The hierarchical structure is maintained in `elements` of each section. You can use [output response to markdown format](#output-response-to-markdown-format) to easily get the sections and subsections in markdown.
529+
Hierarchical document structure analysis is pivotal in organizing, comprehending, and processing extensive documents. This approach is vital for semantically segmenting long documents to boost comprehension, facilitate navigation, and improve information retrieval. The advent of [retrieval-augmented generation (RAG)](../concept/retrieval-augmented-generation.md) in document generative AI underscores the significance of hierarchical document structure analysis. The Layout model supports sections and subsections in the output, which identifies the relationship of sections and object within each section. The hierarchical structure is maintained in `elements` of each section. You can use [output response to markdown format](#output-response-to-markdown-format) to easily get the sections and subsections in markdown.
530530

531531
#### [Sample code](#tab/sample-code)
532532

@@ -681,8 +681,8 @@ After you retrieve you key and endpoint, you can use the following development o
681681
### [REST API](#tab/rest)
682682

683683

684-
* [2023-07-31 GA (v3.1)](/rest/api/aiservices/document-models/analyze-document?view=rest-aiservices-2023-07-31&preserve-view=true&tabs=HTTP)
685-
* [2022-08-31 GA (v3.0)](/rest/api/aiservices/document-models/analyze-document?view=rest-aiservices-v3.0%20(2022-08-31)&preserve-view=true&tabs=HTTP)
684+
* [`2023-07-31` GA (v3.1)](/rest/api/aiservices/document-models/analyze-document?view=rest-aiservices-2023-07-31&preserve-view=true&tabs=HTTP)
685+
* [`2022-08-31` GA (v3.0)](/rest/api/aiservices/document-models/analyze-document?view=rest-aiservices-v3.0%20(2022-08-31)&preserve-view=true&tabs=HTTP)
686686

687687
# [Client libraries](#tab/sdks)
688688

0 commit comments

Comments
 (0)