Add a tool by using an existing custom connector
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:
- The connector already exists, so the work starts elsewhere
- Two grants, two portal pages, two failure symptoms
- Adding the operation as a tool
- The three sections of the tool configuration page
- Writing a description the orchestrator can act on
- Who the call runs as
- When the API changes underneath the tool
- How these choices show up in questions
Four ways to reach one REST API from an agent
| Property | Existing custom connector operation | Prebuilt connector operation | REST API tool (preview) | Send HTTP request node |
|---|---|---|---|---|
| Where it is defined | Power Apps maker portal, from an OpenAPI definition, Postman collection or from scratch | Published by Microsoft or a partner; nothing to define | Guided OpenAPI v2 upload inside Copilot Studio | Typed directly on one topic's canvas |
| Reuse beyond this agent | Copilot Studio, Power Automate, Power Apps and Azure Logic Apps; connectors created in Logic Apps are the exception and do not carry over | Copilot Studio, Power Automate, Power Apps and Azure Logic Apps | Environment Tools page, so other agents in the environment only | None; the configuration belongs to the topic that holds it |
| Prerequisite before the agent can use it | Connector published and shared with the maker (Can view or Can edit) | A licensed plan for premium connectors; standard connectors are on all plans | An OpenAPI v2 specification for the endpoints you want | The URL, method and, where needed, sample response data |
| Credential story | A Power Platform connection, End user or Maker-provided credentials | A Power Platform connection, End user or Maker-provided credentials | Configured on the tool when the API is added | Headers you populate yourself, ideally from environment variables |
| Classified by connector data policies | Yes; admins classify custom connectors alongside prebuilt ones as Business, Non-Business or Blocked | Yes; classified as Business, Non-Business or Blocked | No published connector classification; data policies classify prebuilt and custom connectors | No published connector classification; data policies classify prebuilt and custom connectors |
| Production readiness | No preview label on its product page | No preview label on its product page | Preview; Microsoft states it is not suited for production use | No preview label on its product page |
Decision tree
Cheat sheet
Unlock with Premium — includes all practice exams and the complete study guide.
Also tested in
References
- Custom connectors overview
- Add tools to custom agents
- Understand connector and REST API tools in Copilot Studio
- Custom connector parity in data policies
- Share a custom connector in your organization
- Add prebuilt and custom connector tools to an agent
- Use connectors in Copilot Studio agents
- Configure user authentication for tools
- Configure authentication for connector tools
- Create and manage connections
- Copy an environment