SoftTech AI Registry
Microsoft · Microsoft Copilot Studio

Connector Tools

Copilot Studio agents can be given Power Platform connector tools, allowing the agent to invoke connector actions that read from and write to connected Microsoft and non-Microsoft services.

Recorded characteristics

Function
Microsoft documents Power Platform connectors as proxies or wrappers around APIs that let Copilot Studio communicate with other apps and services. A maker adds connector tools to an agent at agent level (Tools) or inside a topic; each connector tool represents a specific action or operation the agent performs using that connector. With generative orchestration, active by default, the agent can select and call the appropriate tool automatically in response to a user request or an autonomous trigger; tools can also be called explicitly from a topic. Connectors include prebuilt standard connectors, premium connectors and custom connectors built against any publicly available API.
Data access
Access depends on the connector selected, the specific tools or actions exposed to the agent, and the authenticated connection. Microsoft lists connectors to Microsoft services such as Office 365, SharePoint and Dynamics 365 and to non-Microsoft services such as Salesforce, Google services and ServiceNow. The ServiceNow connector reference documents creating, reading and updating records including incidents, questions and users. Access is not unrestricted: it is bounded by the connection's credentials and the underlying service's own permissions, and by Power Platform data policies where configured.
Actions
Can take actions
External actions
Yes
Human confirmation
Not established
Permission basis
Mixed
Administrative control
Documented controls include which connector tools a maker adds to the agent, connection configuration and status on the agent's Connection Settings page (connected, not connected, deactivated, expired, stale), the authentication mode chosen for the tool (agent author authentication or user authentication, with user credentials the default), maker-provided credentials configuration, connection sharing in Power Apps, on-behalf-of parameter sharing, and Power Platform data policies configured in the Power Platform admin center. Microsoft states data policy enforcement applies to all tenants in real time and lists blocking the use of Power Platform connectors as tools and requiring user authentication among common data policy use cases; connectors are classified into business, non-business and blocked data groups.
Default state
Not established
Availability
Recorded at the platform level. Connector availability varies by connector: prebuilt standard connectors are included with all Copilot Studio plans, premium connectors are available in select Copilot Studio plans, and custom connectors can be created for other public APIs. Individual connector reference pages state the service class and regional availability per product; for example the ServiceNow connector is listed as Premium for Copilot Studio, with regional exclusions. Some connector features are documented as preview.
Licensing
Copilot Studio licensing governs access to the platform and to premium connectors; Microsoft directs readers to the current Copilot Studio licensing and billing documentation. Premium connectors require select Copilot Studio plans.
External model or provider
Not publicly established for this capability. Microsoft does not document a specific named model that governs connector tool selection or execution; orchestration behaviour is described functionally (generative orchestration) rather than by model identity, and model configuration can vary.
Limitations and uncertainty
Documented operations vary by connector; each connected service exposes different actions and may impose its own limits, licensing and regional restrictions. Authentication behaviour differs between agent author authentication and user authentication, and user authentication for tools is only supported on some channels (for example custom website, Microsoft Teams, SharePoint and Omnichannel live chat, but not Azure Bot Service channels, demo website, Facebook or mobile app). Single sign-on is not supported for connectors when an agent uses custom Microsoft Entra authentication and is deployed to Teams. Connector-level known issues exist, such as the ServiceNow Create Record action being unable to set the full record description. Copilot Studio does not store credentials; tokens can expire or be revoked. No Copilot Studio-enforced per-action human confirmation for connector tool execution is documented, and the default operational state of the mechanism is not stated.

Evidence