HomeRoadmaps › AI-103
Active Microsoft associate exam

AI-103 Developing AI Apps and Agents on Azure Roadmap

Build practical skill across Microsoft Foundry models and projects, Agent Service and tools, Azure AI Search grounding, safety and evaluation, multimodal vision, language and speech, and layout-aware information extraction.

Exam code: AI-103 5 official domains Suggested pace: 8-10 weeks Skills effective: April 16, 2026
Use the official study guide as the source of truth. Microsoft Foundry, model availability, Agent Service tools, API versions, preview status, quotas, and regional capabilities change. Recheck the current AI-103 guide and linked Microsoft Learn documentation before scheduling or implementing a lab.

What active Exam AI-103 measures

The official audience profile describes an Azure AI engineer who builds, manages, and deploys agents and AI solutions with Microsoft Foundry. Candidates should have Python application-development experience and familiarity with general AI, generative AI, and Azure services. Study complete systems: identity, networks, data, retrieval, tools, evaluation, safety, operations, and cost around the model.

Plan and manage25-30%
Generative and agentic30-35%
Computer vision10-15%
Text analysis10-15%
Information extraction10-15%
1

Plan, secure, deploy, and govern Foundry solutions

Weeks 1-2

Start with architecture and responsible operation. Select services and models through evidence, then design identity, networking, deployment, CI/CD, quota, cost, safety, and observability before adding autonomous tools.

  • Map tasks to LLMs, small models, code models, multimodal models, and Foundry Tools
  • Compare model quality, modality, context, latency, safety, availability, quota, and cost
  • Choose Foundry services for generation, grounding, vector search, tools, memory, and workflows
  • Design Foundry projects, model deployments, agent deployments, environments, and rollback
  • Version code, prompts, model choices, instructions, tools, indexes, safety settings, and evaluation data
  • Use Microsoft Entra ID, managed identities, keyless credentials, least-privilege RBAC, and Key Vault when a secret is unavoidable
  • Plan private endpoints, private DNS, restricted public access, controlled egress, and end-to-end network tests
  • Manage TPM, RPM, concurrency, scaling, retries, budgets, and per-workload cost attribution
  • Configure content filters, Prompt Shields, moderation, provenance, oversight, approvals, and audit workflows
  • Combine Foundry evaluation, Application Insights monitoring, and OpenTelemetry tracing
2

Build grounded generative apps and bounded agents

Weeks 3-5

Spend the most time here. Build a cited RAG application, then turn it into an agent with narrow tools. Keep model planning separate from identity, authorization, validation, approval, and execution.

  • Connect an application to a Foundry project and consume task-appropriate model deployments
  • Engineer prompts, structured outputs, parameters, history, context, and measurable acceptance criteria
  • Implement RAG with source metadata, citations, out-of-corpus behavior, and retrieval evaluation
  • Define agent role, goals, conversation state, memory approach, tool schemas, budgets, and stopping conditions
  • Compare Azure AI Search, File Search, web search, Code Interpreter, Azure Functions, OpenAPI, MCP, and custom functions
  • Validate every tool argument, identity, scope, business rule, timeout, error, and idempotency key in trusted code
  • Require deterministic human approval for consequential actions and retain an independent kill switch
  • Design bounded multi-agent roles, handoff contracts, shared state, least-privilege tools, escalation, and cycle prevention
  • Trace models, retrieval, decisions, handoffs, tools, approvals, errors, latency, and tokens
  • Evaluate groundedness, relevance, safety, task adherence, completion, navigation, tool selection, inputs, outputs, and cost
3

Implement multimodal vision and visual safety

Week 6

Practice both focused vision APIs and multimodal models. Preserve visual evidence, review accessibility output, and treat text embedded in images as untrusted data.

  • Select image or video generation and editing models based on task, controls, region, safety, and cost
  • Understand prompt-driven generation, reference media, inpainting, masks, and editing workflows conceptually
  • Use multimodal models for grounded questions about visual evidence
  • Use Image Analysis captions, dense region captions, OCR, objects, people, and smart crops where supported
  • Create concise alt text and extended descriptions and review them against accessibility needs
  • Use Content Understanding for schema-defined image or video extraction and RAG-ready representations
  • Compare Content Understanding, Vision, Video Indexer, and multimodal models by required output
  • Moderate unsafe visual and multimodal content with appropriate controls
  • Detect indirect prompt injection in image text and keep authorization outside visual instructions
  • Evaluate missing objects, hallucinated objects, spatial relations, regions, language support, safety, latency, and cost
4

Implement language, structured text, and speech

Week 7

Choose between deterministic prebuilt language capabilities and generative extraction. Add voice only with representative audio, privacy controls, and end-to-end task evaluation.

  • Extract named entities, key phrases, topics, summaries, and validated structured JSON
  • Distinguish NER from PII detection and map redaction to organizational policy
  • Use sentiment analysis and opinion mining to associate sentiment with specific aspects
  • Detect language, harmful text, sensitive content, tone, and domain-specific errors
  • Compare Azure Translator with LLM-powered translation for the scenario and supported languages
  • Customize domain extraction or summarization only after establishing a baseline and evaluation set
  • Implement real-time or batch speech to text according to interaction and latency needs
  • Use phrase lists or custom speech when measured domain vocabulary or acoustic errors justify adaptation
  • Implement text to speech with appropriate voices, SSML, accessibility, consent, and disclosure
  • Evaluate language and speech quality, privacy, fairness, latency, cost, and human escalation
5

Build extraction and grounding pipelines, then consolidate

Weeks 8-10

Finish with ingestion and retrieval because they connect every modality to agents. Preserve structure and provenance, evaluate failures by stage, and complete both synthetic portfolio projects.

  • Ingest approved documents, images, audio, and video with validation, metadata, versioning, and failure isolation
  • Use OCR, layout analysis, tables, figures, fields, Markdown, and source locations for downstream reasoning
  • Choose Content Understanding or Document Intelligence by modality, structure, labels, schema, accuracy, and cost
  • Use prebuilt or custom analyzers and route low-confidence or inconsistent records to human review
  • Configure Azure AI Search indexes, text and vector fields, compatible embeddings, filters, and semantic configuration
  • Compare keyword, vector, hybrid, filtered, semantic, and reranked retrieval on a versioned query set
  • Monitor indexers, enrichment failures, extraction quality, freshness, vector consistency, index health, and relevance drift
  • Connect approved retrieval pipelines to applications and agent knowledge tools with citations
  • Complete the secure cited support agent and multimodal extraction projects using synthetic data
  • Use timed original questions, explain every distractor, revisit weak objectives, verify current docs, and clean up labs

PrepKloud AI-103 study surfaces

Official Microsoft sources

AI-103 study guide

Confirm the audience profile, current date, five domain ranges, and every measured skill.

Open Microsoft Learn
Foundry Agent Service

Review current agent architecture, runtimes, tools, models, identity, and observability.

Open Agent Service docs
Agent tool catalog

Compare knowledge, action, computation, search, custom, MCP, and approval-sensitive tools.

Open the tool catalog
Azure AI Search RAG

Study ingestion, chunking, embeddings, integrated vectorization, hybrid retrieval, semantic ranking, and citations.

Open RAG documentation
Content Safety

Review text and image moderation, Prompt Shields, groundedness, protected material, and current support.

Open Content Safety docs
Content Understanding

Compare multimodal analyzers with Document Intelligence for documents, images, audio, video, and RAG.

Open tool-selection guidance
Azure Language

Review NER, PII, sentiment and opinion mining, summarization, and custom text capabilities.

Open Azure Language docs
Foundry observability

Study evaluations, monitoring, OpenTelemetry tracing, Application Insights, agent metrics, and cost signals.

Open observability docs

Frequently asked questions

Is AI-103 an active Microsoft exam?

Yes. Microsoft publishes the study guide for Exam AI-103: Developing AI Apps and Agents on Azure. The current English skills measured are effective April 16, 2026. Verify the official guide before scheduling because objectives and product capabilities change.

Which AI-103 domain has the highest weight?

Implement generative AI and agentic solutions has the largest range at 30-35%, followed by plan and manage an Azure AI solution at 25-30%. The other three domains are each 10-15% and remain essential to complete architectures.

Does AI-103 require Python experience?

Yes. The official audience profile says candidates should have experience developing applications with Python and familiarity with general AI, generative AI, and Azure services.

Should preparation include hands-on agents and retrieval?

Yes. Build an agent with narrow tools, deterministic approvals, traces, and evaluations. Also build retrieval that you can test for parsing, chunks, filters, relevance, grounding, citations, safety, latency, and cost.

Are PrepKloud AI-103 questions copied from the exam?

No. PrepKloud practice is original educational material based on public objectives and official Microsoft documentation. It does not reproduce live, recalled, leaked, or proprietary exam content and cannot guarantee a passing result.

Integrity and independence: PrepKloud is independent and is not Microsoft. This roadmap uses public objectives and first-party documentation and does not contain exam dumps, recalled questions, guaranteed predictions, salary promises, or employment guarantees. Use synthetic data and disposable resources for labs, respect preview limitations and regional support, and remove paid resources after practice.

Turn architecture knowledge into evidence

Diagnose gaps with original questions, reinforce distinctions with flashcards, and prove judgment through secure synthetic projects.