You have likely put a lot of work into your Power Pages site. There are help articles, product details, policy pages, and answers to common questions spread across the whole thing. The problem is that visitors do not always find the page they need. They click around, get lost, and give up. Generative answers in Copilot Studio fix this. Instead of forcing people to hunt through menus, you let an agent read your content and answer questions in plain words, right in the chat.
In this guide I will show you how to use generative answers to pull your Power Pages content into a Copilot Studio agent. I will keep things simple so you can follow along even if this is new to you.
What Generative Answers Actually Do
Generative answers let your agent find and share information from a source you choose, without you having to build a separate topic for every question. Normally, an agent only knows how to handle questions you wrote topics for. That is a lot of work, and you cannot predict every way a person might phrase things. Generative answers change that. You point the agent at a body of content, and when someone asks something, the agent searches that content and writes a clear reply based on what it finds.
This is a huge time saver. You do not have to guess every question in advance. You just give the agent good content to read, and it does the rest.
Pointing the Agent at Your Power Pages Content
The most direct way to surface your site content is to add your public website as a knowledge source. In Copilot Studio, open your agent and go to the Knowledge page. There you can add a source, and one of the options is a public website. You enter the web address of your Power Pages site, and the agent will use the pages at that address to answer questions.
This works well when your site is public and the content you want the agent to use lives on pages anyone can reach. The agent reads those pages and draws answers from them. So if you have a returns policy page, a visitor can simply ask “how do I return something” and get a clear answer pulled straight from that page.
Keep in mind that a public website source works with content that is openly visible. If your most useful content sits behind a login, you may want to also store that information in another source the agent can reach, like SharePoint or a set of files, and add that as a knowledge source too.
Two Places to Add Knowledge
You can add knowledge in two spots, and it helps to know the difference. The first is at the agent level, on the Knowledge page. Anything you add here acts as a general source the agent can fall back on for any question. The second is at the topic level, using a generative answers node inside a specific topic. Sources you set inside a node take priority over the agent-level sources for that part of the conversation.
A good pattern is to set your main Power Pages site as the agent-level source so it covers everything, then add tighter sources inside certain topics when you want the agent to focus. For example, a topic about billing could point only at your billing pages, so the answers stay sharp.
Adding a Generative Answers Node
If you want fine control, you can drop a generative answers node into a topic. This node tells the agent to search a source and build a reply at that exact point in the flow. You can even use a variable for the source address instead of a fixed one, which is handy if your site has different sections for different audiences.
A common setup is to use this node as a catch-all. You create a topic that runs when nothing else matches, and inside it you place a generative answers node. Now, whenever a visitor asks something your other topics do not cover, the agent quietly searches your Power Pages content and tries to help instead of saying “I did not understand.”
Keeping Answers Accurate
Generative answers are only as good as the content behind them. If your pages are out of date, the answers will be too. So before you turn this on, take a pass through the pages the agent will read. Make sure the facts are current, the wording is clear, and there are no half-finished drafts sitting on a public page. Clean content leads to clean answers.
It also helps to write your pages in plain, direct language. The agent does better when the source text is easy to read. Long, tangled sentences and heavy jargon can lead to weaker replies. Short paragraphs and clear headings give the agent solid material to work with.
Test With Real Questions
Once your source is set, test the agent the way a real visitor would. Ask the questions people actually send to your support team. Try different wordings of the same question, since people rarely phrase things the same way twice. Check that the answers match what your pages say and that the agent points people in the right direction.
If an answer comes back weak, look at the page it pulled from. Often the fix is on the content side, not the agent side. A clearer page gives a clearer answer. You can also adjust which sources a topic uses to steer the agent toward better material.
Wrapping Up
Generative answers turn your Power Pages content into something a visitor can simply ask about. You add your site as a knowledge source, decide whether to set it at the agent level or inside a topic with a generative answers node, and let the agent read your pages to build replies. Keep your content fresh and clear, test with the questions real people ask, and you give every visitor a faster path to the answer they came for. It is one of the easiest ways to make a busy site feel helpful instead of overwhelming.