Azure Document Intelligence (Repository Option) - Revision history

Dgreenwood: /* Key similarities and differences between DI Analyze and Azure DI OCR */

2026-01-15T17:54:12Z

Key similarities and differences between DI Analyze and Azure DI OCR

← Older revision		Revision as of 12:54, 15 January 2026
Line 41:		Line 41:
	:'''Azure DI OCR'''		:'''Azure DI OCR'''
	:* Focuses on OCR (text recognition) for machine and hand print and layout data collection.		:* Focuses on OCR (text recognition) for machine and hand print and layout data collection.
	:**<li class="fyi-bullet"> Using the <code>prebuilt-read</code> will perform text recognition only. Using the <code>prebuilt-layout</code> model layout data is also collected. ~~Lines, checkboxes~~ and (optionally) barcodes will be saved to the layout data file created by Recognize.		:**<li class="fyi-bullet"> Using the <code>prebuilt-read</code> will perform text recognition only. Using the <code>prebuilt-layout</code> model, layout data is also collected. Checkboxes and (optionally) barcodes will be saved to the layout data file created by Recognize.
	:* Configured as an OCR Engine within Grooper's OCR Profile.		:* Configured as an OCR Engine within Grooper's OCR Profile.
	:* Results can be used with Grooper's Value Extractions (Pattern Match, Labeled OMR, Labeled Value, etc.)		:* Results can be used with Grooper's Value Extractions (Pattern Match, Labeled OMR, Labeled Value, etc.)

Dgreenwood: /* Overview of Azure Document Intelligence in Grooper */

2026-01-15T16:35:37Z

Overview of Azure Document Intelligence in Grooper

← Older revision		Revision as of 11:35, 15 January 2026
Line 5:		Line 5:
	== Overview of Azure Document Intelligence in Grooper ==		== Overview of Azure Document Intelligence in Grooper ==

	Azure Document Intelligence is a cloud service from Microsoft that ~~provides intelligent~~ document ~~processing capabilities, including~~ text extraction, layout analysis, and semantic understanding. Grooper connects to a Document Intelligence service by enabling and configuring the '''Azure Document Intelligence''' Repository Option. This is configured on the Grooper {{IconName\|Root}} Root node and provides connectivity by entering an API key and a resource name.		Azure Document Intelligence is a cloud service from Microsoft that enables optical character recognition (OCR) and document analysis. Grooper's Azure Document Intelligence integration allows organizations to leverage Azure’s advanced machine learning models for raw text extraction, layout and structure analysis, and semantic understanding. A wide variety of document types are supported, including both machine-printed and handwritten content.

			Grooper connects to an Azure Document Intelligence service by enabling and configuring the '''Azure Document Intelligence''' Repository Option. This option is configured on the Grooper {{IconName\|Root}} Root node and provides connectivity by entering an API key and resource name.

	With the '''Azure Document Intelligence''' option added and configured, Grooper leverages the Document Intelligence service in two primary ways:		With the '''Azure Document Intelligence''' option added and configured, Grooper leverages the Document Intelligence service in two primary ways:
	* The '''[[Azure DI OCR]]''' engine - Used for text extraction and layout data collection by the [[Recognize]] activity.		* The '''[[Azure DI OCR]]''' engine – Used for text extraction and layout data collection by the [[Recognize]] activity.
	* The '''[[DI Analyze]]''' activity - Used for comprehensive document analysis that can be leveraged by Grooper's AI-enabled features (including [[AI Extract]]).		* The '''[[DI Analyze]]''' activity – Used for comprehensive document analysis that can be leveraged by Grooper's AI-enabled features (including [[AI Extract]]).
	**<li class="fyi-bullet"> This analysis ~~results in a~~ JSON data ~~file~~ that is used by the '''DI Layout''' ~~Quoting Method~~ when configuring AI-enabled features.		**<li class="fyi-bullet"> This analysis produces JSON data files that are used by the '''DI Layout''' quoting method when configuring AI-enabled features.

	{\|class="fyi-box"		{\| class="fyi-box"
	\|		\|
	'''FYI'''		'''FYI'''
	\|		\|
	'''What if I want to use both DI Analyze and Azure DI OCR? Does that mean the document gets sent to Azure twice?		'''What if I want to use both DI Analyze and Azure DI OCR? Does that mean the document gets sent to Azure twice?'''

	~~Nope~~. ~~You just~~ need to run DI Analyze first.		No. However, you need to run DI Analyze first.

	Running DI Analyze ~~will create~~ a set of JSON files for each document and ~~their~~ child pages. When an OCR Profile uses Azure DI OCR, it ~~will~~ first ~~look to see if one~~ of these files ~~exists~~. If so, ~~it will get~~ the text data from ~~it,~~ rather than making a duplicate call to the Document Intelligence service.		Running DI Analyze generates a set of JSON files for each document and its child pages. When an OCR Profile uses Azure DI OCR, it first checks for the existence of these files. If they are found, Grooper retrieves the text and layout data from the JSON rather than making a duplicate call to the Azure Document Intelligence service.
	\|}		\|}


	=== Key similarities and differences between DI Analyze and Azure DI OCR ===		=== Key similarities and differences between DI Analyze and Azure DI OCR ===

Dgreenwood: /* Adding and configuring the Azure Document Intelligence option */

2026-01-14T21:35:43Z

Adding and configuring the Azure Document Intelligence option

← Older revision		Revision as of 16:35, 14 January 2026
Line 54:		Line 54:
	You '''must''' add the '''Azure Document Intelligence''' option to the Grooper Root before using Azure DI OCR or DI Analyze. These features will not function without it.		You '''must''' add the '''Azure Document Intelligence''' option to the Grooper Root before using Azure DI OCR or DI Analyze. These features will not function without it.

	There are two ~~broad~~ steps to connect Grooper to Azure Document Intelligence.		There are two primary steps required to connect Grooper to Azure Document Intelligence.

			; 1. Create an Azure Document Intelligence resource
			: Azure Document Intelligence is a cloud-based service and must be provisioned in the Azure portal before it can be used by Grooper. Instructions for creating a Document Intelligence resource are available in Microsoft’s [https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/how-to-guides/create-document-intelligence-resource Create a Document Intelligence resource] article.

	~~; 1. Create a Document Intelligence resource in Azure~~
	: Azure Document Intelligence is a cloud-based service. Users must create this service in their Azure portal before connecting it to Grooper. Information on creating a Document Intelligence resource in Azure can be found in Microsoft's [https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/how-to-guides/create-document-intelligence-resource?view=doc-intel-4.0.0 Create a Document Intelligence resource] article.
	; 2. Add and configure an Azure Document Intelligence repository option in Grooper		; 2. Add and configure an Azure Document Intelligence repository option in Grooper
	: ~~With a~~ Document Intelligence resource ~~up and running~~ in Azure, ~~you connect~~ Grooper to it ~~with~~ the Azure Document Intelligence repository option. Configuration is ~~simple. You will need~~ the ~~Document Intelligence service's~~ API key and resource name from ~~your~~ Azure portal.		: Once the Document Intelligence resource is available in Azure, Grooper can be connected to it using the [[Azure Document Intelligence]] repository option. Configuration is straightforward and requires the service’s API key and resource name, both of which can be obtained from the Azure portal.
	: To add and configure the '''Azure Document Intelligence''' option in Grooper:
	:# From the Design page, go to the {{IconName\|Root}} '''Root''' node.		To add and configure the '''Azure Document Intelligence''' option in Grooper:
	:# Open the "'''Options'''" editor (Press the "..." button).		# From the Design page, go to the {{IconName\|Root}} '''Root''' node.
	:# Press the '''Add''' button ({{IconName\|Add}}) and select "'''Azure Document Intelligence'''" from the dropdown.		# Open the "'''Options'''" editor (Press the "..." button).
	:# In the "'''API Key'''" property, enter your Document Intelligence service's API key (from your Azure portal).		# Press the '''Add''' button ({{IconName\|Add}}) and select "'''Azure Document Intelligence'''" from the dropdown.
	:# In the "'''Resource Name'''" property, enter the Document Intelligence service's resource name (from your Azure portal).		# In the "'''API Key'''" property, enter your Document Intelligence service's API key (from your Azure portal).
			# In the "'''Resource Name'''" property, enter the Document Intelligence service's resource name (from your Azure portal).

Dgreenwood: /* Adding and configuring the Azure Document Intelligence option */

2026-01-14T20:22:42Z

Adding and configuring the Azure Document Intelligence option

← Older revision		Revision as of 15:22, 14 January 2026
Line 58:		Line 58:
	; 1. Create a Document Intelligence resource in Azure		; 1. Create a Document Intelligence resource in Azure
	: Azure Document Intelligence is a cloud-based service. Users must create this service in their Azure portal before connecting it to Grooper. Information on creating a Document Intelligence resource in Azure can be found in Microsoft's [https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/how-to-guides/create-document-intelligence-resource?view=doc-intel-4.0.0 Create a Document Intelligence resource] article.		: Azure Document Intelligence is a cloud-based service. Users must create this service in their Azure portal before connecting it to Grooper. Information on creating a Document Intelligence resource in Azure can be found in Microsoft's [https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/how-to-guides/create-document-intelligence-resource?view=doc-intel-4.0.0 Create a Document Intelligence resource] article.
	; 2. Add and configure an Azure Document Intelligence option in Grooper		; 2. Add and configure an Azure Document Intelligence repository option in Grooper
	: With a Document Intelligence up and running in Azure, you connect Grooper to it with the [[Azure Document Intelligence]] repository option. Configuration is simple. You will need the Document Intelligence service's API key and resource name from your Azure portal.		: With a Document Intelligence resource up and running in Azure, you connect Grooper to it with the Azure Document Intelligence repository option. Configuration is simple. You will need the Document Intelligence service's API key and resource name from your Azure portal.
	: To add and configure the '''Azure Document Intelligence''' option in Grooper:		: To add and configure the '''Azure Document Intelligence''' option in Grooper:
	:# From the Design page, go to the {{IconName\|Root}} '''Root''' node.		:# From the Design page, go to the {{IconName\|Root}} '''Root''' node.

Dgreenwood: /* Adding and configuring the Azure Document Intelligence option */

2026-01-14T20:21:38Z

Adding and configuring the Azure Document Intelligence option

← Older revision		Revision as of 15:21, 14 January 2026
Line 54:		Line 54:
	You '''must''' add the '''Azure Document Intelligence''' option to the Grooper Root before using Azure DI OCR or DI Analyze. These features will not function without it.		You '''must''' add the '''Azure Document Intelligence''' option to the Grooper Root before using Azure DI OCR or DI Analyze. These features will not function without it.

	~~Adding~~ and ~~configuring~~ the '''Azure Document Intelligence''' option in Grooper ~~is simple.~~		There are two broad steps to connect Grooper to Azure Document Intelligence.
	# From the Design page, go to the {{IconName\|Root}} '''Root''' node.
	# Open the "'''Options'''" editor (Press the "..." button).		; 1. Create a Document Intelligence resource in Azure
	# Press the '''Add''' button ({{IconName\|Add}}) and select "'''Azure Document Intelligence'''" from the dropdown.		: Azure Document Intelligence is a cloud-based service. Users must create this service in their Azure portal before connecting it to Grooper. Information on creating a Document Intelligence resource in Azure can be found in Microsoft's [https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/how-to-guides/create-document-intelligence-resource?view=doc-intel-4.0.0 Create a Document Intelligence resource] article.
	# In the "'''API Key'''" property, enter your Document Intelligence service's API key (from your Azure portal).		; 2. Add and configure an Azure Document Intelligence option in Grooper
	# In the "'''Resource Name'''" property, enter the Document Intelligence service's resource name (from your Azure portal).		: With a Document Intelligence up and running in Azure, you connect Grooper to it with the [[Azure Document Intelligence]] repository option. Configuration is simple. You will need the Document Intelligence service's API key and resource name from your Azure portal.
			: To add and configure the '''Azure Document Intelligence''' option in Grooper:
			:# From the Design page, go to the {{IconName\|Root}} '''Root''' node.
			:# Open the "'''Options'''" editor (Press the "..." button).
			:# Press the '''Add''' button ({{IconName\|Add}}) and select "'''Azure Document Intelligence'''" from the dropdown.
			:# In the "'''API Key'''" property, enter your Document Intelligence service's API key (from your Azure portal).
			:# In the "'''Resource Name'''" property, enter the Document Intelligence service's resource name (from your Azure portal).

Dgreenwood: /* Overview of Azure Document Intelligence in Grooper */

2025-12-11T16:54:55Z

Overview of Azure Document Intelligence in Grooper

@@ Line 11: / Line 11: @@
 * The '''[[DI Analyze]]''' activity - Used for comprehensive document analysis that can be leveraged by Grooper's AI-enabled features (including [[AI Extract]]).
 **<li class="fyi-bullet"> This analysis results in a JSON data file that is used by the '''DI Layout''' Quoting Method when configuring AI-enabled features.
 === Key similarities and differences between DI Analyze and Azure DI OCR ===

Dgreenwood: Dgreenwood moved page Azure Document Intelligence to Azure Document Intelligence (Repository Option)

2025-12-11T15:39:38Z

Dgreenwood moved page Azure Document Intelligence to Azure Document Intelligence (Repository Option)

← Older revision	Revision as of 10:39, 11 December 2025
(No difference)

Dgreenwood at 15:35, 11 December 2025

2025-12-11T15:35:41Z

@@ Line 1: / Line 1: @@
-Grooper offers robust integration with Microsoft Azure Document Intelligence, enabling advanced cloud-based document analysis and optical character recognition (OCR) for a wide variety of document types. This integration streamlines the extraction of text, layout, and semantic data, supporting both automation and AI-driven workflows.
+{{AutoVersion}}
 == Overview of Azure Document Intelligence in Grooper ==
@@ Line 36: / Line 38: @@
 :* Using the '''DI Layout''' Quoting Method, AI-enabled features can access results in text, markdown and HTML formats.
 :* Results '''cannot''' be used with Grooper's Value Extractions (Pattern Match, Labeled OMR, Labeled Value, etc.).

Dgreenwood: /* Key similarities and differences between DI Analyze and Azure DI OCR */

2025-12-11T15:22:58Z

Key similarities and differences between DI Analyze and Azure DI OCR

← Older revision		Revision as of 10:22, 11 December 2025
Line 19:		Line 19:
	**<li class="attn-bullet"> Be aware, Grooper's current integration with Azure Document Intelligence has focused on using the <code>prebuilt-read</code> and <code>prebuilt-layout</code> models.		**<li class="attn-bullet"> Be aware, Grooper's current integration with Azure Document Intelligence has focused on using the <code>prebuilt-read</code> and <code>prebuilt-layout</code> models.
	* Both can process page images and a Batch Folder's attachment file.		* Both can process page images and a Batch Folder's attachment file.


	<big>Differences</big>		<big>Differences</big>

Dgreenwood: /* Key similarities and differences between DI Analyze and Azure DI OCR */

2025-12-11T15:22:34Z

Key similarities and differences between DI Analyze and Azure DI OCR

← Older revision		Revision as of 10:22, 11 December 2025
Line 12:		Line 12:
	=== Key similarities and differences between DI Analyze and Azure DI OCR ===		=== Key similarities and differences between DI Analyze and Azure DI OCR ===

	Azure DI OCR and DI Analyze have several things in common.		<big>Similarities</big>

			'''Azure DI OCR''' and '''DI Analyze''' have several things in common.
	* Both utilize the Document Intelligence service Grooper connects to using the Azure Document Intelligence option added to the Grooper Root.		* Both utilize the Document Intelligence service Grooper connects to using the Azure Document Intelligence option added to the Grooper Root.
	* Both have access to the same models (although they utilize them differently).		* Both have access to the same models (although they utilize them differently).
Line 18:		Line 20:
	* Both can process page images and a Batch Folder's attachment file.		* Both can process page images and a Batch Folder's attachment file.


			<big>Differences</big>

	While both methods utilize Azure Document Intelligence, they differ in scope, output, and intended use:		While both methods utilize Azure Document Intelligence, they differ in scope, output, and intended use:
			:'''Azure DI OCR'''
	# '''DI Analyze'''		:* Focuses on OCR (text recognition) for machine and hand print and layout data collection.
	#* Performs full document analysis, extracting text, layout, style, and semantic data.		:**<li class="fyi-bullet"> Using the <code>prebuilt-read</code> will perform text recognition only. Using the <code>prebuilt-layout</code> model layout data is also collected. Lines, checkboxes and (optionally) barcodes will be saved to the layout data file created by Recognize.
	#* Enables advanced AI workflows, including LLM prompt injection and "spatial grounding" to improve document highlighting when aligning an LLM's response back to the Grooper document.		:* Configured as an OCR Engine within Grooper's OCR Profile.
	#* When run on the folder level, can be configured to prefer the folder's child pages (default) or attachment file.		:* Results can be used with Grooper's Value Extractions (Pattern Match, Labeled OMR, Labeled Value, etc.)
	#* When run on the folder level, DI layout data is saved to both the folder and its child pages.		:* Aligns Azure OCR results with Grooper's internal OCR engines for enhanced accuracy.
	#* Using the '''DI Layout''' Quoting Method, AI-enabled features can access results in text, markdown and HTML formats.		:'''DI Analyze'''
	#* Results '''cannot''' be used with Grooper's Value Extractions (Pattern Match, Labeled OMR, Labeled Value, etc.).		:* Performs full document analysis, extracting text, layout, style, and semantic data.
	~~# '''Azure DI OCR'''~~		:* Enables advanced AI workflows, including LLM prompt injection and "spatial grounding" to improve document highlighting when aligning an LLM's response back to the Grooper document.
	~~#* Focuses on OCR (text recognition) for machine and hand print and layout data collection.~~		:* When run on the folder level, can be configured to prefer the folder's child pages (default) or attachment file.
	#**<li class="fyi-bullet"> Using the <code>prebuilt-read</code> will perform text recognition only. Using the <code>prebuilt-layout</code> model layout data is also collected. Lines, checkboxes and (optionally) barcodes will be saved to the layout data file created by Recognize.		:* When run on the folder level, DI layout data is saved to both the folder and its child pages.
	~~#* Configured as an OCR Engine within Grooper's OCR Profile.~~		:* Using the '''DI Layout''' Quoting Method, AI-enabled features can access results in text, markdown and HTML formats.
	~~#* Results can be used with Grooper's Value Extractions (Pattern Match, Labeled OMR, Labeled Value, etc.)~~		:* Results '''cannot''' be used with Grooper's Value Extractions (Pattern Match, Labeled OMR, Labeled Value, etc.).
	~~#* Aligns Azure OCR results with Grooper's internal OCR engines for enhanced accuracy~~.