6.1 Map Business Processes and Use Cases to Copilot
Key Takeaways
- Map Copilot to knowledge work that already lives in Microsoft 365: drafting, meeting recap, inbox triage, spreadsheet analysis, presentation generation, and question-and-answer over files the user can already open.
- Work-grounded Copilot uses Microsoft Graph and Work IQ on content the signed-in person is already allowed to see; it does not create a new permission to secret files.
- A named human still owns send, file, or present. Copilot accelerates a first draft; it does not replace counsel, finance, or HR judgment.
- Custom vision APIs, high-volume document intelligence, and a model catalog are Foundry and Foundry Tools jobs, not first-fit Copilot mappings.
- Consumer Microsoft Copilot signed in with a personal account is the wrong process map for tenant mail, files, and meetings.
6.1 Map Business Processes and Use Cases to Copilot
Quick Answer: Put Microsoft 365 Copilot and Microsoft Copilot on processes that already happen in Word, Excel, PowerPoint, Outlook, Teams, and related Microsoft 365 apps: draft, recap, triage, analyze a sheet, generate a deck, and ask questions over files the user can already open. Do not map Copilot to a custom vision API, a high-volume document-intelligence pipeline, or a model catalog. Those are Microsoft Foundry and Foundry Tools jobs.
Microsoft's July 22, 2026 skills list for Exam AB-731: AI Transformation Leader asks you to map business processes and use cases to Copilot. You do this as a business decision-maker. You are not expected to write code. You are expected to name the process, name the Copilot-shaped outcome, and know when a different Microsoft AI family is the first fit.
Copilot, in this chapter, means the productivity assistant Microsoft documents as pairing large language models (LLMs) with Microsoft 365 apps and, when licensed, with Microsoft Graph and Work IQ. Access stays scoped by the user's existing permissions. That permission story is the whole mapping trick: Copilot helps a person do work they could already do more slowly. It is not a master key to other people's mailboxes.
Start with the process, not the brand
Sit with the process owner. Write the verb on a whiteboard before anyone says a SKU.
- What artifact must exist by Friday: an email, a recap, a cleaned inbox, a chart, a slide deck, or an answer with citations?
- Where does the source already live: a Word file, an Excel table, a mailbox, a Teams meeting, a SharePoint library?
- Who is allowed to see that source today?
- Who owns the send, file, or present button after the draft appears?
- Is the work interactive (a person waiting in the app) or a batch pipeline (thousands of files overnight)?
If the source is not in Microsoft 365, or the job is extract a field from 80,000 PDFs, stop. Copilot can still draft a memo about that pipeline. It is not the pipeline.
Six first-fit Copilot mappings
Microsoft's Copilot overview and in-app documentation describe the same everyday jobs AB-731 expects you to recognize. Map them as processes.
| Process | Typical app | What Copilot produces | Leader watch-out |
|---|---|---|---|
| Drafting | Word, Outlook, OneNote | A first-pass document, email, plan, or list the owner still edits | Fluency is not approval. Legal notices and customer credits need a named reviewer. |
| Meeting recap | Teams (and Outlook calendar follow-up) | Summary, decisions, and action items from a transcript or recording | After-meeting recap needs transcription or recording turned on. Copilot in a live meeting answers from that meeting's transcript, not from the rest of the tenant. |
| Inbox triage | Outlook | Thread summaries, draft replies, coaching on clarity, sentiment, and tone | Copilot is documented for Exchange Online mailboxes leaders actually use. Microsoft's requirements page currently says it is not available on group mailboxes. Reopen that page before you promise shared-mailbox magic. |
| Spreadsheet analysis | Excel | Insights, formula suggestions, charts, and natural-language questions over the grid | Analyst-style deep reasoning over numbers is a later Copilot agent topic. Everyday Excel Copilot is the first mapping. |
| Presentation generation | PowerPoint | A deck from a prompt or from a Word file, plus summary and light edits (slides, pictures, deck-wide formatting) | Enterprise templates and a human editor still own brand and numbers. |
| Q&A over work files | Copilot Chat with a Copilot license, or in-app chat on an open file | Answers grounded in files, mail, meetings, and sites the user can already access | Web-only Copilot Chat without work grounding will not roam the tenant. Upload, attach, or license work chat. |
Keep the list in that order on exam day. If a stem names one of those six verbs and the content already lives in Microsoft 365, Copilot is the default map.
Worked mappings by role
Chief financial officer (CFO). Board package due Monday. The forecast already exists in Excel. Mapping A: Copilot in Excel to explain variance and propose a chart the FP&A lead still checks. Mapping B: Copilot in Word or PowerPoint to turn the approved commentary into a narrative or slides. Mapping C is a miss: asking Copilot to invent next quarter's units instead of using the forecast model.
Operations vice president. Plant leadership lives in Teams. Mapping A: Copilot in Teams to recap the daily standup and list owners. Mapping B: Copilot in Outlook to triage vendor threads after a missed shipment. Mapping C is a miss: counting damaged cartons from a camera every minute. That is vision, not recap.
Human resources (HR). Policy questions land in email and chat. Mapping A: work-grounded Q&A over the published leave policy the employee can already open. Mapping B: Copilot in Word to draft a job description the HR business partner edits. Mapping C is a miss: routing 4,000 résumés into stages. That is classification, not Copilot drafting.
Legal. Counsel needs a first-pass issue list on a vendor paper sitting in Word. Mapping A: Copilot in Word on the open file. Mapping B: Copilot in Outlook to draft a negotiation email the lawyer sends. The output is not a signed opinion. Consumer Copilot with a personal Microsoft account (MSA) is the wrong map for matter files.
Security. The chief information security officer (CISO) wants staff to summarize incident channels they already can open. Mapping A: Copilot in Teams on that channel's thread, with citations back to messages. Mapping B: Copilot in Word to draft the post-incident narrative from notes the responder uploaded. Mapping C is a miss: dumping unpublished vulnerability data into a consumer chatbot.
When Copilot is the wrong tool (Foundry teaser only)
AB-731 also measures Foundry Tools in a later chapter. You only need the boundary here so you do not over-map Copilot.
- Custom vision API. Photos, video frames, or badge images that must detect, count, or classify objects belong with Azure Vision in Foundry Tools. Copilot can write the standard operating procedure. It does not replace a vision endpoint on the plant floor.
- High-volume document intelligence. Extracting fields from tens of thousands of invoices, claims, or forms is a document-intelligence and search pipeline, not “open this PDF in Word and chat.” Copilot is the wrong unit of work when the metric is records per hour and structured output into a system of record.
- Model catalog. Choosing, evaluating, or hosting a specific foundation model for a custom app is Microsoft Foundry. Copilot does not expose a catalog of models for you to swap under Word. (Copilot Chat's model selector is a chat experience setting, not a Foundry catalog.)
If the exam stem says inspect images, extract fields at scale, or pick a model from a catalog, do not answer Copilot. Point to Foundry or Foundry Tools and move on. Copilot Studio, Graph extensibility, Researcher versus Analyst, and build-buy-extend are later bullets. This section only needs process-to-Copilot versus process-not-Copilot.
Grounding and permissions in the mapping
Microsoft's Copilot overview is explicit: experiences are powered by LLMs, grounding in web and/or organizational data, and access scoped by user permissions. Work-grounded Copilot can reason over mail, files, meetings, calendars, chats, sites, and other Microsoft 365 content the signed-in user is already allowed to open. It does not grant a new right.
That fact changes the process map:
- A manager asking “summarize the deal room” only sees files they can already open. Oversharing in SharePoint becomes a Copilot quality and risk problem. SharePoint Advanced Management shows up with the paid add-on later; the mapping lesson is clean permissions first.
- Web-grounded Copilot Chat can still help a process if the user pastes text, uploads a file, or works with open content in supported Outlook and Teams experiences. That is not the same as Graph-wide Q&A.
- Consumer Microsoft Copilot with an MSA is a personal assistant. It is not your tenant process map.
How this shows up for AB-731 candidates
Expect stems that name a verb and a workplace. Match Copilot when the verb is draft, recap, triage, analyze a sheet, generate a deck, or ask over permitted files. Match Foundry or Foundry Tools when the verb is see, extract at volume, or catalog a model. Keep a human in the loop whenever the artifact leaves the building.
Official Microsoft pages to reopen
- Study guide for Exam AB-731 — skills measured as of July 22, 2026, including map business processes and use cases to Copilot
- What is Microsoft Copilot? — apps, grounding, and in-app jobs
- License options for Microsoft Copilot — web-based versus work-based chat
- App and network requirements for Microsoft Copilot — Teams transcription, mailbox, and app prerequisites
A finance team wants a pipeline that extracts line items from 8,000 supplier PDFs each night and posts codes to the ERP. What is the first-fit mapping?
Which process is a first-fit map to Copilot for an operations vice president?
HR wants employees to ask what the parental leave policy says, using files those employees can already open. Which mapping fits Copilot?