Example context. Preview only. Nothing is submitted.
When to sendAt the end of a specific article, or from its feedback link while the content is still visible.
- 01
Did this article help?
Start with whether the article helped. A negative answer reveals optional reasons; the comment is available on both paths.
See the questions
- Was this article helpful?
- Ask about the article’s usefulness, not satisfaction with the whole product.
- What needs attention?
- Allow more than one content problem, and do not require a diagnosis before accepting a comment.
- What should the author know?
- Leave room for a specific example, correction, or positive feedback after either answer.
Using the answers
Review the answer against the article and its version. Multiple reasons can apply to one response, so their percentages need not sum to 100. Feedback from volunteers does not measure whether all readers completed their tasks.
When to choose another form
A reader needs a support reply or wants to report a product bug. Give those requests their own route.
Before you publish
Keep the article URL, language, and version with the response. In an embed, supply this from the page instead of asking the reader to retype it.
Send feedback to the content owner and provide a separate support link. Do not copy Microsoft’s privacy or response-time promises into your own form.