Heads up: this browser is blocking local storage, so your progress will not be saved after you close the page.
Lab 11 · Module 3 · Automate and Synthesize
Analyst, the Built-In Agent
Step 1: why this is needed and what each entry does
Switch on the data agent (Open Analyst). Analyst writes and runs code to analyze a spreadsheet and shows its working. Plain chat estimates.
- Analyst
- A built-in agent for data. It runs Python in the background and can show the code, which is how you check it. Shares a monthly run limit with Researcher.
- No Analyst entry
- Licensing or admin settings. Path B does the same lab with the data as text in Copilot Chat.
Step 2: why this is needed and what each entry does
Give it the real numbers (Attach the data file). Analyst needs the spreadsheet itself, not a description of it.
- Attach content
- Analyst accepts CSV and XLSX. One clean table per file works best.
Step 3: why this is needed and what each entry does
Ask one careful question (Send the prompt). The prompt says what to produce, what to cite, and what to do when the files are silent. A vague question gets a confident guess.
- Copy prompt
- The prompts follow the C.H.A.T. frame: Context, How come, Assign task, Type of output. Copy them whole; a shortened prompt drops the guardrails.
- Show the steps
- The code is the method. A result without a method cannot be checked.
Step 4: why this is needed and what each entry does
Prove one figure yourself (Check one number by hand). One hand calculation tells you whether the method is right. June is the test case.
- Why June
- Completion over 100% looks like an error but is real: a backlog was cleared. A tool that silently caps it at 100% is wrong.
Step 5: why this is needed and what each entry does
Decide what the numbers can carry (Check and record). Numbers that match your hand check can go in a briefing, with the limitation you found.
- Five Checks
- Source: which file. Verification: did you open it. Context: did the caveats survive. Resilience: would it still hold if the data changed. Authorized Owner: who signs off before anyone acts on it.
The prompts for this lab: copy and paste
Same prompts as in the Prompts section and the Do it steps. Paste each one whole.
Overview
What we are doing
- The situation
- The monthly request numbers (received, completed, days to resolve) need a quick analysis before the review. This time Analyst, Copilot's data agent, does the math and shows its code.
- Your role
- You are the analyst who checks the numbers before they go to a manager.
- Your task
- Ask Analyst (the Copilot agent that analyzes data by writing and running code) to analyze the same data. Then check its work. You can open the code it wrote.
- Files you need
- File 06 (06_Service_Request_Data.xlsx).
- Done when
- You have Analyst's results and flags, and you matched at least one of its numbers to a calculation you did by hand.
- Why it matters
- Analyst is fast and sounds sure. Matching one number to your own hand check tells you whether to trust the rest.
- Good to know
- Analyst is included with the Microsoft 365 Copilot license. If you do not see it, use Path B (Copilot Chat only). If you already did Lab 6 (Excel), compare with that hand check too.
Check before you finish
- Do Analyst's numbers match the one you checked by hand? June: 455 / 390 x 100 = 116.7%.
How to do it: the basic steps
5 steps, one screen each. Select the ? on a card for why the step is needed and what each entry does.
- Switch on the data agent (Open Analyst)
Why: Analyst writes and runs code to analyze a spreadsheet and shows its working. Plain chat estimates.
- m365.cloud.microsoft
- Agents
- Analyst
Sign in at m365.cloud.microsoft with your work account. Select Agents in the left pane, then Analyst. No Analyst? It needs a Microsoft 365 Copilot license; use the Path B steps.
- Give it the real numbers (Attach the data file)
Why: Analyst needs the spreadsheet itself, not a description of it.
- +
- Attach content
- Upload or OneDrive
- file 06
Select the + in the prompt box, then Attach content. Choose Upload or OneDrive and pick 06_Service_Request_Data.xlsx (the .csv works too). It shows as attached.
- Ask one careful question (Send the prompt)
Why: The prompt says what to produce, what to cite, and what to do when the files are silent. A vague question gets a confident guess.
- Copy prompt
- Paste
- Send
Select Show the prompts below, then Copy under Analyst prompt (Path A & B). Paste it into the chat box and select Send. Analyst shows its steps, sometimes with the code it ran. Expand them if offered; that is your audit trail.
- Prove one figure yourself (Check one number by hand)
Why: One hand calculation tells you whether the method is right. June is the test case.
- June row
- Completed / Received x 100
- Compare
June: 455 completed divided by 390 received, times 100, is 116.7%. Does Analyst's June completion rate match? If you did Lab 6, compare with your Excel column.
- Decide what the numbers can carry (Check and record)
Why: Numbers that match your hand check can go in a briefing, with the limitation you found.
- Match?
- One limitation
- Five Checks
Do the numbers match your hand check? Name one limitation of the data (for example months with missing values). Run the Five Checks: Source, Verification, Context, Resilience, Authorized Owner. Then mark the lab steps done.
= why the step is needed and what each entry does. Like this = something you select or click. Like this = something you type or paste.
Microsoft changes these screens often; a label on your screen may differ slightly. If a button is missing, your organization may not have turned the feature on: use the Path B steps.
Where to click
- Copilot
- Agents
- Analyst
- +
- file 06
Watch the demo video
Demo C: Analyst calculates completion rates, flags June and August, and charts them
Chapters (select one to jump there):
Step-by-step narration (transcript)
Recorded in consumer Copilot with supplied file 06. Compare its numbers with one you check by hand. No audio. Captions are WebVTT: captions .vtt · chapters .vtt · MP4 (601 KB)
Watch where to click Real screenshots (consumer Copilot) + illustrations
The demo shows where to click, step by step. Steps marked Real screen are screenshots from Copilot (consumer version); your work Microsoft 365 Copilot may look slightly different. The other steps are drawings. The list under the player is the same steps as text.
Annotated screenshots (consumer Copilot, opens the image): chat home empty analyst pinned plus button menu
Do it: step by step
Check off each step as you go. Your progress saves in this browser.
Prompts: weak vs strong
Follow the brackets. The detailed prompt is built from the four C.H.A.T. parts: [Context], [How come], [Assign task], and [Type of output]. Keep the labels when you paste it; Copilot reads them fine, and they help you check that each part is there.
Compare a vague prompt with a detailed, source-checkable prompt. The activity below separates the request from the Guardrails (limits you add, such as "cite the source" or "do not decide for a person") you need before use.
Analyst prompt
Analyze this data.
[Context] I shared file 06, the monthly service request data (requests received, completed, and days to resolve by month). [How come] I want to check its work against one number I calculate myself before I trust the rest. [Assign task] Using the file 06 data I shared, analyze monthly changes in requests received, average days to resolve, completion rate, and first-contact resolution share of completed requests. [Type of output] Identify trends and unusual values. Do not infer causes the data does not support.
Why the detailed version works (letter by letter)
- CContext
I shared file 06, the monthly service request data
- HHow come
I want to check its work against one number I calculate myself
- AAssign task
analyze monthly changes in requests received, average days to resolve, completion rate, and first-contact resolution share of completed requests
- TType of output
Identify trends and unusual values
- GGuardrail: keep it off-limits
Do not infer causes the data does not support
Optional chart follow-up
[Context] Same Analyst chat, with file 06 and the Analyst results. [How come] A chart makes the trend easier to see and to check against the numbers. [Assign task] Make one simple line chart of Avg Days to Resolve by month from file 06. [Type of output] One line chart, with one point for each month.
Send this after the Analyst prompt if you want a chart. The Analyst prompt alone may not draw one.
Quiz
Self-check only. Answers stay on your device.
Path B Text Pack and downloads
Download the practice files (Path A)
Path A (full access): these downloads are for you. Save them where Copilot can reach them (OneDrive for the Office app labs). Path B: nothing to download; the files are below as text, ready to paste. Path C: nothing to download; read the text below when you check sources.
Path B (Chat only): short steps
- Select Copy all files + prompts for this lab below, paste it into the chat, and select Send. It includes the Analyst prompt and the optional chart follow-up.
- Check June by hand: 455 / 390 x 100 = 116.7%. Does Copilot's number match?
[Context] I shared file 06, the monthly service request data (requests received, completed, and days to resolve by month). [How come] I want to check its work against one number I calculate myself before I trust the rest. [Assign task] Using the file 06 data I shared, analyze monthly changes in requests received, average days to resolve, completion rate, and first-contact resolution share of completed requests. [Type of output] Identify trends and unusual values. Do not infer causes the data does not support.
[Context] Same chat as the Analyst prompt, with the table I pasted from file 06. [How come] A chart makes the trend easier to see and to check against the numbers. [Assign task] Make one simple line chart of Avg Days to Resolve by month from the table I pasted. [Type of output] One line chart, with one point for each month. If you cannot make a chart, give a month-by-month table instead.
File 06 - Service Request Data (spreadsheet as text) (1,366 characters)
FICTIONAL TRAINING FILE - The City of Fernhollow, its staff, residents and data are invented for the CPS HR Microsoft 365 Copilot workshop. Do not use real work data. FILE 06 - SERVICE REQUEST DATA (text version of the spreadsheet) Sheet: Monthly Data (Excel table name: ServiceRequests) Blank = no data; 0 = measured and zero. Ending Backlog = Beginning Backlog + Received - Completed. Month | Beginning Backlog | Requests Received | Requests Completed | Resolved on First Contact | Avg Days to Resolve | Escalated | Ending Backlog | Notes Jan 2026 | 120 | 410 | 395 | 150 | 6.1 | 12 | 135 | Feb 2026 | 135 | 398 | 380 | 141 | 6.3 | 9 | 153 | Mar 2026 | 153 | 445 | 412 | 160 | 6.8 | 0 | 186 | No escalations recorded (confirmed zero) Apr 2026 | 186 | 460 | 418 | 155 | 7.4 | 14 | 228 | May 2026 | 228 | 472 | 430 | 149 | 8.0 | 18 | 270 | Jun 2026 | 270 | 390 | 455 | 170 | 8.4 | 21 | 205 | Focused effort to clear older requests Jul 2026 | 205 | 430 | 418 | 162 | 7.6 | 15 | 217 | Aug 2026 | 217 | 455 | 440 | | 7.2 | | 232 | Case-system migration: first-contact and escalation data not captured (blank = no data) Sep 2026 | 232 | 468 | 452 | 181 | 6.9 | 13 | 248 | Lab 6 measures: Completion Rate = Requests Completed / Requests Received x 100 First-Contact Resolution Share of Completed Requests = Resolved on First Contact / Requests Completed x 100
Path C (Watch and verify): Compare the instructor's Analyst numbers with your own hand check.
Debrief question: Why use Analyst instead of regular chat for this?


