An operations maker needs a Copilot Studio topic to create a Dataverse work order after the user confirms details. The team already has a Power Automate cloud flow that creates the work order. What is the correct way to invoke that flow from the topic?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Cloud flows are the agent's "hands" — you wire them in as an action, pass the form fields as inputs, and read the work order ID back as outputs. A Message node link or knowledge upload does not create records.
Full explanation below image
Full Explanation
Copilot Studio integrates with Power Automate by registering instant (manually triggered) cloud flows as actions/tools. The topic collects inputs, the flow runs with those parameters, and outputs return to the conversation for messaging or branching.
Option A is correct. Mapping topic variables to flow inputs and outputs is the supported pattern for transactional work like creating a Dataverse work order.
Option B is wrong because sending a user a link to run a flow outside the agent breaks conversational continuity, authentication context, and automated confirmation inside the topic.
Option C is wrong because knowledge sources are for retrieval-augmented answers, not for executing business process automation.
Option D is wrong because storing personal tokens in plain text environment variables is insecure and not the recommended Dataverse integration path; use connectors/flows with proper connection references and least-privilege identities.
Exam tip: Instant cloud flow + input/output parameters = standard plugin/action pattern for write operations.