Bring an agent into the tools you use.
An early-access service in development for tasks that span business applications. An agent can retrieve permitted information and prepare a proposed action; enabled actions stay within agreed permissions and review points.
Early-access services. Scope, integrations and pricing agreed before work starts.
Example pilot: assemble a support handoff from approved records. Begin with a draft for review, then consider specific actions after evaluation.
Retrieve approved information and prepare a draft without changing source records.
Test ordinary cases, missing access, misleading content and service failures.
Enable selected operations and apply the agreed review before execution.
Record results, handle exceptions and follow the recovery plan for each action.
Choose a task such as preparing a support summary, drafting a record update or assembling a review pack. Existing applications remain the systems of record.
Confirm that the required operations are available through the vendor's API, your plan and your permissions. Start with information retrieval and draft outputs; add particular writes only after evaluation.
Test missing records, stale information, misleading source content and unavailable APIs. Review both output quality and whether the agent stays inside the permitted task.
For an enabled write, check the destination, proposed change and required approval before execution. Record the result and agree how to stop further work or revoke access. Recovery depends on the connected application and action.
These examples describe vendor capabilities. Each connection still needs assessment for your pilot.
Google Drive supports access to files a user selects or shares with an app. That access is not inherently read-only, so a pilot must also define which operations the agent is allowed to perform.
Google: Drive access scopesMicrosoft Graph distinguishes acting for a signed-in user from application access without one. Delegated access is bounded by both the app's permissions and the user's own access.
Microsoft: Graph permissionsSlack provides an API for posting messages, subject to messaging permission, destination access and rate limits. A pilot can keep a handoff as a draft until the agreed reviewer approves sending it.
Slack: posting messagesDocumentation checked 15 October 2026.
Each pilot needs a clear agreement on access, data handling, approval and exceptions.
Related guidance: OWASP AI agent security and NIST generative AI risk management. Controls and responsibilities are agreed for each engagement.
Connections are assessed per pilot. The Google Drive, Microsoft 365 and Slack details describe vendor capabilities, not a catalogue of integrations already delivered by tech automation services.
Your applications can stay in place. The proposed agent layer uses approved APIs or adapters, subject to the vendor's terms, available operations and your access policies.
No. A pilot may use a direct API or another adapter. MCP is an optional tool interface; it does not replace application permissions, approval checks or evaluation.
Bring one cross-application task, the apps it uses and the actions you want an agent to prepare. We will assess the access, integration and review requirements before proposing a pilot.