A generative answers node can search an agent’s configured knowledge sources and summarize relevant material for a user. The answer still needs review: Microsoft notes that responses can contain mistakes and that the system doesn’t verify the accuracy of the source content.
Where the node fits
Add the node to a topic when the response should use selected knowledge sources. You can also use generative answers as a fallback when a question doesn’t match an authored topic, if that behavior is enabled. If neither a topic nor generative answers handles the request, the Fallback system topic runs.
A node can search the agent’s knowledge sources or, with Search only selected sources enabled, a narrower set. The selected sources replace the agent-level sources for that node. They aren’t added to them.
Choose sources with care
Use sources that are current and relevant. If a source contains incorrect information, the generated answer can repeat it. When a response includes citations, check that the cited material supports the answer. If a source uses user authentication, test with users who have different access.
Test questions the node should miss
Test questions with known answers, questions that aren’t covered by the sources, and questions that should be handled by another topic or action. Review the answer and source attribution. Generative answers are nondeterministic, so repeated questions can produce different responses.
For a transaction, such as creating a ticket or updating a record, add an action or an agent flow. A generative answers node can explain information, but it doesn’t replace the operation that changes the record.
Sources
- Add a generative answers node, Microsoft Learn
- FAQ for generative answers, Microsoft Learn
💬 Comments & Suggestions
Share your thoughts, tips, or drop a useful link below.