Domain 1 of 3 · Chapter 10 of 22

Configure actions and connectors

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:

  • What one connector call is made of
  • Pick the operation by the side effect it has
  • Map values by type, not by what the preview looks like
  • The environment can refuse a combination
  • Whose credentials the call runs under
  • When the connection is broken and the logic is fine
  • Sharing a connection is sharing a credential
  • How these choices show up in questions

Where the credential for one connector call comes from

Decision axisEnd user credentialsMaker-provided credentialsProvided by run-only userA specific connection
Where it is setTool configuration: Details, Additional details, Credentials to useSame place, changed from the defaultRun-only settings of a cloud flow the agent callsRun-only settings of a cloud flow the agent calls
Identity the call usesThe signed-in user of the agentThe tool author's credentialsThe user who runs or invokes the flowThe connection the flow owner selected
Documented prerequisiteAuthentication enabled on the agent; it is the default for connector toolsAn authenticated channel first, then publish and test in that channelA supported authenticated agentA connection the owner owns or has permission to use
Pick it whenThe source system enforces per-caller permissionsThe resource is genuinely shared and authorization does not vary by callerEach caller's own access should decide what the flow returnsA shared service identity is wanted, or the environment uses customer-managed keys
Known constraintTurning agent authentication off stops these tools workingEvery caller inherits the author's accessNot available for cloud flows in customer-managed key environmentsEvery caller shares one credential, so audit trails name the connection owner

Decision tree

Is it a cloud flow the agent calls?No, a connector toolYesDoes the source system enforceper-caller permissions?Is the environment usingcustomer-managed keys?YesNoKeep End usercredentialsMaker-providedcredentials, on anauthenticated channelNoYesWhose access shoulddecide the result?Run-only:a specificconnectionThe callerA shared identityProvided byrun-only userA specificconnection
Cheat sheet

Cheat sheet

  • Select the connector operation that matches the intended side effect
  • Create a custom connector when the required API lacks a suitable operation
  • Map connector inputs and outputs with compatible types
  • Verify connector availability and data-policy classification
  • Choose each flow connection from the intended runtime identity model
  • Use specific connections for callable flows in CMK environments
  • Repair broken connections before troubleshooting flow logic
  • Share maker connections only with intended operators

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

References

  1. Use connectors in Copilot Studio agents
  2. Connectors overview
  3. Use a connection reference in a solution with Microsoft Dataverse
  4. Edit and manage your agent flow in the designer
  5. Add tools to custom agents
  6. Agent flows overview - Microsoft Copilot Studio
  7. SharePoint connector reference
  8. Work with variables - Microsoft Copilot Studio
  9. Manage data policies - Power Platform
  10. Data policies - Power Platform
  11. Configure user authentication - Microsoft Copilot Studio
  12. Create an agent flow as a tool
  13. Share a cloud flow - Power Automate
  14. https://learn.microsoft.com/en-us/microsoft-copilot-studio/configure-enduser-authentication
  15. Create and manage connections - Microsoft Copilot Studio
  16. Manage connections in Power Automate