Use fictional data first when teaching Copilot
Diesen Beitrag auf Deutsch lesen
Fictional files reduce privacy exposure and make Copilot accuracy testing measurable through planted errors and an answer key.
TL;DR
Use a fictional municipality or company for Copilot courses, based on the customer’s templates and tasks. Remove personal data, mark files as fictional, plant known errors, and keep an error-free control file so participants can test Copilot against an answer key without exposing real cases.
Original by Anders Jensen, on andersjensen.org. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: Use fictional files for shared Copilot exercises because participants may see uploaded content and files can remain in shared folders.
- Security/Compliance: Check personal and confidential information before any real files enter a course, because enterprise data protection does not control participant sharing.
- Leadership/Business: Tailor fictional cases to real templates and tasks so participants learn the method without shifting discussion into sensitive business cases.
Frequently asked questions
Does Microsoft enterprise data protection make real files safe for a Copilot course?
Enterprise data protection covers Microsoft’s handling of prompts and responses, but course sharing can still expose files to unsuitable colleagues.
How can a fictional municipality test Copilot answers?
Create documents with known planted errors, keep an answer key, and include one error-free control file to check whether Copilot reports false errors.
What should a company remove before using its own files on a Copilot course?
The company should remove personal and confidential information, then consider access differences and the absence of an answer key before sharing real files.