How Long to Study for Azure AI Engineer (AI-102)
A complete week-by-week study plan for the Azure AI Engineer (AI-102) (Hard difficulty, ~55% pass rate).
12
Weeks
9
Hrs/Week
110
Total Hours
~55%
Pass Rate
6-8 hours this week
- Verify on the Microsoft exam and assessment lab retirement list that AI-102 retired on June 30, 2026 before spending money on any course
- Download the AI-103 study guide and map its five skill areas against the six areas of the final AI-102 blueprint
- Note the language shift: AI-103 expects Python development experience, where AI-102 accepted Python or C#
- Create an Azure subscription and a Microsoft Foundry project, and confirm your region supports the models you want
- Take the free practice assessment for AI-103 on Microsoft Learn and record the per-area result
8-10 hours this week
- Create a Microsoft Foundry hub and project and deploy one model, noting quota and rate limit settings
- Connect to the deployed model from Python using the Foundry SDK and again with a raw REST call
- Switch the connection from an account key to a managed identity and confirm the keyless path works
- Configure a private endpoint for the AI resource and verify public access is refused
- Enable diagnostic settings and send resource logs to a Log Analytics workspace
8-10 hours this week
- Configure content filters at the deployment level and test each severity threshold against sample prompts
- Add a blocklist and confirm which requests it stops that the default filter allows through
- Enable prompt shields and attempt a direct and an indirect prompt injection to see what is detected
- Read the Microsoft responsible AI documentation on harm categories and write down the four categories and their severity levels
- Run a safety evaluation against a set of prompts and read the resulting report
9-11 hours this week
- Deploy a chat completion model and a text embedding model and compare their pricing units
- Write code that varies temperature, top-p, max tokens and stop sequences and observe the effect on output
- Generate images with DALL-E and pass an image into a multimodal model to compare the two workflows
- Build a prompt template with variables and reuse it across three different inputs
- Fine-tune a small model on a labelled dataset and compare its output with the base model
9-11 hours this week
- Provision an Azure AI Search resource, create a data source, an index and an indexer over a document set
- Add a skillset with a built-in skill and then a custom skill backed by an Azure Function
- Configure semantic ranking and a vector field, then compare keyword, semantic and hybrid search results for the same query
- Ground a chat model in the index and inspect the citations it returns
- Configure a Knowledge Store projection and inspect the file, object and table outputs
9-11 hours this week
- Build a single agent with the Microsoft Foundry Agent Service, giving it one tool and one knowledge source
- Add function calling with a schema you define, and handle the tool call round trip in code
- Implement conversation memory and observe how it changes multi-turn behaviour
- Build a two-agent orchestration where one agent delegates a subtask to another
- Add an approval step before a state-changing tool runs, then trace the agent's decisions
8-10 hours this week
- Call Azure Vision in Foundry Tools with several visual feature combinations and read the JSON response field by field
- Extract printed and handwritten text from the same document and compare the confidence scores
- Train a custom image classification model and an object detection model on the same small dataset and compare precision and recall
- Publish a custom vision model and consume it from code rather than the portal
- Run a video through Azure AI Video Indexer and review the extracted insights
9-11 hours this week
- Run key phrase extraction, named entity recognition, sentiment analysis, language detection and PII detection against one text corpus
- Translate a document with Azure Translator in Foundry Tools and compare it with an LLM translation of the same text
- Implement text-to-speech and shape the output with Speech Synthesis Markup Language, adjusting prosody and pronunciation
- Build a custom question answering project, add question and answer pairs, create a multi-turn prompt flow and publish it
- Train a conversational language understanding model with intents, entities and utterances, then evaluate and deploy it
8-10 hours this week
- Run three prebuilt Document Intelligence models, including invoice and receipt, and read the confidence values on extracted fields
- Label a small document set, train a custom model, test it and publish it
- Build a composed model from two custom models and observe how routing works
- Use Azure Content Understanding in Foundry Tools to produce structured and markdown outputs from the same document
- Ingest an image, an audio file and a video through Content Understanding and compare the analyzer outputs
8-10 hours this week
- Set up tracing across a generative application and read the token analytics and latency breakdown
- Configure quota and rate limits on a deployment and trigger a throttling response deliberately
- Model the monthly cost of a RAG application, separating embedding, storage, query and completion costs
- Add a model monitoring configuration that reports drift and grounding quality
- Deploy a container image of an AI service to a local or edge target
8-10 hours this week
- Retake the Microsoft Learn practice assessment under timed conditions and compare it with your week one baseline
- Work through the Microsoft exam sandbox and interact with build list, hot area, drag and drop and case study question types
- Practise locating three specific facts on learn.microsoft.com quickly, because the exam gives access to that domain but adds no extra time
- Decide in advance where you would take a break, given that you cannot return to any question already viewed
- Rewrite every missed practice question as a one-sentence rule about which service or parameter was correct
8-10 hours this week
- Spend the largest remaining block on generative AI and agentic solutions, which carry 30 to 35 percent of AI-103
- Re-read the AI-103 study guide bullet list and tick off every item you have built at least once
- Check the Microsoft Certification deals page for an exam and retake bundle before paying full price
- Confirm your Microsoft Learn profile name matches your government-issued photo identification exactly
- Book the exam and read Microsoft's exam duration and experience page so the seat time and break rules hold no surprises
Duration: 18 weeks
Hours/week: 6 hours
Daily: ~1 hours on weeknights
Weekends: 3-4 hours Saturday + Sunday
Study during lunch breaks and commute time. Use weekends for deeper study sessions and practice tests.
Duration: 24 weeks
Hours/week: 5 hours
Saturday: 4-5 hours of focused study
Sunday: 3-4 hours of practice tests
Longer timeline but sustainable. Review flashcards on weeknights for 15-20 minutes to maintain retention.
How long does it take to study for the Azure AI Engineer (AI-102)?
Plan for 12 weeks of dedicated study at 9 hours per week (110 total hours). If studying while working full-time, extend to 18 weeks.
Can I pass the Azure AI Engineer (AI-102) in 2 weeks?
It's unlikely for most candidates. The Azure AI Engineer (AI-102) is rated "Hard" difficulty and typically requires 12 weeks of preparation. Rushing increases your risk of failing and paying the exam fee again.
How many hours a day should I study for Azure AI Engineer (AI-102)?
Aim for 2-2 hours per day on weekdays. Quality matters more than quantity, use active recall and practice tests rather than passive reading.
Is Azure AI Engineer (AI-102) hard to pass?
The Azure AI Engineer (AI-102) is rated "Hard" difficulty with a pass rate of ~55%. Solid preparation over several months is recommended.
Ready to start your Azure AI Engineer (AI-102) journey?
Get the complete exam guide with tips, resources, and practice questions.
View Azure AI Engineer (AI-102) Guide