A consultant is extending a custom Copilot Studio agent used by a home appliance manufacturer's Dynamics 365 Sales reps. Reps already ask the agent about product specifications and get correct answers pulled from a SharePoint library. The sales manager now wants reps to be able to ask the agent to log a follow-up task on the opportunity record directly from the chat window, without switching to the opportunity form. Which capability should the consultant add to the agent?
Select an answer to reveal the explanation.
Short Explanation
Think about what the rep is actually asking for here: not more information, but for something new to get written into the system. Pulling up specs and summarizing a document is one kind of skill, and it is the one already working well. Creating a task tied to a specific record is a completely different skill, because it means reaching into the database and adding a row, not just reading from a library. A bigger memory for the conversation sounds appealing but it only helps the agent keep track of what was said, not perform an action. And a little card that just shows the current stage is purely informational, like a dashboard tile, it does not do anything on command. So the piece that is actually missing is a way for the chat to trigger a real write action against the opportunity, which is what lets the rep skip the form entirely and get the task logged from the conversation itself.
Full Explanation
The correct answer is D. Creating a task from chat is a write operation against Dynamics 365 Sales data, and Copilot Studio topics reach that data through an action calling the Dataverse connector, which can insert a task row and link it to the opportunity the rep is discussing. Option A is incorrect because generative answers only retrieve and summarize existing content from a knowledge source such as SharePoint; it cannot create records and is already handling the specification questions, which is a separate need. Option B is incorrect because a larger context window improves the agent's ability to track conversation history, not its ability to write data into Dataverse; memory and data-write permissions are unrelated capabilities. Option C is incorrect because an adaptive card is a display mechanism for showing existing information, such as stage, inside the chat surface; it does not perform an action like creating a task, so it would show data rather than log anything new. Only a topic with a Dataverse-connected action both understands the rep's request and executes the corresponding record creation.