To escalate this issue and provide effective feedback about Copilot and the QR code experience, use the in-product feedback mechanisms and include as much detail as possible about what happened.
- When Copilot gives an incorrect or misleading result (such as generating a QR code that doesn’t work after printing), submit feedback directly from that Copilot chat session using the thumbs-down button on the response.
- In the feedback form, include:
- That the QR code was generated for printed material as advised by Copilot.
- That the QR code failed to scan after printing, even after following Copilot’s improvement suggestions.
- How many times this occurred and any cost/impact (for example, printing costs).
- If using Copilot in a browser (for example, in Intune or another admin experience), developer tools in Microsoft Edge (F12 → Network → logs) can help capture the specific prompt/response sequence. This information can be shared with Microsoft Support if they request it.
- If working with Microsoft Support on this issue, they may ask for the Copilot session ID. This can be obtained via browser developer tools or, for Security/Intune-related Copilot experiences, from the Security Copilot portal’s prompt sessions view.
For future QR code scenarios, before committing to print, validate the QR code by:
- Scanning it directly from the screen with multiple devices.
- Printing a single low-cost test page and confirming it scans reliably.
- Optionally decoding the QR code with Copilot (for example, “Please decode this QR code”) to verify that the embedded configuration or URL is correct before distribution.
If the QR code is being used to connect a mobile app (such as a warehouse management or similar app), treat the QR code as sensitive configuration data and distribute only via secure channels while testing.
References: