Content Understanding requires three AI model deployments to power its document processing pipeline. Each model serves a distinct role.
This is the brain of Content Understanding. When you define fields with generate or classify methods, the service sends the extracted document content to this LLM to:
It’s the most capable model in the pipeline and handles nuanced reasoning about document content.
Note: Microsoft now recommends
gpt-5.2as the completion model. The GPT-4.1 family retires October 2026, butgpt-4.1works fine for demos today.
Used for faster, cheaper processing on simpler tasks within the pipeline:
gpt-4.1Think of it as the “fast path.” Content Understanding routes simpler subtasks here to reduce latency and cost.
This converts text into vector representations (embeddings). Used for:
Document --> OCR/Layout --> Markdown
|
text-embedding-3-large (find relevant sections)
|
gpt-4.1-mini (simple extractions, confidence scores)
|
gpt-4.1 (generate summaries, classify, complex fields)
|
Structured Output + Confidence Scores
gpt-4.1-mini for simpler tasks keeps costs down compared to routing everything through gpt-4.1