A Copilot Studio topic calls a Power Automate cloud flow and needs to use the flow's output in a subsequent condition node. The flow returns a string value called 'approvalStatus'. How does the topic access this returned value?

For a Power Automate cloud flow to return values to a Copilot Studio topic, the flow must end with the 'Respond to a Power Virtual Agents or Copilot Studio' action (the specific action name may vary slightly by version), where you define named output parameters — such as 'approvalStatus' as a string.

In the Copilot Studio topic, when you insert the 'Run a flow' action node and select this flow, the node's output panel automatically lists all outputs defined in the flow's respond action. You then bind each output to a topic variable using the variable picker. After the flow runs, the topic variable receives the returned value and can be used in any subsequent node — including condition branches.

Option A (automatic global variable named after the flow) — outputs are not automatically stored in any variable. Binding to a topic variable is an explicit configuration step.

Option C (separate HTTP call to Dataverse) — unnecessarily complex. The native flow integration handles value return directly through the action node.

Option D (shared environment variable) — environment variables are configuration/settings containers, not runtime communication channels between flows and topics.

Exam chain: Flow defines output in 'Respond to PVA/Copilot' action → Copilot Studio action node exposes outputs → author binds output to topic variable → topic uses variable in conditions.