AI and Machine Learning Document Intelligence

Document analysis operation

A document analysis operation is an asynchronous Document Intelligence request that analyzes a document with a model and returns extracted content, layout, and fields when polling completes.

Source: Microsoft Learn - Document Intelligence analyze document response Reviewed 2026-05-13

Exam trap: Changing production before checking the exact Azure scope, owner, dependency, data sensitivity, and rollback or recovery procedure.
Production check: Can you name the Azure scope, owner, resource ID, dependency, and rollback or recovery path without guessing?

Practice this topic Microsoft Learn

Article details and learning context

Aliases: Analyze operation, analyze document operation, Document Intelligence analysis request, async analysis operation
Difficulty: intermediate
CLI mappings: 5
Last verified: 2026-05-13

Related context No curated learning path mapped yet; use the category trail.

Compare related concepts Search related resources Browse the glossary

Understand the concept

In plain English

Document analysis operation is the asynchronous Document Intelligence request that submits a document for model analysis and returns structured results after polling completes. In Azure, it helps teams turn PDFs, images, and other supported documents into structured outputs that applications can validate, route, store, and review. Plainly, it is a named part of the platform that operators can point to when they need ownership, evidence, and a safe change path. A useful glossary entry should explain where it appears, what it controls, what depends on it, and which signal proves it is healthy.

Why it matters

Document analysis operation matters because a small Azure design choice can shape customer experience, security posture, operational visibility, and incident recovery. When it is shallowly documented, teams may troubleshoot the wrong DNS record, AI endpoint, model, storage container, policy assignment, deployment stack, or monitoring signal while the real dependency remains hidden. In enterprise Azure work, the value is shared language: application, platform, security, data, finance, and operations teams can discuss the same object without guessing. That reduces incident time, improves audit quality, clarifies ownership, and makes production changes safer because failure modes and graph relationships are visible before change. Treat Document analysis operation as production owned when customer traffic, regulated documents, model decisions, name resolution, compliance posture, or release automation depends on it.

Technical context

Technically, Document analysis operation appears in Document Intelligence REST API calls, SDK analyze methods, Operation-Location headers, polling responses, model IDs, result JSON, and batch analysis output containers and interacts with Azure AI Document Intelligence, Azure AI services account, Azure Storage, and Azure Monitor. Configuration is reviewed through model ID, API version, input document location, and polling interval, while operators validate live state through operation status, operation result URL, analyze result JSON, and page count. Scope determines which permissions, logs, API calls, commands, and dependencies matter.

Exam context

Compare with

Document Intelligence model Document field Content Understanding

Where it is used

Where you see it

In REST integrations, a document analysis operation appears when the service returns an Operation-Location URL that clients poll until completion during production review when operators need repeatable evidence.
In application logs, it appears as a submitted analysis request, operation ID, completion status, model ID, page count, and result payload reference during production review.
In batch processing, it appears when many documents are submitted together and results are written to an approved storage container during production review when operators need repeatable evidence.

Common situations

Submit an invoice or claim form for asynchronous extraction.
Poll operation status and store the final analyze result.
Process batches of documents from an approved storage container.

Illustrative Azure scenarios

These examples show how the concept can affect design and operations. They are illustrative scenarios, not customer claims.

Scenario 01 Document analysis operation in action for property insurance Scenario, objectives, solution, measured impact, and takeaway.

Scenario

HarborSure Insurance, a property insurance organization, needed to address claim adjusters waited hours for scanned damage reports to be manually keyed into the claims system. The architecture team used Document analysis operation as the control point for a measurable production improvement.

Goals

Analyze uploaded documents within 5 minutes
Reduce manual data entry by 55 percent
Provide an auditable operation status for each claim

Approach using Document analysis operation

Developers used the Document Intelligence analyze operation from an Azure Function triggered by blob uploads. Each request stored the operation URL, claim ID, model ID, and polling status in a tracking table. Completed results were validated against confidence thresholds before being sent to the claims workflow, while low-confidence fields moved to human review. The team validated Document analysis operation in a lower environment, captured before-and-after evidence, and promoted the change through a controlled release with rollback ownership. Runbooks were updated so support engineers could identify the correct scope, identity, dependency, telemetry signal, and approval record without asking the original implementer. The final design connected governance with day-to-day engineering work, which made the change understandable to security, operations, finance, and application stakeholders.

Potential outcomes

Average intake time fell from 2.8 hours to 4.6 minutes
Manual keying effort dropped 61 percent
Every claim had operation status and result evidence

What to learn

Document analysis operations make document automation reliable because applications can track asynchronous extraction from submission to validated result.

Scenario 02 Document analysis operation in action for shipping and logistics Scenario, objectives, solution, measured impact, and takeaway.

Scenario

MetroPort Logistics, a shipping and logistics organization, needed to address proof-of-delivery PDFs arrived in large evening batches and overwhelmed the operations team. The architecture team used Document analysis operation as the control point for a measurable production improvement.

Goals

Process 20,000 documents per night
Separate failed operations from successful results
Keep storage output under approved retention controls

Approach using Document analysis operation

The team adopted batch document analysis for scanned proof-of-delivery files stored in Blob Storage. A nightly pipeline submitted batches, tracked operation status, and wrote results to a controlled container. Failed files were tagged with reason codes and replayed through a smaller retry queue instead of resubmitting the whole batch. The team validated Document analysis operation in a lower environment, captured before-and-after evidence, and promoted the change through a controlled release with rollback ownership. Runbooks were updated so support engineers could identify the correct scope, identity, dependency, telemetry signal, and approval record without asking the original implementer. The final design connected governance with day-to-day engineering work, which made the change understandable to security, operations, finance, and application stakeholders. The team validated Document analysis operation in a lower environment, captured before-and-after evidence, and promoted the change through a controlled release with rollback ownership.

Potential outcomes

Nightly batch processing completed before the 6 a.m. SLA
Retry volume fell by 47 percent
Operations stopped manually sorting successful and failed documents

What to learn

Batch-aware document analysis operations let teams scale document processing without losing control of failures and evidence.

Scenario 03 Document analysis operation in action for public sector permitting Scenario, objectives, solution, measured impact, and takeaway.

Scenario

CivicWorks County, a public sector permitting organization, needed to address permit applications contained mixed PDFs, images, and scanned attachments that had to be reviewed before routing. The architecture team used Document analysis operation as the control point for a measurable production improvement.

Goals

Extract layout and key fields before routing
Reduce incomplete permit submissions by 30 percent
Expose analysis failures to support staff quickly

Approach using Document analysis operation

Architects integrated the analyze operation with a permit intake portal. The portal submitted each document to the chosen model, polled for completion, and checked required fields before assigning the permit to the correct review queue. Azure Monitor alerts watched operation failures, request volume, and abnormal retry spikes. The team validated Document analysis operation in a lower environment, captured before-and-after evidence, and promoted the change through a controlled release with rollback ownership. Runbooks were updated so support engineers could identify the correct scope, identity, dependency, telemetry signal, and approval record without asking the original implementer. The final design connected governance with day-to-day engineering work, which made the change understandable to security, operations, finance, and application stakeholders. The team validated Document analysis operation in a lower environment, captured before-and-after evidence, and promoted the change through a controlled release with rollback ownership.

Potential outcomes

Incomplete submissions dropped 34 percent
Review queues received structured document summaries
Support identified failed operations within minutes

What to learn

The analyze operation is the bridge between raw documents and workflow decisions that applications can monitor and govern.

Azure CLI

CLI checks for Document analysis operation are useful because they turn portal assumptions into repeatable evidence. Start with read-only commands that show scope, state, owner, permissions, destinations, configuration, metrics, operation status, or drift evidence. Run mutating, security-impacting, or cost-impacting commands only after approval, because the wrong scope can affect production availability, spend, access, or document processing.

Useful for

Submit an invoice or claim form for asynchronous extraction.
Poll operation status and store the final analyze result.
Process batches of documents from an approved storage container.

Before you run a command

Run az account show, confirm tenant and subscription, and verify the signed-in operator has approved read access for the exact Azure scope.
Confirm resource group, resource name, endpoint, environment, owner, data classification, and change record before collecting evidence or modifying production configuration.
Prefer read-only commands first; review any command that changes DNS records, AI resources, keys, private networking, model configuration, policy compliance, or deployment state before running it.

What the output tells you

Whether the target DNS zone, Document Intelligence resource, model, operation, field extraction path, policy result, deployment stack, or monitored resource exists at the expected scope.
Which state, endpoint, record set, model ID, operation result, field confidence, identity assignment, diagnostic route, policy compliance result, or drift signal is visible to the operator.
Whether the issue is wrong scope, stale DNS, missing access, expired keys, unsupported model choice, throttling, weak training data, private endpoint misrouting, or configuration drift.

Mapped commands

Document analysis operation operational checks

direct

az cognitiveservices account show --name <account> --resource-group <resource-group>

az cognitiveservices accountdiscoverAI and Machine Learning

az rest --method GET --url <operation-location-url>

az restdiscoverAI and Machine Learning

az monitor metrics list --resource <document-intelligence-resource-id> --metric Transactions

az monitor metricsdiscoverAI and Machine Learning

az monitor diagnostic-settings list --resource <document-intelligence-resource-id>

az monitor diagnostic-settingsdiscoverAI and Machine Learning

az role assignment list --scope <document-intelligence-resource-id> --output table

az role assignmentdiscoverAI and Machine Learning

Architecture context

Document analysis operation belongs to AI and Machine Learning architecture decisions where identity, monitoring, cost ownership, reliability, and production support need shared evidence.

Security: Security for Document analysis operation starts with least privilege, trusted configuration, and evidence that access matches workload risk. Review endpoint authentication, key or managed identity use, document data exposure, private endpoint access, and diagnostic retention before approving production use. A common failure is assuming that a successful deployment, resolved name, model output, or dashboard proves the configuration is safe. Use Microsoft Entra groups, managed identities, RBAC, private connectivity, diagnostic logging, source-controlled definitions, and approval records where applicable. Keep exceptions ticketed, time-bounded, and owned. For regulated workloads, align the term with classification, retention, break-glass, and incident-response procedures. Remove broad access, stale keys, public endpoints, unreviewed contributors, and undocumented exception paths before Document analysis operation becomes an incident path.
Cost: Cost for Document analysis operation appears through service transactions, analyzed pages, storage use, diagnostic retention, private networking, policy remediation, deployment reruns, support time, and the downstream work triggered by bad configuration. Review pages analyzed, failed retry volume, batch size, diagnostic retention, and manual review reduction before expanding production use. Some costs are direct, such as page analysis, retained logs, storage operations, or duplicated resources; others are indirect, such as failed releases, repeated troubleshooting, emergency rework, and audit remediation. Tag related resources, monitor usage, and separate exploratory work from production. A cost review should connect spend to a real owner and measurable value.
Reliability: Reliability for Document analysis operation depends on repeatable configuration, tested dependencies, and clear failure signals. Watch operation polling, retry behavior, input format support, batch result retention, and downstream queue handling because drift often appears later as unresolved names, failed document processing, missing model results, blocked private endpoints, false compliance evidence, or slow recovery. Use lower environments, source-controlled definitions where possible, deployment validation, monitoring, and rollback notes before changing production. Operators should know which endpoint, DNS path, model, storage dependency, policy, or downstream application fails first and which metric or log proves the failure. The goal is predictable recovery: detect Document analysis operation drift, preserve service, restore safely, and explain the incident without guessing.
Performance: Performance for Document analysis operation depends on workload shape, service limits, data volume, network path, API behavior, diagnostic destination, policy evaluation, and the monitoring path used to confirm success. Review document size, page count, request concurrency, polling cadence, and model selection before increasing capacity or retrying blindly. The better fix might be correcting DNS TTLs, reducing document size, choosing the right model, improving training data, tuning request concurrency, or repairing drift at the source. Measure under representative production conditions. Operators should connect symptoms to evidence: latency, throttling, backlog, failed operations, stale records, low confidence, or noncompliance. Good performance work ties Document analysis operation measurements to user impact and avoids hiding design issues behind larger resources.
Operations: Operations for Document analysis operation should focus on ownership, observability, and safe repeatability. Standardize names, tags, owner groups, environment labels, diagnostic destinations, runbook links, approval records, and change windows so support teams do not reverse-engineer the platform during incidents. Use read-only CLI, API, policy, diagnostic, or portal checks first, then compare live state with intended configuration. For production, connect alerts, audit events, cost records, graph links, and release notes to the same term. The support question should be simple: who owns it, what changed, and what proves the current state?. Capture owner, scope, evidence, and recovery procedure before changing Document analysis operation in a production environment.

Common mistakes

Changing production before checking the exact Azure scope, owner, dependency, data sensitivity, and rollback or recovery procedure.
Treating a portal screenshot as enough evidence when CLI output, activity logs, diagnostics, API responses, and source-controlled configuration are repeatable.
Assuming a familiar name proves the correct resource when tenants, subscriptions, DNS zones, AI resources, models, storage containers, and policies can look similar.