Draft and Analyze Business Content
The whole domain turns on one move: ground the work on a real source, then reuse it
A business analyst at Contoso who needs a launch brief can type "write a launch plan" into the Copilot prompt box and get something generic, or type "/" to reference last quarter's plan and Friday's status notes and get a draft that already speaks in the team's own terminology, figures, and KPIs (key performance indicators). That single choice, drafting from a blank prompt versus grounding on a file you already have permission to open, is the lever the exam keeps pulling. Everything in this domain builds on it: a grounded Word brief becomes a PowerPoint deck, an Excel analysis becomes a written summary, and a Copilot Chat answer becomes a shared Page the whole team edits. The model to carry through the page is ground it, then move it, then collaborate on it, and the classic trap is to skip the grounding step and treat Copilot as a blank-page writer rather than a tool that reuses content you already trust.
The domain unfolds in two steps: create and move content, then collaborate on it
The first subtopic, Drafting Documents and Communications, owns producing and reshaping content: drafting in Word, building decks in PowerPoint, writing email in Outlook, getting insights in Excel, summarizing to compress a source, and moving the result across apps so you never retype it. Reach for it whenever the task is to make a document, message, or analysis. The second subtopic, Meetings, Pages, and Collaboration, owns the moments after content exists and people need to work on it together: Copilot in Teams meetings for live and after-meeting recaps, Copilot Pages for a persistent shared canvas a team co-edits, and Copilot memory plus custom instructions for personalization that follows you across chats. Reach for it whenever the task is about a meeting, shared editing, or tailoring Copilot to how you work.
When two answers both work, pick the feature that matches the stage of the work
Many AB-730 scenarios offer several Copilot actions that all sound plausible; the rewarded answer is the one whose output shape fits what the task actually needs. If the goal is to shorten one document to what matters, summarize rather than draft, because a summary stays anchored to the source while drafting can introduce new content. If the goal is a deck from a brief, use Create presentation from file rather than copy-pasting by hand. If a team must edit the answer together in real time, use a Copilot Page rather than exporting a static Word copy. And if personalization should follow only you across chats, that is memory or custom instructions, not a Page. Matching the feature to the stage, create, compress, move, or collaborate, is the instinct the exam rewards.
The two steps of the domain and what each one owns
| Step | What it owns | Reach for it when | Drill into |
|---|---|---|---|
| Create and move content | Drafting in Word, decks in PowerPoint, email in Outlook, insights in Excel, summarizing, and carrying grounded content across apps | The task is to produce, analyze, compress, or reuse a document, message, or dataset | Drafting Documents and Communications |
| Collaborate on content | Copilot in Teams meetings, Copilot Pages as a shared canvas, and memory plus custom instructions for personalization | The task is about a meeting, co-editing the answer together, or tailoring Copilot to how you work | Meetings, Pages, and Collaboration |