Copilot / Copilot Accounts & Source Grounding
Copilot: ground a work question in the intended source
Choose one approved file or excerpt and identify its exact name and revision. Confirm it is actually available in the active Copilot experience.
Environment and inputs: Copilot user guide · Feature and source access depend on the active account, app and organization settings. Optional file or app steps have a text-excerpt fallback. No fixed model version, price or usage quota is assumed.
What you will make
A practical Copilot guide to ground a work question in the intended source. Use the sample input and prompt, then check the result. Use a fictional Microsoft 365 workplace task as the practice setting. Identify the file or excerpt that supports the requested result.
Prepare the source and scope
Choose one approved file or excerpt and identify its exact name and revision. Confirm it is actually available in the active Copilot experience. Open your available Microsoft Copilot experience and confirm whether it can read the intended work source.
Try this prompt
In Copilot, provide the prepared input, then send the following request. For real work, replace fictional details with approved facts.
Answer the approval question using only this source. Give the section reference and mark any unavailable information as Not established.Review the result
Open the cited source and confirm the answer applies to the same revision and organization. Record each correction and its supporting source.
If the answer is wrong or incomplete
Work-data access varies with account, licensing and configuration. If the file cannot be read, provide an authorized excerpt instead of relying on a title. If the active Copilot surface cannot access the file or app, paste an authorized excerpt into chat. Keep the same review criteria for the text-only workflow.
Practice and completion check
Repeat with one incomplete input. Check the answer against the review criteria, remove unsupported claims and save the prompt with its source version. This workflow has not been verified in a customer deployment.