Three weeks ago, the SAP API Policy v.4.2026a looked like a legal document with no enforcement infrastructure. After Sapphire 2026, it looks like a strategy with a product line attached. CIOs running SAP have three weeks until June 9 enforcement begins, and the destination the policy redirects you to is now fully visible. The policy is real. The pathway is real. The 2027 pricing cliff is the part SAP is not yet talking about.
What the policy says, in plain language
The SAP API Policy restricts three things outside SAP-endorsed pathways:
Third-party AI agents calling SAP APIs to plan, select, or execute actions
Large-scale data extraction to non-SAP environments
Work-arounds through proxies, gateways, custom code, or impersonation (section 3)
Enforcement begins June 9, 2026, with a security patch that technically blocks noncompliant ODP via RFC calls. The enforcement is anchored in SAP Note 3255746 (Version 11, updated April 21, 2026), with SAP Note 3439624 providing the self-assessment tool to audit existing ODP-RFC usage.
Why the policy now has teeth it did not have before
When the policy first dropped, four gaps made it look unfinished. SAP closed all four at Sapphire.
Gap 1: The endorsed pathway was vague. Joule Studio 2.0 is generally available now. Joule Work runs in production on mobile, with H2 2026 general availability (GA) on web and desktop. SAP AI Agent Hub reaches general availability Q3 2026. The Integration Suite MCP gateway launches Q2 2026. SAP Business Data Cloud (BDC) is in market. Now CIOs can map vendor commitments against this stack tied to specific dates.
Gap 2: Third-party AI agents reach SAP data only through Joule Agents. A Microsoft Copilot for Finance instance querying SAP general ledger data must pass through a Joule agent under the A2A protocol, generally available Q4 2026. Salesforce Agentforce and ServiceNow AI Agents face the same constraint. SAP defines the mediating Joule agent, governs the protocol, and meters the traffic. Twelve months ago, this layer did not exist. The finance team running Copilot against S/4HANA now pays for it.
Gap 3: The metered access layer is now an SAP product. The Integration Suite MCP gateway, releasing Q2 2026, exposes curated SAP APIs as managed MCP servers with metering, traffic management, token consumption, rate limiting, and agent identity verification. Practical impact: A global manufacturer running Microsoft Fabric pipelines off SAP S/4HANA finance data through the Azure Data Factory SAP ODP connector loses that pipeline June 9. The supported replacements are SAP Business Data Cloud Delta Sharing for analytical workloads and the MCP gateway for agent workloads. Both route through SAP-metered infrastructure. Data that previously flowed at the cost of compute now flows at the cost of compute plus SAP’s metering surface.
Gap 4: SAP had no AI products credible enough to justify the restriction. SAP can defend the policy because it ships agentic capability that customers will deploy. The Autonomous Close Assistant compresses financial close from weeks to days via automated journal entries, reconciliation, and error resolution. JPMorganChase confirmed migration of its corporate general ledger to S/4HANA. H&M demonstrated Store Intelligence Agents and an AI-powered Store Concierge. The 224 agents and 51 assistants now have named reference deployments to point to.
The 2027 pricing cliff is the story SAP is not telling
SAP made Joule Studio 2.0 free through December 31, 2026. Agent runtime is free, and A2A interoperability is free with no cap. This is the most aggressive commercial move SAP has made in a decade. It is also the Microsoft Teams 2017 playbook: free to adopt, priced to entrench.
The 2027 pricing for Agent Gateway throughput at scale, A2A consumption, BDC egress, and Joule Studio post-promotion remains undisclosed. Most customer 2026 budgets do not model this cliff. The free-through-year-end window is SAP’s path to getting the customer on the highway, knowing that the customer will inevitably pass through a metered tollbooth down the road in 2027.
What still has not been addressed
Four unresolved questions in the policy text expose every SAP customer signing a 2026 renewal:
What happens to existing integrations? No grandfathering language in the policy text.
What constitutes “large-scale data extraction”? No quantitative threshold published.
What will 2027 commercial terms look like for Joule Studio, Agent Gateway, A2A consumption, and BDC egress? No published pricing.
How fast will SAP publish APIs to match capability needs? No publication SLA committed.
Why SAP is doing this
SAP is not winning the agentic AI war inside its own customer base. The tell is in SAP’s own pricing: Joule Studio 2.0 is free, agent runtime is free through December 31, 2026, and A2A interoperability is free with no cap. This is the most aggressive commercial concession SAP has made in a decade, beyond even the €100 million partner fund SAP launched at Sapphire to incentivize agent adoption. As a comparison, Microsoft 365 Copilot paid commercial seats exceeded 20 million by Q3 FY2026 per Microsoft’s April 29, 2026, earnings disclosure, up from 15 million one quarter earlier (a 33% increase in three months). Of SAP’s 224 agents and 51 assistants announced at Sapphire, most sit in mixed GA, early-adopter, or preview status.
Why Forrester thinks it is the wrong call
Closed architectures work when the vendor is winning on capability. Apple closed iOS from a position of product leadership. SAP is closing from a position of AI weakness. The historical pattern is consistent: Vendors that restrict access while trailing on product create openings for alternative ecosystems. Microsoft’s Internet Explorer strategy and Twitter’s API restrictions both bought short-term control and pushed developers and partners toward more open substitutes. SAP could have charged for Joule, the Knowledge Graph, BDC, and Agent Gateway on merit without banning competitors, and the revenue would likely have followed the capability. By choosing restriction instead of competition, SAP is collecting tomorrow’s lock-in revenue at the cost of the next decade of customer trust. The 2017 indirect-access controversy established a lasting concern for buyers: SAP may monetize “access” in ways customers didn’t budget for. This policy risks reviving that concern by increasing friction, scrutiny, and escalation in renewals and architecture decisions. That is how trust damage shows up: slower commitments, harder negotiations, and more hedging.
What you should do next
Hedge with discipline. Negotiate with leverage. Do not migrate. Do not capitulate.
Five actions before June 9:
Inventory ODP-RFC dependencies this week. Every SAP-to-non-SAP data pipe is a June 9 risk. Use SAP Note 3439624’s self-assessment tool. List, rank, and plan remediation.
Freeze new multiyear third-party AI deals dependent on SAP data. This includes Salesforce Agentforce, Microsoft Copilot for Finance, ServiceNow AI Agents, Workday Illuminate, and Celonis. There should be no three-year-plus commitments without written SAP carve-outs.
Escalate to SAP at the executive sponsor level. Demand the four items in writing: grandfathering, fair-use thresholds, 2027 commercial terms, and a published API SLA. Set a 14-day response window.
Pilot Joule Studio while it is free, but contract for the 2027 cliff. Use the free-through-year-end window to validate capability. Add post-promotion price ceilings to every SAP renewal signed in 2026.
Brief the board. This is bigger than an IT integration issue and demands board attention. A vendor control event with budget and AI strategy implications with this level of strategic partner should be treated as such.
The policy is the plan. June 9 is the trigger. 2027 is when the bill arrives. Act this week. Brief the board next.
