AB-620 Cheat Sheet: Task-to-Feature Quick Reference
Organized by what you're trying to do, not by domain — find the Copilot Studio feature fast, then check the pattern table for how the exam phrases it.
Exam Snapshot
Domain weights, the passing score, and every referenced feature trace back to Microsoft's official AB-620 study guide and Microsoft Copilot Studio documentation. Microsoft does not publish an exact question count or duration for AB-620 as of this writing.
How to Use This Page
Instead of grouping by exam domain, the table below groups by the thing you're trying to accomplish — because that's how the exam actually poses most questions: a scenario describing a goal, then four options for how to achieve it. Scan the left column for your scenario, then check the right column for the trap.
Task Ledger
| You want to… | Configure this | Watch out for |
|---|---|---|
| Bring in ServiceNow, SAP, or SharePoint content as broad searchable knowledge | Copilot connector (Enterprise knowledge sources) | Indexes content into Microsoft Graph — best for broad grounding, not live transactional data |
| Read or write live, up-to-the-second data from a line-of-business system | Microsoft Power Platform connector | Calls the API in real time — no data replication, ideal for current facts and transactions |
| Ground answers in your own custom vector/semantic search index | Azure AI Search knowledge source | Requires a Foundry-connected Azure AI Search resource, not a Copilot connector |
| Let the agent call tools from an existing MCP server | Tools → Add a tool → Model Context Protocol | Copilot Studio negotiates the handshake and lists the server’s tools; you can disable individual tools per agent |
| Automate a legacy app or website with no API | Computer use tool (Computer-Using Agent model) | Perceives the screen, reasons, then drives a virtual mouse/keyboard — needs generative orchestration turned on |
| Call your own internal REST endpoint directly | Add REST API as a tool | Different path from a custom connector — use when you don’t need the connector wrapper |
| Delegate a task to an agent built on another framework or hosted elsewhere | A2A (Agent2Agent) protocol connection | Supports multiturn interactions and rich metadata — a plain HTTP connector does not |
| Connect to a Microsoft Foundry agent | Foundry agent integration | Foundry agents expose only Responses + A2A by default — the Activity protocol endpoint must be enabled via REST API/Python SDK first, or the connection 400s |
| Pull structured analytics from a Fabric workspace | Fabric data agent integration | A distinct integration path from Foundry or A2A agents |
| Let a person approve or supply info mid-automation | Human-in-the-loop agent flow | Different from a standard agent flow — pauses for input instead of running straight through |
| Show buttons, images, or structured input in a response | Adaptive card node inside a topic | Configured at the topic level, not the agent flow level |
| Answer from a narrow, specific, bounded source | Generative answers node with a scoped knowledge source | Different from a broad custom prompt — the exam tests this distinction directly |
| Measure whether the agent gives accurate, grounded answers | Evaluation method + test set | Match the method to what you’re measuring — accuracy, tool-call correctness, or task completion aren’t the same check |
| Watch for latency, failures, or usage trends over time | Application Insights monitoring | Operational telemetry — not the same tool as answer-quality evaluation |
| Move an agent from dev to test to production without hardcoding values | Solution + environment variables + Power Platform Pipelines | Standard Power Platform ALM applied to agents |
Knowledge-Source Decision Table
Domain 2's single most-tested distinction — three ways to ground an agent, one job each:
| Source | Mental model | Best for |
|---|---|---|
| Copilot connector | Search & index — copies content into Microsoft Graph | Broad, searchable knowledge with citations across Microsoft 365 |
| Power Platform connector | Live API bridge — no data replication | Up-to-date facts, transactions, read/write actions |
| Azure AI Search + Foundry | Your own managed semantic index | Custom-built retrieval you control end to end |
If the Question Says X, Think Y
| Exam cue | Think |
|---|---|
| The question says “ServiceNow,” “SAP,” or “index a large document set” | Think Copilot connector, not Power Platform connector |
| The question says “real-time,” “current inventory,” or “write data back” | Think Power Platform connector, not Copilot connector |
| The question says “no API exists” or “legacy desktop app” | Think computer use, not MCP or REST API |
| The question says “existing MCP server” or “tools exposed by a server” | Think MCP tools, not a custom connector |
| The question says “agent built on another framework” or “hosted outside Copilot Studio” | Think A2A protocol, not a plain HTTP connector |
| The question describes a Foundry connection that fails with a 400 error despite correct credentials | Think missing Activity protocol endpoint on the Foundry agent |
| The question says “approval before continuing” or “needs more info from a person” | Think human-in-the-loop agent flow, not a standard topic |
| The question says “buttons,” “structured input,” or “rich response” | Think adaptive card node |
| The question says “move to production” or “different environment values” | Think solution + environment variables, not manual reconfiguration |
| The question says “track latency or failures over time” | Think Application Insights, not agent evaluation |
Quick Terms
| Term | Meaning |
|---|---|
| MCP | Model Context Protocol — a standard for exposing tools/resources to an agent from a connected server |
| A2A | Agent2Agent protocol — an open standard for one agent to delegate tasks to another across frameworks |
| RAG | Retrieval-augmented generation — grounding a model’s answer in retrieved external content |
| CUA | Computer-Using Agent — the model powering the computer use tool’s screen perception and control |
| ALM | Application lifecycle management — solutions, environment variables, and pipelines for agents |
| ISV | Independent software vendor — one of AB-620’s named candidate audience roles |
| Foundry | Microsoft Foundry — Azure’s AI platform for models, agents, and the model catalog |
| Fabric | Microsoft Fabric — the data platform whose data agents can be integrated into a Copilot Studio agent |
Quick Answers
How is this cheat sheet different from the AB-620 study guide?
The study guide explains each domain's reasoning and common traps in narrative form. This page is organized by task — what you're trying to do — for a fast lookup during final review.
What's the single most-confused topic?
Copilot connectors versus Power Platform connectors as knowledge sources — see the decision table above.
Does this cheat sheet cover everything the exam tests?
No single page replaces hands-on Copilot Studio experience, which Microsoft's audience profile explicitly expects. Use this as a review aid alongside actually building an agent and connecting an MCP server yourself.
Can I print this AB-620 cheat sheet?
Yes — every table here is plain HTML, so a browser print or "print to PDF" renders cleanly.
MSCertQuiz sells practice-exam access for AB-620 and other Microsoft certifications; this cheat sheet is written by the same team that builds those questions.
Continue Your Prep
Domain-by-domain narrative behind this quick reference.
12 scenario questions across Easy, Medium, and Hard tiers.
Full exam details and the complete 500-question bank.
Browse every Microsoft certification MSCertQuiz covers.
Glossary down. Now spot the pattern live.
Start with 40 free AB-620 questions covering every task above.
Start Free AB-620 Practice