Copilot: turn an incident description into a useful triage note

What you will make

A practical Copilot guide to turn an incident description into a useful triage note. 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

Collect observed symptoms, start time, affected users and recent changes. Sanitize hostnames, access tokens and personal data. 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.

Create a triage note from these observations. Separate confirmed facts, hypotheses and next questions. Suggest read-only checks first and do not claim a root cause.

Review the result

Each hypothesis should name the observation that would support or reject it; the impact should match the report. Record each correction and its supporting source.

If the answer is wrong or incomplete

Repeated symptoms do not establish causation. Keep a suspected update or network issue labeled as unconfirmed. 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.