Summary

  • 2 minutes

In this module, you explored how to build and connect a standalone workflow to an agent in Microsoft Copilot Studio, and how to test it across the full range of expected behaviors. You can now:

  • Decide when to use agent reasoning and when to use a deterministic workflow, and apply a clear decision framework to new agent designs.
  • Design a workflow contract with named trigger inputs, precise descriptions, and response outputs that the agent uses after the workflow runs.
  • Create a standalone workflow in the Copilot Studio Workflows experience, configure the agent-callable trigger, and navigate the draft-to-published lifecycle.
  • Add a connector action between the trigger and response steps using dynamic content from the trigger inputs, and configure the response outputs.
  • Add a published workflow to an agent as a tool, configure input filling, require end-user confirmation before consequential actions run, and reference the tool in the agent's instructions.
  • Test a workflow tool across success, missing-information, cancellation, and failure paths, and use workflow activity to diagnose connector-level problems.

In the exercise, you created the Contoso Task Notification Agent and the Send Task Notification Email workflow. The workflow uses the Office 365 Outlook connector to send a structured email notification with four defined inputs and a confirmation output. You added the workflow as a tool with end-user confirmation enabled and verified the full test coverage required before releasing a consequential action.

What you learned

  • Plan workflow automation: Choose a workflow when execution must be consistent or auditable, and define clear trigger inputs and response outputs before building it.
  • Build and publish a standalone workflow: Use dynamic content to map trigger inputs to connector fields. Agent-callable workflows must use When an agent calls the flow, respond in real time, and be published.
  • Add and configure a workflow tool for an agent: Use a clear tool description to guide tool selection and end-user confirmation to protect users from consequential actions.
  • Test and troubleshoot workflow behavior: Run all four test paths before releasing a tool. Use the Activity panel to identify the exact step and error when a workflow fails.

Learn more