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: microsoft-365/syntex/document-understanding-overview.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,12 +39,12 @@ Use the unstructured document processing model ([teaching method](create-syntex-
39
39
40
40
## Introduction to unstructured models
41
41
42
-
The unstructured document processing model uses artificial intelligence (AI) to process documents. These documents must have text that can be identified based on phrases or patterns. The identified text designates both the type of file it is (its classification) and what you'd like to extract (its extractors).
42
+
Unstructured document processing models use artificial intelligence (AI) to analyze and extract information from documents. These models rely on identifiable text—based on phrases or patterns—to determine both the document’s classification and the data to extract.
43
43
44
44
> [!NOTE]
45
45
> For more information about how to use Syntex and scenario examples, see [Get started driving adoption of Microsoft Syntex](./adoption-getstarted.md) and [Scenarios and use cases for Microsoft Syntex](./adoption-scenarios.md).
46
46
47
-
Unstructured document processing models are created and managed in a type of SharePoint site called a [content center](create-a-content-center.md). When applied to a SharePoint document library, the model is associated with a content type has columns to store the information being extracted. The content type you create is stored in the SharePoint content type gallery. You can also choose to use existing content types to use their schema.
47
+
You create and manage unstructured document processing models in a SharePoint content center. When you apply a model to a SharePoint document library, it’s associated with a content type that includes columns for storing extracted information. You can create a new content type or use an existing one from the SharePoint content type gallery.
48
48
49
49
> [!NOTE]
50
50
> Read-only or sealed content types can't be updated, so they can't be used in a model.
@@ -55,7 +55,7 @@ Add [classifiers](create-a-classifier.md) and [extractors](create-an-extractor.m
55
55
56
56
- Extractors pull information from these documents. For example, for each contract renewal document identified in your document library, columns display that show the *Service Start Date* and *Client* for each document.
57
57
58
-
You can use example files to train and test your classifiers and extractors in your model. Example files provide your model examples of what to look for when trying to identify and extract data from files. For example, you would train your contract renewal classifiers and extractors with examples of contract renewal documents your company works with. You can also use example files to test the effectiveness of your model.
58
+
Use example files to train and test your classifiers and extractors. These files help the model learn what to look for when identifying and extracting data. For example, train your contract renewal model using real contract renewal documents from your organization. You can also use these files to validate your model’s accuracy.
59
59
60
60
After publishing your model, use the content center to apply it to any SharePoint document library that you have access to.
Copy file name to clipboardExpand all lines: microsoft-365/syntex/form-processing-overview.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ ms.author: chucked
4
4
author: chuckedmonson
5
5
manager: jtremper
6
6
ms.reviewer: ssquires
7
-
ms.date: 01/22/2025
7
+
ms.date: 03/22/2025
8
8
audience: admin
9
9
ms.topic: concept-article
10
10
ms.custom: intro-overview
@@ -38,28 +38,26 @@ Use the freeform document processing model ([freeform selection method](create-s
38
38
39
39
## Introduction to structured and freeform models
40
40
41
-
Microsoft Syntex uses Microsoft Power Apps [AI Builder](/ai-builder/form-processing-model-overview) document processing to create structured and freeform document processing models within SharePoint document libraries.
You can use AI Builder document processing to create structured or freeform document processing models that use machine learning technology to identify and extract key-value pairs and table data from structured or semi-structured documents, such as forms and invoices, and unstructured or freeform documents, such as contracts and correspondence.
41
+
Microsoft Syntex uses Microsoft Power Apps [AI Builder](/ai-builder/form-processing-model-overview) to enable both structured and freeform document processing directly within SharePoint document libraries.
46
42
47
-
Organizations often receive invoices in large quantities from various sources, such as mail, fax, and email. Processing these documents and manually entering them into a database can take a considerable amount of time. By using AI to extract the text, key-value pairs, and tables from your documents, Syntex automates this process.
43
+
With AI Builder, you can create models that use machine learning to identify and extract key-value pairs and table data from various document types—including structured or semi-structured formats like forms and invoices, as well as unstructured formats like contracts and correspondence.
44
+
45
+
For example, organizations often receive large volumes of invoices through mail, fax, or email. Manually processing and entering this data can be time-consuming. Syntex streamlines this process by using AI to extract text, key-value pairs, and tables—automating data capture and reducing manual effort.
48
46
49
47
> [!NOTE]
50
48
> For more ideas about how to use these models in your organization, see [Get started driving adoption](adoption-getstarted.md) and [Scenarios and use cases](adoption-scenarios.md).
51
49
52
-
For example, you can create a structured or freeform document processing model that identifies all documents that are uploaded to the document library. From each document, you can then extract and display specific data that is important to you.
50
+
You can create structured or freeform document processing models that automatically identify and extract important information from files uploaded to a SharePoint document library.
53
51
54
52

55
53
56
-
You use example files to train your model and define the information to be extracted from your form. The layout of your document is learned by training your model. You only need five form documents to get started. Syntex analyzes your example files for key-value pairs, and you can also manually identify ones that might not have been detected. AI builder lets you test the accuracy of your model on your example files.
54
+
To get started, you use example files to train your model. Microsoft Syntex uses these examples to learn the layout of your documents and identify key-value pairs and tables. You only need five sample documents to begin. During training, you can review and manually tag any fields that weren’t automatically detected. AI Builder also lets you test your model’s accuracy using your example files.
57
55
58
-
You can only create a structured or freeform document processing model in SharePoint document libraries for which it's enabled. If it's been enabled, you're able to see the **Classify and extract** option in your document library.
56
+
You can only create document processing models in SharePoint libraries where Syntex has been enabled. If it’s available, yousee the **Classify and extract** option in the library’s command bar.
59
57
60
58

61
59
62
-
If you need it enabled on your document library, contact your Microsoft 365 admin.
60
+
If you don’t see this option, contact your Microsoft 365 admin to enable Microsoft Syntex for your library.
Copy file name to clipboardExpand all lines: microsoft-365/syntex/prebuilt-overview.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ ms.author: chucked
4
4
author: chuckedmonson
5
5
manager: jtremper
6
6
ms.reviewer: ssquires
7
-
ms.date: 01/22/2025
7
+
ms.date: 03/22/2025
8
8
audience: admin
9
9
ms.topic: concept-article
10
10
ms.custom: intro-overview
@@ -23,20 +23,20 @@ description: Learn about prebuilt document processing in SharePoint.
23
23
> [!NOTE]
24
24
> Through June 2025, you can try out a [limited amount](promo-syntex.md#monthly-included-capacity) of prebuilt document processing and other selected content services at no cost if you have [pay-as-you-go billing](syntex-azure-billing.md) set up. For information and limitations, see [Try out pay-as-you-go services](promo-syntex.md).
25
25
26
-
In addition to [custom models](model-types-overview.md#custom-models), Microsoft Syntex provides *prebuilt models* to automate the extraction of information.
26
+
In addition to using [custom models](model-types-overview.md#custom-models), Microsoft Syntex offers prebuilt models that help automate information extraction from documents—no training required. These models are ready to use and designed to recognize common document types and data patterns, so you can get started quickly and scale efficiently.
27
27
28
28
> [!NOTE]
29
29
> Microsoft respects the privacy and ownership of data you use to train and process models in Syntex. None of your organization's data is used or transferred by Microsoft to train AI models, large-language models, or any other models. Your data remains securely within your organization’s tenant. For more information, see [Microsoft data protection and privacy](https://www.microsoft.com/en-us/trust-center/privacy).
30
30
31
31
## Introduction to prebuilt models
32
32
33
-
Prebuilt document processing uses [prebuilt models](#available-prebuilt-models) that are preconfigured to recognize documents and the structured information in the documents. Instead of having to create a new custom model from scratch, you can iterate on an existing pretrained model to add specific fields that fit the needs of your organization.
33
+
Prebuilt document processing uses pretrained models that are already configured to recognize common document types and extract structured information. Instead of building a custom model from scratch, you can start with a prebuilt model and tailor it by adding fields specific to your organization’s needs.
34
34
35
-
Prebuilt models use optical character recognition (OCR) combined with deep learning models to identify and extract predefined text and data fields common to specific document types. You start by analyzing one of your files against the prebuilt model. You then select the detected fields that make sense for your purpose. If the model doesn't detect the fields that you need, you can analyze again by using a different file.
35
+
These models combine optical character recognition (OCR) with deep learning to identify and extract predefined text and data fields. To get started, analyze a sample file using a prebuilt model. Then, select the fields that are relevant to your scenario. If the model doesn’t detect the fields you need, try analyzing a different file.
36
36
37
-
Like other models, prebuilt models are created and managed in the [content center](create-a-content-center.md). When applied to a SharePoint document library, the model is associated with a content type and has columns to store the information being extracted.
37
+
Like other models, prebuilt models are created and managed in the [content center](create-a-content-center.md). When you apply a model to a SharePoint document library, it links to a content type and includes columns to store the extracted information.
38
38
39
-
After publishing your model, use the content center to apply it to any SharePoint document library that you have access to.
39
+
After publishing your model, use the content center to apply it to any SharePoint document library you have access to.
0 commit comments