Microsoft's AI Agent Builder Associate cert. The official courseware is a swamp. This is the map through it — built on the fact that you already own a third of the ground.
Tick items as you lock them in. The green ones are pre-checked because you do them for a living — that's your head start.
Half the misery of this exam is Microsoft re-explaining agents to someone who ships multi-agent systems on opencode and runs MCP servers by hand. Don't relearn these. Just learn the branded noun and move on.
MCP tools — it's literally the Model Context Protocol. You run MCP servers. Copilot Studio just gives you a wizard to point an agent at one. Learn the 3-click flow, not the protocol.
Custom connectors / Send HTTP request / REST API tools — REST + OAuth 2.0 you already do in bug-bounty and tooling. This is the same, in a form designer.
Grounding / knowledge sources — it's RAG. Retrieval you already understand. The only new part is which Microsoft product does the retrieving (Azure AI Search).
Multi-agent orchestration + A2A protocol — you build agent hand-off already. A2A is just the open standard for it. Connected/child agents = your sub-agents with a GUI.
Custom prompts / instructions — prompt engineering. Nothing new here except the box you type it in.
Application Insights monitoring — telemetry / observability. Familiar territory, Azure branding.
Each domain below maps Microsoft's term → what you already know, then flags the genuinely-new bits and the traps they'll set in the questions. Tap a domain to open it.
Generative answers node vs authored topic — they hand you a scenario and make you pick. Rule of thumb: unpredictable / open-ended → generative; deterministic / compliance-critical flow → authored topic.
Variable scope — global (whole agent) vs topic-local. Easy points if you know it, easy loss if you don't.
MCP tool vs custom connector vs REST API tool — they give a scenario, you pick the mechanism. Speaks MCP → MCP tool. Existing REST endpoint you define → custom connector / HTTP action. Don't overthink it, but know the tell in each question.
A2A vs connected agents — same platform = connected/child agent. Different vendor/platform = A2A. This distinction shows up constantly.
Foundry agent vs Copilot Studio agent — know why you'd reach into Foundry (model catalogue, pro-code models) vs staying native.
This whole domain is the sleeper. Coming from pure red-team/dev work, ALM (solutions, env variables, Pipelines) is the least-familiar and the cheapest points to grab. Do one hands-on lab moving a solution between environments and this domain becomes free marks.
The exam is mostly "given this scenario, pick the mechanism." These are the recurring decisions. Answer in your head, then reveal.
ScenarioYour agent must call a third-party tool that already speaks MCP. What do you add?
ScenarioYour agent must hand a task to an agent running on a different vendor's platform. Which protocol?
ScenarioYou need the same agent to move from dev to prod with no hardcoded URLs or keys. What's the play?
ScenarioGround the agent in a large enterprise document corpus with semantic/vector search. Which service?
ScenarioA flow must pause for a manager to approve before it continues. What are you configuring?
ScenarioWhere do you write formula logic to set or transform a variable's value?
The exam rewards hands-on and punishes crammers — it's built around scenarios you can't fake. So the plan is mostly labs, weighted toward Domain 2.
Spin up a Power Platform trial, open Copilot Studio, build and publish one working agent end-to-end. Non-negotiable — everything else builds on this.
day 0Lab, don't read: connect Azure AI Search grounding, add a REST API tool, wire an MCP tool, set up connected agents + an A2A hand-off, integrate a Foundry agent. This is most of your hours.
bulk of your timeBuild an agent flow with a human approval + error handling. Author a topic using the generative answers node and an adaptive card. Touch Power Fx variables until the syntax stops feeling foreign.
the branded UICreate a solution, add your agent, use an environment variable, push it through a Power Platform Pipeline dev→test. One lab converts the sleeper domain into easy points.
don't skipMemorize the Microsoft-named features for moderation, groundedness, governance. Pure-dev candidates lose cheap points by describing the concept instead of naming the feature.
cheap pointsYou get split-screen Microsoft Learn — pre-bookmark the ALM, Foundry, and connector reference pages for quick lookups. It's a safety net for one detail, not a substitute for the labs. Clock keeps running.
go timeThese are the real spine of the exam and they're free. Use them as the outline; do the labs above for the actual retention. Skim the parts you already own.