explainx / blog
Microsoft's AI-103 is a 120-minute proctored Associate exam covering Microsoft Foundry, Foundry Agent Service, RAG on Azure AI Search, computer vision, speech, and document extraction. Domain weights, the Foundry naming maze, scenarios, pricing—and explainx.ai mock tests and study pathway.
Jul 3, 2026
Microsoft renamed its AI platform three times in two years. Here is the timeline, what each term means today, and how to keep Foundry Tools, Foundry Agent Service, and Foundry IQ straight for the AI-103 exam.
Jul 3, 2026
Professional-tier AWS certification: 65 scored questions in five domains, six production scenario frames, $300 per attempt. Here is the competency map, what to expect on exam day, official Skill Builder prep—and our mock test bank.
Jul 3, 2026
Vector search ranks by embedding similarity. Semantic search reranks with language understanding. Hybrid combines keyword and vector. Here is how each works, when to use it, and how Azure AI Search implements all three.
Microsoft's Azure AI Apps and Agents Developer – Associate (AI-103) is the company's bid to standardize production-grade generative AI and agent development on Azure — the practical work of shipping Microsoft Foundry apps with RAG, agents, vision, speech, and document extraction, in Python.
This post is a field guide: format, the Foundry naming maze, domains, per-domain depth, the #1 confusable topic (semantic vs vector vs hybrid search), pricing, official prep, and how explainx.ai fits in — including timed mock tests, a certification study guide, and a structured learning pathway.
Disclaimer: Exam structure and policies belong to Microsoft and Pearson VUE. Confirm details on the official exam page before you register.
The target candidate is an Azure AI engineer or developer who builds AI apps and agents with Python and the Microsoft Foundry SDKs. Microsoft rates it at the intermediate level, delivered as a proctored exam through Pearson VUE, currently in English, with a 24-hour wait before a retake.
You should be comfortable with:
Explicitly out of scope: training models from scratch, non-Azure services as primary answers, and data engineering unrelated to AI ingestion.
| Attribute | Detail |
|---|---|
| Duration | 120 minutes, proctored via Pearson VUE |
| Questions | ~40 (estimate) — Microsoft does not publish an exact count for AI-103; 40 is a reasonable pacing estimate for a 120-minute associate exam |
| Format | Multiple choice and multiple response (select all correct answers) |
| Pass score | 700 / 1000 — officially documented: "a score of 700 or greater is required to pass" |
| Pricing | $165 USD per attempt (US; varies by country) |
| Retake | Wait 24 hours after a failed attempt |
Be honest with yourself about pacing. The 700/1000 pass score is official and confirmed. The ~40-question count is an estimate we use only to reason about time per question — do not treat it as gospel. At ~40 questions in 120 minutes you have roughly 3 minutes each, which is generous for MCQs but tight if several are long, multi-part scenario items.
More candidates lose points to branding confusion than to any single technical gap. Microsoft's platform has been renamed repeatedly, and the docs still carry legacy URLs. Here is the map as of early 2026:
learn.microsoft.com/azure/foundry/, but the ai.azure.com portal domain persists from the older naming.If you want the full rebrand timeline and why ai.azure.com URLs survive, read our dedicated Microsoft Foundry naming explained post.
| Domain | Weight | What it emphasizes |
|---|---|---|
| Plan and manage an Azure AI solution | 25-30% | Foundry service/model selection, deployment, quotas/rate limits, security, monitoring, responsible AI |
| Implement generative AI and agentic solutions | 30-35% | Generative apps, RAG, Foundry agents, tool integration, multi-agent orchestration, gen-AI ops |
| Implement computer vision solutions | 10-15% | Image/video generation and editing, multimodal understanding, responsible AI for visuals |
| Implement text analysis solutions | 10-15% | Entities, sentiment, translation, and speech as a first-class agent modality |
| Implement information extraction solutions | 10-15% | Semantic/vector/hybrid search, enrichment skills, OCR + layout + field extraction |
The agentic and generative AI domain is the largest at 30-35% — give it the most study time. Plan and manage is a close second. The three implementation domains (vision, text, extraction) are each smaller but together make up 30-45% and share a lot of grounding/retrieval concepts.
This is where most points live. Three threads:
Generative apps with Foundry. Deploy and consume LLMs, small language models, code models, and multimodal models. Implement RAG against grounded knowledge. Design tool-augmented, multistep reasoning workflows. Evaluate models for fabrications, relevance, quality, and safety. Integrate through Foundry SDKs and connectors and configure app-to-project connections.
Agents with Foundry Agent Service. Define agent roles, goals, conversation tracking, and tool schemas. Integrate retrieval + function calling + memory. Wire up agent tools — APIs, knowledge stores, Azure AI Search, Content Understanding, custom functions. Build orchestrated multi-agent solutions and autonomous/semiautonomous workflows with safeguards and approval flows.
Optimize and operationalize. Prompt engineering and parameter tuning; reflection / chain-of-thought / self-critique loops; observability — tracing, token analytics, safety signals, latency; and orchestrating multiple models or hybrid LLM + rules-engine designs.
Trap alert. When a scenario says answers are wrong or hallucinated, the exam loves to offer fine-tuning as a distractor. In most AI-103 scenarios the right fix is better grounding (RAG) or better prompting, not fine-tuning. Also distinguish chain-of-thought / self-critique within a single model call from a separate evaluator agent in a multi-agent loop — and remember a tool-augmented flow with function calling is not automatically an "agent" (agents imply a role, goal, memory, and tool schema). Our multi-agent orchestration patterns guide covers sequential handoff vs planner/router vs parallel, which the exam swaps in distractors.
Service selection (Foundry Tools vs Foundry Agent Service), deployment options, quotas/rate limits (throttling) vs cost management (billing) as distinct controls, security (managed identity, private networking, keyless credentials, role policies), and monitoring (model performance, drift, safety events, grounding quality). Two recurring distinctions:
Image and video generation from text and reference media; editing — inpainting (fill masked regions), mask-based targeted edits, and prompt-driven whole-image modifications (these are technically distinct, and the exam exploits candidates who use them interchangeably). Multimodal understanding — captioning, visual Q&A, accessibility alt-text (concise) vs detailed descriptions, and Content Understanding single-task vs pro-mode pipelines. Plus responsible AI for visuals: unsafe-content filters, watermarks/prohibited symbols/brand rules, and indirect prompt injection via text embedded in an image (distinct from direct prompt injection through user input).
Entity/topic/summary/structured JSON extraction, sentiment vs tone vs safety/sensitive-content as three distinct tasks, and translation via Azure Translator (dedicated, good for consistent terminology and glossary control) vs LLM-powered translation (nuanced/contextual). Plus speech: speech-to-text/text-to-speech as an app feature vs speech as a first-class agent modality with custom speech models for domain jargon. Structured-output patterns are worth reviewing — see our structured output / JSON mode guide.
Retrieval/grounding pipelines: ingest and index documents, images, audio, video; semantic/vector/hybrid search; enrichment via built-in skills (native) vs custom skills (a hosted function/API called during indexing); RAG ingestion (chunking, embeddings, grounding metadata, OCR). Document extraction combines OCR + layout analysis + field extraction as three separate stages — pulling a specific named field from an invoice needs field extraction, not just an OCR text dump.
If you learn one thing cold, make it this. Azure AI Search implements all three, and the exam leans on the distinction constantly:
The tell: a scenario describing "combining keyword precision with meaning-based relevance" is hybrid, not semantic alone. We wrote a full technical explainer — semantic vs vector vs hybrid search — because this single distinction shows up across Domains 2 and 5.
Practice exam
3 timed mock exams with shuffled questions, instant scoring, and per-question explanations. Pass score: 720/1000. The fastest way to find your weak domains before exam day.
Microsoft's AI-103 exam page links four learning paths. Work them in this order:
Then build one real thing: a RAG app on Azure AI Search where you toggle semantic, vector, and hybrid retrieval and watch the difference. Preview the exam sandbox to see the Pearson VUE interface, and finish with explainx mock tests for scenario-style MCQ practice.
Start mock tests → — eight timed practice exams (two Foundations drills, a Plan & Manage focus, an Agentic & Generative AI focus, a Vision/Text/Extraction focus, a Retrieval & Grounding focus, a scenario marathon, and a 40-question / 120-minute simulation), 400+ shuffled multiple-choice questions, instant explanations, $5 lifetime access.
Certification study guide → — domain weights, task statements per domain, six scenario narratives, in-scope / out-of-scope topics, and an Azure AI service checklist mapped to the official skills outline.
Learning pathway → — articles mapped to exam domains with embedded quiz questions.
AI-103 validates that you can move beyond a prototype to production generative and agentic AI on Azure — Foundry apps, agents, RAG, vision, speech, and extraction. Learn the Foundry naming, master semantic vs vector vs hybrid search, weight your study toward the agentic/generative domain, work Microsoft's four learning paths, and run mock tests before your Pearson VUE sitting.
Practice exam
3 timed mock exams with shuffled questions, instant scoring, and per-question explanations. Pass score: 720/1000. The fastest way to find your weak domains before exam day.
Exam names, weights, and policies are summarized from Microsoft's public certification messaging; the ~40-question count is an estimate for pacing, while the 700/1000 pass score is officially documented. Verify all details on Microsoft Learn before registering. explainx.ai is not affiliated with Microsoft's certification program.