Skip to main content

​
What this means

An integration provides a channel or scoped access to another system. It is not a blanket authorization for an agent to read all data or perform every action. Read the integration’s current capabilities and security requirements before using it.

​
What to configure and check

Begin with What you can connect. Follow the guide for the specific integration: Have an authorized owner complete configuration. Confirm the account, scopes, connection state, and intended data flow. Store credentials only in the designated secure configuration, never in documentation, evaluation cases, or agent prompts. A guide or tile does not mean an integration is connected to your account. These integrations also do not imply a direct handoff into every Agents workflow. Verify the supported workflow path before relying on it.

​
How it connects

The connection provides access to sources; the workflow uses relevant information as context. Separate connection permissions from permission to perform an action and from any required approval.

​
Example

The Outlook add-in can work with the message you have open. Reading more of the conversation may require the optional Microsoft 365 mailbox connection. Do not assume an open task pane means the entire mailbox is available.

​
If a connection is unavailable

Follow its troubleshooting guide or ask your account team. An expired connection, an unprovisioned capability, and a missing permission are different problems. Do not work around them with copied credentials or a different customer’s account.