Domain 1 of 3 · Chapter 12 of 22

Add input and output parameters

Unlock the complete study guide + 1,040 practice questions across 16 full exams.

Bundled into the existing Designing and Building Integrated AI Agent Solutions in Copilot Studio premium course — no separate purchase.

14-day money-back guarantee — no questions asked.

Included in this chapter:

  • Two surfaces, one parameter contract
  • Declaring an input on the trigger
  • How the orchestrator fills an input at runtime
  • Overriding an input with a Custom value
  • Keeping credentials out of the input contract
  • Declaring outputs on Respond to the agent
  • One output schema on every branch
  • Diagnosing a parameter defect at the boundary
  • How these choices show up in questions

Four ways a value reaches an agent flow input

ConsiderationDynamically fill with AICustom valueTopic Question nodeNot an input at all
Who supplies the valueThe orchestrator, from available context such as the user's messageThe maker, at design timeThe user, answering an authored questionThe connection or the environment configuration
Does the agent ask the user?Only when no appropriate value is found in contextNever; an overridden input isn't asked aboutAlways, on the authored pathNo
What you enterNothing; you author the name, Identify as type and descriptionA literal value, a variable, or a Power Fx formulaThe question text, and the variable it fillsA connection reference or an environment variable
Orchestration modeGenerative orchestrationEither modeEither mode, and the only route under classic orchestrationEither mode
Custom entities (closed list, regex)Not supported as tool input parametersNot applicable; the maker sets the valueSupported; this is the documented workaroundNot applicable
Files uploaded in chatDoesn't work for file inputsThe route that works: a Power Fx formula over System.Activity.AttachmentsA Question node that identifies a File, passed on to the toolNot applicable
Reach for it whenThe value changes per request and users state it in their own wordsThe value is fixed, or derived rather than asked forThe value needs a closed list or a regex, or the agent runs classic orchestrationThe value is a secret, a credential, or environment configuration

Decision tree

Is the value a credential or anenvironment-specific setting?yesNot an input at all:connection and credential mode,or environment variablenoIs the value fixed, or derivablewithout asking the user?yesTrigger input,Fill using = Custom valuenoDoes it need a closed list or a regex,or is orchestration classic?yesTopic Question node,passed into the toolnoTrigger input,Fill using = Dynamically fill with AI
Cheat sheet

Cheat sheet

  • Define flow inputs on When an agent calls the flow
  • Give tool inputs clear names and descriptions
  • Choose whether each input is dynamically filled or explicitly set
  • Do not collect secrets as conversational tool inputs
  • Define returned values on Respond to the agent
  • Keep output names and types consistent on every response path
  • Inspect input and output values in the activity map

Unlock with Premium — includes all practice exams and the complete study guide.

References

  1. Create an agent flow as a tool - Microsoft Copilot Studio
  2. Add tools to custom agents - Microsoft Copilot Studio
  3. Work with variables - Microsoft Copilot Studio
  4. Pass files to agent flows, connectors, and tools - Microsoft Copilot Studio
  5. Orchestrate agent behavior with generative AI - Microsoft Copilot Studio
  6. Additional settings for inputs of topics and tools - Microsoft Copilot Studio
  7. Review agent activity - Microsoft Copilot Studio
  8. Remove sensitive data - Microsoft Copilot Studio
  9. Manage topic inputs and outputs - Microsoft Copilot Studio
  10. Modify an existing flow to use with an agent - Microsoft Copilot Studio