SAP Agent Interoperability
This repo contains a collection of hands-on recipes for connecting AI agents from non-SAP platforms - initially Amazon Web Services, Google Cloud and Microsoft - to AI agents running on the SAP Business AI Platform through the SAP Agent Gateway.
Enterprises run agents on SAP Business AI Platform alongside agents built on agent platforms from Amazon Web Services, Google Cloud, Microsoft or other. For those agents to collaborate on a business process, they need more than a shared protocol - they need identity federation, trust, governed and a controlled path into the SAP ecosystem.
These cookbooks and recipes are the how-to companion to the SAP Architecture Center reference architectures fo agent interoperability under: Integrating Joule Agents into Your Ecosystem. The Architecture Center explains the what and why of each integration pattern; the cookbooks here give you the concrete, step-by-step setup and implementation guides - including code samples - to reproduce it.
Definitions:
- Agent-to-Agent (A2A) is the protocol agents use to delegate tasks to one another.
- SAP Agent Gateway is the single, secured inbound hub through which external agents reach Joule Agents, Assistants, and Custom Agents on the SAP Business AI Platform. (User Guide)
- SAP Cloud Identity Services (IAS) brokers identity so every delegated task runs under the signed-in business user, respecting the SAP authorizations already in place.
Related reference architectures on the SAP Architecture Center:
Cookbooks
Before you start: make sure to complet the → Common setup - All cookbooks share the same one-time SAP-side onboarding - creating an Agent Gateway consumer system in SAP for Me and configuring authentication.
The platforms offer differrent ways to build agents, and they also differenciate in the way how the integration needs to be addressed. To date, we offer the following cookbooks for the platforms and integration patterns:
| Platform (alphabetical order) |
Tooling |
Integration pattern |
Cookbook |
| AWS |
Amazon Web Services (AWS AgentCore) |
On-behalf-of token exchange via AWS AgentCore Identity |
→ |
| GCP |
Google Gemini Enterprise |
Three-legged OAuth with a proxy agent on Google Agent Runtime |
→ |
| Microsoft |
Microsoft Copilot Studio |
Per-user token exchange via a Power Platform custom connector (Entra or direct IAS OAuth) |
→ |
Requirements
- SAP Business AI Platform, SAP Cloud Identity Services, and access to SAP for Me (cloud administrator role).
- An account on the third-party platform you want to connect (Microsoft Copilot Studio, Google Gemini Enterprise, or AWS).
- Platform-specific prerequisites are listed at the top of each cookbook.
Known Issues
See the detailed cookbook for known issues.
How to obtain support
Create an issue in this repository if you find a bug or have a question about the content.
For additional support, ask a question in SAP Community.
Contributing
If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation. See CONTRIBUTING for details.
Code of Conduct
Please read the SAP Open Source Code of Conduct.
License
Copyright 2026 SAP SE or an SAP affiliate company and agent-interoperability contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.