Configuring Custom Connectors as Tools in Copilot Studio Agents
Short answer
1. Add the connector as a tool; 2. Create or reuse a connection for the connector; 3. Map topic variables to the tool inputs.
Question
A company has an existing custom connector that is approved and available in the environment. A builder wants an agent in Copilot Studio to call the connector during a conversation to retrieve information from an internal system.
To meet the business needs, the solution must meet the following requirements:
The agent must make the connector available for topic steps.
The agent must run the connector call with a valid connection.
The connector call must receive the required input values at runtime.
You need to configure the agent so the custom connector can be used as a tool.
What should you configure for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Key Takeaways
The question tests the distinction between registering a tool (availability), authenticating it (connection), and binding its parameters (variable mapping).
Learn how to configure a custom connector in Copilot Studio by adding it as a tool, establishing a valid connection, and mapping topic variables for runtime inputs.
Common mistake: Learners often confuse 'adding a tool' with 'mapping inputs'. Adding the tool makes it visible but does not provide authentication or data binding; these are separate configuration steps that must all be completed independently.
Expert Analysis
To successfully integrate a custom connector as a tool in Copilot Studio, the builder must address three distinct configuration layers: availability, authentication, and data binding. Each requirement maps to a specific action within the agent's tool configuration settings.
Requirement 1: Make the connector available for topic steps To expose the connector’s actions so they can be selected during conversation design, the connector itself must be registered with the agent. This is achieved by adding the connector as a tool. Without this step, the connector remains invisible to the topic editor, regardless of connection status or input mappings. Therefore, the correct configuration is to add the connector as a tool.
Requirement 2: Run the connector call with a valid connection Custom connectors often require authentication (such as OAuth or API keys) to access internal systems. In Copilot Studio, tools that require credentials need an explicit connection reference. The builder must create or reuse a connection instance associated with the custom connector. This ensures that when the agent invokes the tool, it passes valid credentials rather than failing due to missing authentication context.
Requirement 3: Receive required input values at runtime Tools defined in custom connectors have specific input parameters (e.g., 'CustomerID', 'StartDate'). These are static placeholders until mapped to dynamic data from the conversation flow. To satisfy this requirement, the builder must map topic variables (or other dynamic inputs like user prompts) to the tool’s input fields. This mapping happens at the tool configuration level, linking the connector’s expected parameters to the agent’s runtime context.
Official Reference
- https://learn.microsoft.com/en-us/copilot-studio/agent-tools-connectors-add
- https://learn.microsoft.com/en-us/power-platform/guidance/coach/connectors-best-practices
These links open the official vendor documentation in a new tab.
Exam Strategy
When configuring tools in Copilot Studio, always verify the three pillars: Visibility (Tool Added), Security (Connection Created), and Data (Inputs Mapped). If a requirement mentions 'available for use', think Tool Registration. If it mentions 'authentication' or 'valid connection', think Connection Reference. If it mentions 'input values' or 'parameters', think Variable Mapping. Do not assume that adding a tool automatically configures its inputs or connections.
Frequently Asked Questions
Do I need to create a new connection every time I add a custom connector?
What happens if I add a tool but don't map the inputs?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
Exam Topics Bob 👍 11. The agent must make the connector available for topic steps. - -> Add the connector as a tool in the agent. 2. The agent must run the connector call with a valid connection. - -> Create or reuse a connection for the connector. 3. The connector call must receive the required input values at runtime. - -> Map topic variables to the tool inputs.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.