AgentenCode
DEEN
Enterprise AI & agent governance

SAP opens its agents to outsiders. A2A is live, but freedom has limits

SAP opens inbound A2A calls to Joule agents, yet outbound collaboration is still on the roadmap. Why German enterprise users demand costs and proof.

Original AgentenCode editorial illustration; conceptual visualization, not a real product screenshot or independently measured architecture.
Original AgentenCode editorial illustration; conceptual visualization, not a real product screenshot or independently measured architecture.
DIRECT ANSWER

SAP says inbound Agent2Agent calls to supported SAP agents reached general availability in October 2026. That does not mean bidirectional agent collaboration is generally available. Germany's SAP user association DSAG calls for predictable spending and clear rollout dates.

EDITORIAL SOURCE AUDIT

Sources and open questions

  1. Original source:

    Inbound A2A availability and planned outbound integration

    The vendor documents the stated scope and timing.

    Read primary source ↗

  2. Evidence limit:

    Independent operational proof missing

    Inbound A2A is now generally available, but SAP's outbound integrations and parts of its wider governance stack are still planned.

Inbound A2A is now generally available, but SAP's outbound integrations and parts of its wider governance stack are still planned.

Source check at a glance

Confirmed scope

Shipped: inbound A2A calls to eligible SAP agents with customer-configured access.

Open evidence

Not yet general: outbound A2A/MCP and broader Enterprise AI Gateway; actual costs and tenant controls need proof.

The agent economy finally faces a practical interoperability test

SAP's October 27 announcement marks a useful change in enterprise AI: assistants built outside SAP can invoke supported SAP agents through an official, governed Agent2Agent (A2A) interface. The company says inbound interoperability reached general availability in October. Employees could ask their preferred assistant to initiate an SAP process without continuously changing business applications.

The headline is easy to overread. Inbound A2A is the component SAP says it shipped; outbound delegation to external agents and tools exposed through MCP remains part of a future direction. A universally interoperable, bidirectional agent network is not suddenly available simply because one gateway now accepts standardized requests.

Discovery is not permission to execute

SAP describes three layers. Agentic Resource Discovery (ARD) advertises relevant capabilities and AgentCards with A2A endpoints. An external assistant then communicates through A2A. The Agent Gateway checks the requesting client and applies the configured agent permissions. SAP explicitly says discovering an agent does not grant the right to invoke it. Customer administrators must onboard external clients and establish trust and identity using SAP Cloud Identity Services.

The vendor's purchasing example has an outside assistant delegate an urgent sourcing task to an SAP sourcing agent, which prepares a request for proposal in SAP Ariba. A procurement employee reviews and approves the draft before creation. That is an illustrative workflow, not an independently audited success rate. Actual behavior depends on the permitted agents, business roles, tenant configuration and the handling of errors and revocation.

Why SAP's documents sound more optimistic than some architecture pages

Readers may encounter conflicting availability statements. The fresh October 27 SAP Architecture Center update calls inbound A2A generally available, while older reference designs still warn that the Agent Gateway or bidirectional collaboration is not generally available. Those pages can describe different release stages and integration directions; a buyer should not silently turn either into a promise that every connector or use case works today.

The larger SAP TechEd announcement also covers tools and governance capabilities still on the roadmap. The German-speaking SAP user association DSAG reports that the broader Enterprise AI Gateway, intended to centralize authentication, policies, routing, monitoring and auditing, is planned for the first quarter of 2027. Standardized agent messages are one component; comprehensive operational governance is another.

The price of an 'open' enterprise architecture

DSAG welcomes interoperability and non-SAP data support but says buyers need a dependable commercial model. Many TechEd capabilities are scheduled for 2027, while selected customers can run custom agents on SAP-managed Joule Studio runtime for a time-limited promotion through December 2026. A temporary free deployment does not settle the cost of repeated agent invocations, model usage and chains that span several providers.

Each cross-platform task may cross distinct identity, audit and billing boundaries. A successful demo does not show who owns spending across agents, how a revoke command propagates, or whether every data movement is permitted in a regulated environment. SAP's claims need to be mapped against an organization's precise entitlements and hybrid deployment constraints.

Our view: prove the denied action, not just the successful demo

We regard inbound A2A general availability as more consequential than another autonomous-enterprise slogan. Separating discovery, permission and task execution is a sound design principle. But a standard becomes genuinely useful when customers can swap components and retain clear governance without unpredictable integration costs. Otherwise vendor lock-in moves from the application screen to the gateway.

Our suggested pilot starts with one harmless SAP process and an external assistant with minimal access. Attempt an unauthorized second-agent invocation, revoke permission during a running task, verify human approval and reconstruct the complete audit trail. Measure costs across both platforms. Only after those tests should an organization extend the pattern to procurement or finance operations. AgentenCode has not independently tested SAP's gateway or certified the claimed protections.

Primary sources and scope

The evidence is based on primary publications and an independently authored editorial assessment, not independent penetration testing, production auditing or product certification.

Evidence methodology

Frequently asked questions

Is SAP's A2A Agent Gateway generally available?

SAP says inbound invocation of supported SAP agents became generally available in October 2026. Outbound and fully bidirectional patterns are separate roadmap items.

What is DSAG asking SAP to clarify?

Predictable costs, actual availability dates and workable deployment in mixed SAP and non-SAP environments.

Can any outside agent access all SAP data?

No. Discovery and invocation permission are separate, and business actions remain subject to the user's configured authorization.

Further reading

← All news