AB-620 30-Day Study Plan 2026: Pass the Microsoft AI Agent Builder Associate Exam

Last updated: 9 October 2026

TL;DR: You can prepare for AB-620 in 30 days if you already build agents in Copilot Studio. Spend the most time on Integrate and extend agents, which is 40 to 45 percent of the exam. Learn the topics and agent flows before that, then evaluation and ALM. Do labs every week and save the last six days for timed practice.

The AB-620 (Designing and Building Integrated AI Solutions in Copilot Studio) exam leads to the Microsoft Certified: AI Agent Builder Associate certification. It is an Intermediate, role-based exam for app makers and developers who build, extend and integrate custom agents in Microsoft Copilot Studio [1]. Most questions are scenarios, not definitions. You need to know which tool, connector or orchestration pattern fits a requirement and why.

This guide turns Microsoft's official AB-620 skills outline into a 30-day schedule. It shows where to spend your hours, which hands-on labs to build, and the 2026 product changes that can catch out candidates who study from older material. It works alongside our AB-620 exam guide, which explains what the exam is, and our guide on how to pass AB-620 on your first attempt, which covers exam technique.

Is 30 days enough to pass AB-620?

Thirty days is enough to pass AB-620 if you already have some hands-on Copilot Studio experience and can study for one to two hours on most days. Microsoft's audience profile describes a professional developer or advanced builder who "builds, extends, and integrates custom agents for enterprise-grade solutions" [2]. It also expects you to have configured agents with basic knowledge sources, instructions, tools and topics before you start. If that matches your day job, a month of structured study is realistic.

Some candidates will need longer than 30 days. If you have never built an agent, never written Power Fx, or have never called a REST API, plan for six to eight weeks. The audience profile names familiarity with Power Fx, Microsoft Dataverse, Power Platform environments, Microsoft 365 Copilot, Microsoft Foundry and adaptive cards. It also lists intermediate generative AI knowledge, including retrieval augmented generation (RAG), the Model Context Protocol (MCP) and the Agent2Agent (A2A) protocol [2]. Microsoft does not publish an official study-hours figure for AB-620, so treat any hours estimate, including ours, as guidance.

AB-620 exam facts at a glance

The AB-620 exam lasts 120 minutes, needs a score of 700 out of 1000 to pass, and may include interactive components [1][2]. Microsoft does not publish a question count for AB-620. Its general guidance says most exams contain 40 to 60 questions, but the number varies [3].

Two of these facts shape the plan. First, there is no free Microsoft practice assessment for AB-620 yet. Microsoft says practice assessments usually appear within eight weeks of an exam becoming generally available [1], so independent timed practice matters more than usual. Second, AB-620 is an associate exam, so you can open Microsoft Learn during it [3]. That lookup costs exam time, so practise finding facts quickly instead of planning to rely on it. Our guide to using Microsoft Learn during your exam explains the rules.

The AB-620 skills measured and how the 30 days are weighted

The AB-620 skills outline has three domains, and the middle one carries nearly half the marks [2]:

• Plan and configure agent solutions: 30 to 35 percent. Planning integration, identity, channels, responsible AI and governance. Building and monitoring agent flows, including human-in-the-loop flows and error handling. Configuring topics, generative answers, custom prompts, HTTP requests, adaptive cards and variables.
• Integrate and extend agents in Copilot Studio: 40 to 45 percent. Connecting enterprise knowledge (Copilot connectors, Power Platform connectors and Azure AI Search). Adding tools (computer use, MCP tools, custom connectors and REST APIs). Building multi-agent solutions with Foundry agents, Fabric data agents and A2A. Integrating with Azure, including Application Insights monitoring.
• Test and manage agents: 20 to 25 percent. Evaluating agents with test sets and evaluation methods. Application lifecycle management (ALM) with solutions, environment variables and Power Platform Pipelines.

The plan below weights the 30 days towards the heaviest domain, then reserves the last six days for all three:

Microsoft adds that the bullets under each skill "are intended to illustrate how we are assessing that skill" and that "related topics may be covered in the exam" [2]. Use the outline as a map of the exam, but do not treat it as a complete list of what can appear.

Before day 1: set up your Copilot Studio lab

AB-620 rewards hands-on experience, so build a working lab before you start the plan. You need two things: Copilot Studio access, and a Power Platform environment where you can create solutions and use premium connectors.

• Copilot Studio trial. Microsoft offers a self-service Copilot Studio trial, and you can extend it by 30 days when it expires [5]. The trial lets you build agents and test them in the test chat panel, but you cannot publish them [5]. You need a work or school account, because personal email addresses may be rejected.
• Power Apps Developer Plan. The free Developer Plan gives you a personal developer environment with Dataverse, premium and custom connectors, and solution export [6]. It also needs a work or school account. Microsoft disables environments that are inactive for 30 days, so keep using it throughout the month [6].

If your employer already licenses Copilot Studio, ask your administrator for a non-production environment instead. You will need somewhere to import and export solutions in week four.

A 2026 trap to know before you study: Copilot Studio harnesses

Copilot Studio now has more than one harness. Microsoft's documentation describes a standard harness, a GitHub Copilot harness and a Copilot chat harness [7]. The standard harness powers rule-based agents and agent flows [7]. Many feature pages now open with a note that they describe features "powered by the standard harness".

This matters for AB-620 because the official self-paced learning paths for the course are titled for the GitHub Copilot harness [4]. The skills outline, however, still names standard-harness features such as topics, the generative answers node, adaptive cards and agent flows [2]. Microsoft does not state which harness the exam questions assume. The safe approach is to study the standard-harness documentation for every bullet in the outline, and use the learning paths for extra practice. Also note that the GitHub Copilot harness is a way to build agents in Copilot Studio. It is not the GitHub Copilot developer product.

Week 1 (days 1 to 7): plan and configure agent solutions

Week 1 covers the Plan and configure agent solutions domain, which is 30 to 35 percent of AB-620 [2]. It moves from design decisions to the building blocks every Copilot Studio agent uses.

Days 1 and 2: plan the solution. Work through the planning bullets: integration with enterprise systems, identity strategy, channels and deployment, responsible AI, security and governance, reusable components, and designing for internal or external audiences [2]. For identity, learn the three end-user authentication options: no authentication, Authenticate with Microsoft, and Authenticate manually [22]. Know which channels each option supports. Practise writing a one-paragraph design for an internal HR agent and an external customer agent, and note how the identity and channel choices differ.

Days 3 and 4: agent flows. Agent flows are deterministic workflows created in Copilot Studio, and they run as tools that an agent can call [8]. Build at least one flow that receives input parameters, calls a connector action, handles an error and returns output parameters. Then build a human-in-the-loop flow. The Request for information action pauses the flow and collects a reviewer's response through Outlook [8]. Finally, find where flow runs are monitored, because "Monitor agent flows" is a named bullet [2].

Days 5 and 6: topics. Topics define how a conversation progresses, and Copilot Studio offers node types including Message, Question, Adaptive Card, Condition, Variable management, Tool and Advanced nodes such as generative answers and HTTP requests [9]. In your lab, build a topic that calls your agent flow, sends an adaptive card, uses a custom prompt, and makes a Send HTTP request to a public API [2]. Learn the difference between topic, global and system variables. Also understand how generative orchestration chooses topics and tools from their descriptions. It is the default for new agents [21].

Day 7: consolidate and self-test. Write a one-page summary of the domain in your own words. Then answer a set of Domain 1 practice questions and check every wrong answer against the study guide. Our AB-620 practice questions and answers walk through the question formats you will meet.

Week 2 (days 8 to 13): knowledge sources and tools

Days 8 to 19 cover Integrate and extend agents in Copilot Studio, the heaviest AB-620 domain at 40 to 45 percent [2]. Days 8 to 13 cover the first half, which is about giving an agent knowledge and tools.

Days 8 and 9: enterprise knowledge. Learn the knowledge sources Copilot Studio supports, including public websites, uploaded documents, SharePoint, Dataverse and enterprise connectors, along with their limits and authentication requirements [10]. The exam names three knowledge integrations: Copilot connectors, Power Platform connectors and Azure AI Search [2]. Add a SharePoint site and a Dataverse table to your lab agent. Then test how the grounding and moderation settings change the answers.

Days 10 and 11: connectors, custom connectors and REST APIs. Prebuilt and custom connectors can be used as agent tools, flow actions or knowledge [11]. Add a prebuilt connector as a tool. Then create a custom connector for a simple REST API and add it to the agent. That covers two exam bullets: adding a tool through an existing custom connector, and adding REST APIs to an agent [2]. Write good tool descriptions, because generative orchestration uses them to decide when to call a tool.

Day 12: MCP tools. You can connect an existing Model Context Protocol (MCP) server to a Copilot Studio agent with the onboarding wizard or a custom connector [12]. Copilot Studio supports only the Streamable transport, and authentication can be none, API key or OAuth 2.0 [12]. Learn these constraints well, because scenario questions often hinge on a server that uses an unsupported transport or the wrong authentication type.

Day 13: computer use. Computer use lets an agent operate websites and Windows desktop applications that have no API [13]. It requires generative orchestration, and Microsoft lists it as generally available from May 2026 [13][14]. Know when computer use is the right choice (a legacy app with no connector or API) and when it is not (a system with a supported connector, which is cheaper and more reliable).

Week 3 (days 14 to 19): multi-agent collaboration and Azure integration

Days 14 to 19 complete the Integrate and extend agents domain. This is where AB-620 tests architecture: how agents work together and how Copilot Studio uses Azure services.

Days 14 and 15: multi-agent design. Copilot Studio supports child agents, connected Copilot Studio agents, and external agents through A2A, Microsoft Foundry, Fabric data agents and the Microsoft 365 Agents SDK [15]. Microsoft's guidance warns that routing quality can degrade beyond roughly 30 to 40 choices for the orchestrator [15]. Build a parent agent with one child agent and one connected agent. Then write down when you would choose each. Our hands-on guide to building a multi-agent solution in Copilot Studio goes through this lab step by step.

Day 16: A2A, Foundry and Fabric agents. You connect an A2A-capable agent by its endpoint URL, and the authentication options are none, API key or OAuth 2.0 [16]. Integrating a Foundry agent and a Fabric data agent are both named exam bullets [2], but Microsoft's documentation still labels both integrations as preview [15]. The study guide says the exam "may contain questions on Preview features if those features are commonly used" [2], so learn the prerequisites and limitations as they are documented now. Foundry connections only work with agents from the new Microsoft Foundry portal [15]. If you studied under the older name, read our explainer on Azure AI Foundry becoming Microsoft Foundry.

Days 17 and 18: integrate with Azure. The Azure bullets cover generative answers that use Azure AI Search with Foundry, custom prompts that use models from the Foundry model catalog, and monitoring agents with Application Insights [2]. In your lab, connect an Azure AI Search index if you have Azure credit. Otherwise, study the configuration steps closely and be clear about which service does what. Azure AI Search retrieves content, the Foundry model generates the answer, and Application Insights records telemetry.

Day 19: consolidate the domain. This is the largest domain, so take a longer practice set across knowledge, tools, multi-agent and Azure scenarios. Go back to the documentation for any area where you score below about 75 percent. Do not move on until your weak spots are fixed.

Week 4 (days 20 to 24): evaluate, test and manage agents

Days 20 to 24 cover Test and manage agents, which is 20 to 25 percent of AB-620 [2]. It is the smallest domain, but the questions are precise and process-based, so you need to know the exact steps.

Days 20 and 21: agent evaluation. Copilot Studio agent evaluation uses test sets of test cases that you can generate, import or write by hand. Each case is scored with a chosen test method [17]. Microsoft lists agent evaluation as generally available from March 2026 [14]. In your lab, create a test set, run it with at least two evaluation methods, and read the results. Note the documented limitations, including that Fabric data agents are not supported [17].

Days 22 and 23: solutions and environment variables. Copilot Studio agents live in Power Platform solutions. Learn how to create a custom solution, add an existing agent to it, and export it as managed or unmanaged. Environment variables hold values that change between environments. Their data types include text, JSON, data source and secret, and secrets need Azure Key Vault [18]. Move a URL that your agent calls into an environment variable, then export the solution.

Day 24: Power Platform Pipelines. Pipelines provide in-product deployment of solutions between environments, with options such as delegated deployments and extensibility [19]. Production target environments must be managed environments [19]. Learn the stages of a pipeline, who can run it, and how environment variable values are supplied during deployment. "Implement and extend Microsoft Power Platform Pipelines" is a named bullet, so know the extensibility points as well as the basics [2].

Days 25 to 30: timed practice, gap closing and exam logistics

The last six days are for exam performance, not new material. Use them to work out where you are still losing marks and to fix those areas.

Days 25 to 27: full timed practice tests. Sit full-length practice tests under exam conditions: 120 minutes, no interruptions and no notes. After each test, sort every wrong answer by domain and sub-skill. Because Microsoft has no AB-620 practice assessment yet [1], independent practice tests are your best guide to readiness. Aim for scores comfortably above the 700 pass mark, not just above it.

Days 28 and 29: close your weakest domain. Go back to the documentation and your lab for the two or three sub-skills you keep missing. Rebuild the relevant lab exercise from scratch without notes, because that shows whether you really understand it. Re-read the study guide once more as well. Copilot Studio changes quickly, so check that the outline has not changed since you started [2].

Day 30: logistics and rest. Confirm your booking and identification. Try the exam sandbox to get used to the interface [1]. If you are sitting the exam online, run the OnVUE system test in advance, and read our Microsoft online proctored exam guide for the room and ID rules. After that, stop studying for the day. Rest will help you more than a final cram.

How many hours a day should you study for AB-620?

Most candidates following this plan should study for about 1 to 2 focused hours on weekdays and 3 to 4 hours at weekends. That adds up to roughly 45 to 60 hours over the month. This is our estimate, not a Microsoft figure, because Microsoft does not publish recommended study hours for AB-620. Spend at least half of each session on hands-on lab work rather than reading. Scenario questions test whether you have actually configured a feature, and lab practice is how you get that experience.

If you are an experienced Copilot Studio builder, you can compress the plan into 14 days. Combine weeks 1 and 4 (the two lighter domains) into one week, and keep the full time for the Integrate and extend domain. If you are newer to the platform, stretch the plan to about 45 days by doubling the time for weeks 2 and 3. Do not shorten the hands-on time in either case.

Common mistakes that derail an AB-620 study plan

• Splitting time evenly across domains. Integrate and extend is 40 to 45 percent of the exam, so it gets about 12 of your 30 days [2].
• Studying only the GitHub Copilot harness learning paths. The skills outline names standard-harness features, so study their documentation too [2][7].
• Using the old Foundry name and portal. Foundry agent integration needs agents from the new Microsoft Foundry portal [15].
• Ignoring preview features. Foundry and Fabric data agent integrations are preview, but they are still in the outline [2][15].
• Reading without building. Topics, flows, connectors and pipelines are all hands-on skills, and the scenario questions show it.
• Relying on open-book access. You can use Microsoft Learn in the exam, but the timer keeps running [3].

If you fail, you can retake after 24 hours. After that, there is a 14-day wait between attempts, with a limit of five attempts in 12 months [20]. Our guide to the Microsoft exam retake policy covers how to rebuild your plan after a fail.

Your AB-620 exam-week checklist

• Booking confirmed and identification ready
• OnVUE system test completed if sitting online
• Exam sandbox tried at least once
• One-page summaries written for all three domains
• Lab agent built with a topic, an agent flow, a custom connector, an MCP tool and a child agent
• Solution exported with an environment variable and deployed through a pipeline
• At least two full timed practice tests scored comfortably above 700
• Study guide checked once more for changes in the final week

Frequently asked questions

How long should I study for AB-620? Most candidates with some Copilot Studio experience need about 30 days at 1 to 2 hours on weekdays and 3 to 4 hours at weekends, roughly 45 to 60 hours. Newer builders should allow six to eight weeks. Microsoft publishes no official study-hours figure for AB-620, so base your timeline on your hands-on experience.

Is the AB-620 exam hard? AB-620 is an Intermediate, associate-level exam, and most candidates find it demanding because it tests applied judgement, not recall. Questions present scenarios where you choose the right connector, tool, orchestration pattern or ALM approach. Candidates who have built agents, flows and multi-agent solutions in Copilot Studio usually find it manageable with structured preparation.

Is there a free AB-620 practice test from Microsoft? Microsoft does not currently offer a free practice assessment for AB-620. Its certification page says the practice assessment is not yet available, and these usually follow within about eight weeks of general availability. Until then, use the exam sandbox to learn the interface and independent timed practice tests to measure readiness.

Can I use Microsoft Learn during the AB-620 exam? Yes, Microsoft allows access to Microsoft Learn during associate and expert exams, and AB-620 is associate level. You can browse learn.microsoft.com, but not Q&A, practice assessments or your profile. No extra time is added and the timer keeps running, so use it only for occasional lookups.

Do I need coding skills for AB-620? AB-620 does not require you to write application code, but it expects more technical depth than business-user exams. Microsoft's audience profile names Power Fx, REST APIs, integration patterns and adaptive cards. You should be comfortable configuring HTTP requests, custom connectors and MCP tools, and reading JSON responses.

How long is the AB-620 exam and what is the pass mark? The AB-620 exam lasts 120 minutes and you need 700 out of 1000 to pass. Microsoft does not publish a question count for AB-620; its general guidance says most exams contain 40 to 60 questions. The exam may include interactive components, and the certification renews annually through a free online assessment.

Start your AB-620 preparation

A 30-day plan works best when your practice matches the real exam's weighting. Examinotion's AB-620 preparation course includes seven practice tests of 40 questions each. The questions are weighted to the three official domains, include case studies, and come with detailed explanations so you can see quickly where you are losing marks. To compare AB-620 with other Microsoft AI certifications, browse the Microsoft AI exams hub.

Sources

1. Microsoft Certified: AI Agent Builder Associate - Microsoft Learn, accessed 2026-10-09
2. Study guide for Exam AB-620: Designing and Building Integrated AI Solutions in Copilot Studio - Microsoft Learn, accessed 2026-10-09
3. Exam duration and exam experience - Microsoft Learn, accessed 2026-10-09
4. Course AB-620T00-A: Design and build integrated AI agent solutions in Copilot Studio - Microsoft Learn, accessed 2026-10-09
5. Get access to Copilot Studio - Microsoft Learn, accessed 2026-10-09
6. Power Apps Developer Plan - Microsoft Learn, accessed 2026-10-09
7. Copilot Studio harnesses overview - Microsoft Learn, accessed 2026-10-09
8. Agent flows overview - Microsoft Learn, accessed 2026-10-09
9. Create and edit topics - Microsoft Learn, accessed 2026-10-09
10. Knowledge sources in Copilot Studio - Microsoft Learn, accessed 2026-10-09
11. Use connectors in Copilot Studio - Microsoft Learn, accessed 2026-10-09
12. Add an existing MCP server to an agent - Microsoft Learn, accessed 2026-10-09
13. Computer use in Copilot Studio - Microsoft Learn, accessed 2026-10-09
14. What's new in Copilot Studio - Microsoft Learn, accessed 2026-10-09
15. Add other agents to your agent - Microsoft Learn, accessed 2026-10-09
16. Connect an agent using the Agent2Agent protocol - Microsoft Learn, accessed 2026-10-09
17. Agent evaluation in Copilot Studio - Microsoft Learn, accessed 2026-10-09
18. Environment variables overview - Microsoft Learn, accessed 2026-10-09
19. Overview of pipelines in Power Platform - Microsoft Learn, accessed 2026-10-09
20. Exam retake policy - Microsoft Learn, accessed 2026-10-09
21. Generative orchestration in Copilot Studio - Microsoft Learn, accessed 2026-10-09
22. Configure user authentication in Copilot Studio - Microsoft Learn, accessed 2026-10-09