Azure Content Understanding

azureAI serviceazure-content-understanding

Analyzers that extract a user-defined structured schema from documents, images, audio and video.

Provider
azure
Category
Compute
Properties · 6 set by this component
propertytypevaluesrequiredkind defaultthis component
analyzerType · component propertyenumprebuilt | customnoprebuiltinherited
authenumapi-key | oauth | iam | noneno—▸ api-key
confidenceScores · component propertyboolean—nofalseinherited
contentFilteringboolean—no—▸ true
customerManagedKeysboolean—no—▸ false
dataResidency · advancedenumus | eu | asia | globalno—inherited
dataRetentionDaysinteger—no—inherited
inputModality · component propertyenumdocument | image | audio | videono—inherited
keyStoreboolean—nofalseinherited
managedboolean—nofalse▸ true
modalityenumtext | vision | speech | multimodal | structured | image | video | audio | embedding | rerankno—▸ multimodal
publicEndpointboolean—no—▸ true
quotaUnitsPerMinuteinteger—no—inherited
rateLimitRpm · advancedinteger—no—inherited
rateLimitTpm · advancedinteger—no—inherited
segmentation · component propertyboolean—nofalseinherited
viaGatewayboolean—nofalseinherited
Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

ai-api-key-unmanaged

This AI vendor is reached with an API key, and nothing in the design holds or rotates that key. It ends up in environment files or code, every caller shares it, and a single leak runs up the vendor bill until someone notices. Put the key in a key-management component, or say it is held there with keyStore.

  • — all of these hold:
  • — the node's `auth` is "api-key"
  • — the node's `keyStore` is false
  • — the node has at least one incoming edge from an app-server, worker or client
  • — this does not hold:
  • — the design contains a node of kind key-management
stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

  • — all of these hold:
  • — the node's `stateless` is false
  • — the node sits inside exactly 1 availability-zone group
  • — this does not hold:
  • — the node sits inside at least one cell group
Use it in a design
nodes:
  - { id: "content-understanding", component: "azure-content-understanding" }
Other AI service products · 125
Content Moderationalibaba-content-moderationalibabacloudai-serviceFraud Detectionalibaba-fraud-detectionalibabacloudai-serviceID Verificationalibaba-id-verificationalibabacloudai-serviceIntelligent Robotalibaba-intelligent-robotalibabacloudai-serviceModel Studioalibaba-model-studioalibabacloudai-serviceSmart Conversation Analysisalibaba-smart-conversation-analysisalibabacloudai-serviceAmazon Bedrockaws-bedrockawsai-serviceAmazon Bedrock AgentCoreaws-bedrock-agentcoreawsai-serviceAmazon Bedrock Data Automationaws-bedrock-data-automationawsai-serviceAmazon Bedrock Guardrailsaws-bedrock-guardrailsawsai-serviceAmazon Comprehendaws-comprehendawsai-serviceAmazon Comprehend Medicalaws-comprehend-medicalawsai-serviceAWS Elemental Inferenceaws-elemental-inferenceawsai-serviceAmazon Forecastaws-forecastawsai-serviceAmazon Fraud Detectoraws-fraud-detectorawsai-serviceAWS HealthScribeaws-healthscribeawsai-serviceAmazon Lex botaws-lexawsai-serviceAmazon Lookout for Equipmentaws-lookout-for-equipmentawsai-serviceAmazon Lookout for Metricsaws-lookout-for-metricsawsai-serviceAmazon Lookout for Visionaws-lookout-for-visionawsai-serviceAmazon Personalizeaws-personalizeawsai-serviceAmazon Pollyaws-pollyawsai-serviceAmazon Q Businessaws-q-businessawsai-serviceAmazon Rekognitionaws-rekognitionawsai-serviceAmazon Textractaws-textractawsai-serviceAmazon Transcribeaws-transcribeawsai-serviceAmazon Translateaws-translateawsai-serviceContent Safetyazure-ai-content-safetyazureai-serviceAzure AI Custom Visionazure-ai-custom-visionazureai-serviceAzure AI Faceazure-ai-faceazureai-serviceAzure Languageazure-ai-languageazureai-serviceAzure Speechazure-ai-speechazureai-serviceAzure Translatorazure-ai-translatorazureai-serviceAzure Visionazure-ai-visionazureai-serviceMicrosoft Discoveryazure-discoveryazureai-serviceAzure Document Intelligenceazure-document-intelligenceazureai-serviceFoundry Agent Serviceazure-foundry-agent-serviceazureai-serviceFoundry Modelsazure-foundry-modelsazureai-serviceAzure AI Immersive Readerazure-immersive-readerazureai-serviceAzure OpenAI in Foundry Modelsazure-openaiazureai-service
and 85 more → AI service page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Azure Content Understanding: analyzers that turn documents, images, audio and video into a user-defined structured schema.
# "What is Azure Content Understanding in Foundry Tools?" states confidence scores and grounding are enabled through the estimateFieldSourceAndConfidence setting and segmentation through enableSegment, so both are off unless configured, and that content filter results come from the Guardrails instance of the model deployment it uses.
schemaVersion: "1"
type: "component"
id: "azure-content-understanding"
kind: "ai-service"
provider: "azure"
docs: "https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/overview"
defaults:
  auth: "api-key"
  managed: true
  modality: "multimodal"
  contentFiltering: true
  publicEndpoint: true
  customerManagedKeys: false
properties:
  inputModality:
    type: "enum"
    values: ["document", "image", "audio", "video"]
  analyzerType:
    type: "enum"
    values: ["prebuilt", "custom"]
    default: "prebuilt"
  confidenceScores:
    type: "boolean"
    default: false
  segmentation:
    type: "boolean"
    default: false

The same page as markdown, for an agent: /catalogue/components/azure-content-understanding.md