Module 00 · Lesson 00.2
Build a practice setup that cannot hurt real work
Prepare an approved Copilot sign-in, fictional practice material, a course folder, and a simple review log before you bring AI anywhere near customer or company data.
A safe setup removes avoidable decisions
New learners often paste the nearest real document because it feels practical. A dedicated practice kit lets you learn attachments, prompts, Pages, app workflows, and review habits without testing policy boundaries.
Account
Use the surface your organization or subscription provides
Record the active identity before each session. A work browser profile can still contain a personal sign-in, and the reverse is also possible.
Material
Practice with synthetic but realistic data
Use invented names, organizations, figures, messages, and decisions. Synthetic data should still contain the ambiguity you need to learn from.
Review
Keep the input, first output, corrections, and final result
A review log turns “Copilot seemed helpful” into evidence about what worked, what failed, and what you changed.
Your minimum setup kit
You do not need every Microsoft 365 app or a paid Copilot add-on. Start with the approved surface you have and a place to save your practice.
| Item | Required now | Optional later | Do not use for practice |
|---|---|---|---|
| Sign-in | One known personal or work/school identity | A separate browser profile for another approved identity | A shared account or an identity whose ownership is unclear |
| Copilot surface | Approved chat or in-app experience | Pages, Notebooks, agents, or additional apps | A consumer surface for proprietary work information |
| Source material | Fictional notes and documents | Organization-approved training files | Customer, employee, financial, medical, legal, regulated, or confidential data |
| Storage | A course folder or notebook | A Copilot Page when available | An externally shared folder with unknown access |
| Review record | A simple table of task, source, issue, correction, and result | A team prompt-and-evaluation log | Only the final answer with no source or correction history |
Create a course workspace
The tool does not matter. Use a local folder, OneDrive folder approved for training, OneNote section, or another place your organization permits.
- Create one parent folder. Name it “Copilot course practice” and add the date you started.
- Add four subfolders or sections. Use “Sources,” “First outputs,” “Verified outputs,” and “Review log.”
- Save the fictional notes from Lesson 00.1. Label them clearly so nobody mistakes them for a real project record.
- Create a review log. Add columns for date, task, Copilot surface, source, issue found, correction, and final disposition.
- Write the practice-data rule. State what you may use, what you may not use, and who decides when the answer is unclear.
For this course I will use:
- fictional people, companies, messages, meetings, and figures;
- public information that I am allowed to reuse;
- organization-approved training files, when explicitly provided.
I will not use:
- customer, employee, applicant, student, patient, financial, legal, security, credential, regulated, confidential, or proprietary information;
- files whose permissions or ownership I do not understand.
When I am unsure, I will stop and ask: [role or policy owner].Add a small synthetic practice pack
Copy these scenarios into your Sources folder. They support later lessons without containing real information.
Writing
Northstar Bikes onboarding note
A fictional bike retailer is onboarding 12 store managers to a new returns process. The note must be clear, calm, and under 180 words.
Data
Four-week support table
Invent ticket counts, response times, and satisfaction scores for four weeks. Include one missing value and one visible outlier.
Meetings
Pilot launch notes
Reuse Lesson 00.1’s notes, including the absent owner, missing date, and unresolved security dependency.
Run the pre-session check
It takes less than a minute and prevents the most common account and data-boundary mistakes.
- I can name the active account and whether it is personal or work/school.
- I recognize the Copilot surface and its current product label.
- I know which source I will provide and why I am allowed to use it.
- The practice file is fictional or explicitly approved for training.
- I know where the first output and review notes will be saved.
- I know who to ask when policy, permission, or sensitivity is unclear.
Deliverable and quality check
Your workspace is ready when another learner could understand the boundary without relying on your memory.
Pass
- The active identity and Copilot surface are recorded.
- Practice files are clearly marked fictional.
- The review log preserves first output and correction history.
- The prohibited-data list is specific.
- An escalation owner or policy is named.
Revise
- The setup says only “do not share sensitive information.”
- Real email or meeting content is used because it is convenient.
- Personal and organizational accounts are mixed without a record.
- Only polished final outputs are saved.
- There is no owner for a policy question.
Knowledge check
Why keep the first output after you correct it?
The first output shows the failure mode. Keeping it lets you compare prompts, corrections, and final quality instead of remembering only the successful result.
Is public information always safe to paste into any Copilot surface?
No. Public availability does not settle copyright, license, confidentiality, organizational policy, or intended-use questions. Confirm that you may reuse it and cite the source when appropriate.
What should you do when you cannot classify a file?
Stop. Do not upload or paste it. Ask the named policy, privacy, security, legal, records, or data owner who can make that decision.
Official Microsoft sources
- Microsoft account vs work or school account
- Enterprise data protection in Microsoft 365 Copilot and Copilot Chat
- Validate Copilot output before you act on it
Verified July 30, 2026.