Building and customizing solutions using Microsoft 365 Copilot APIs and tools
Report the specific Copilot response using its thumbs-down or Send feedback → Report a problem control; this attaches the report to the affected interaction, while the additional escalation path depends on whether the conversation used a personal Microsoft account or a work/school account.
Submit the interaction itself
- Open the original conversation.
- Select thumbs down on the inappropriate response—preferably on each response where the behavior continued.
- In the feedback form:
- Classify it as inappropriate, offensive, or harmful if those choices appear.
- Explain that Copilot continued using humor and emojis after being explicitly asked to stop.
- Include the approximate date/time and identify the sensitive topic.
- Permit diagnostic data or the conversation excerpt to be included if the form offers that option.
- If response-level feedback is unavailable, open Copilot’s … menu in the upper-right and select Send feedback → Report a problem. Microsoft documents this route for Microsoft 365 Copilot and distinguishes it from compliments and suggestions.^1^
Response-level feedback is the appropriate choice here because it associates the report with the relevant prompt-and-response exchange. In Microsoft 365 apps, selecting thumbs down opens a form for details about what went wrong.^2^
If this was consumer Microsoft Copilot
If signed in with a personal Microsoft account, submit the response-level feedback above. Because the concern involves inappropriate behavior around a sensitive subject, it can also be filed through Microsoft’s Report a Concern safety channel; Microsoft explicitly directs unsafe, inappropriate, or illegal Copilot content there.^3^
Include:
- The exact prompts and responses, or screenshots
- Date, time, time zone, platform, and app/browser
- A concise sequence showing each request to stop and each subsequent response
- No unnecessary personal, confidential, or identifying information
If this was Microsoft 365 Copilot at work or school
Ask the Microsoft 365 administrator to submit admin-initiated feedback or diagnostic logs for the affected user. This is the stronger escalation when the goal is investigation of the actual conversation rather than general product feedback.
The administrator can:
- Open the Microsoft 365 admin center.
- Go to Copilot → Settings → Other settings → Copilot diagnostic logs.
- Start collection, select the affected user, review the material, add a description, and submit it to Microsoft.
The submitted data can include prompts, generated responses, relevant content samples, and log files.^4^
Administrators can also select specific prompt-response pairs from chat logs, choose a date range of up to the previous 30 days, identify the Copilot product, and describe the issue.^5^
If the thumbs controls are absent, the organization may have disabled end-user feedback. In that case, the administrator-assisted route is the appropriate alternative; administrators can also review submitted end-user feedback under Microsoft 365 admin center → Health → Product feedback.^2^
For a continuing or business-critical problem, the administrator should additionally open a Microsoft support request through Microsoft 365 admin center → Support → Help and support, referencing the submitted feedback and its date/time.
Important platform exception
If this occurred in the Copilot app inside Teams, Teams’ normal Report this message command cannot currently report a Copilot-app message.^6^ Use Copilot’s own thumbs-down/feedback control, or have the Microsoft 365 administrator submit the diagnostic logs instead.
Microsoft Q&A cannot itself perform the requested conversation review because it is a public support forum rather than a channel with access to Copilot account data, session logs, or back-end investigation tools. The in-product report—and, for organizational accounts, the administrator’s diagnostic submission—is the correct path for review of this specific exchange.
References