Experts question whether Salesforce demo breaches SAP API policy

Salesforce demonstrated an AI agent at Dreamforce that could complete supplier onboarding in SAP through the SAP user interface, prompting SAP specialists to question whether the approach would violate SAP's April API policy and endorsed-architecture requirements. Salesforce said the restrictions do not apply because the demo used service accounts and UI interaction rather than SAP APIs, while SAP declined to comment. The dispute highlights a strategic risk for SAP: its AI-access policies may constrain customers' use of third-party agents and allow Salesforce, Microsoft, or ServiceNow to control the end-user workflow while SAP remains the backend system.

Analysis

The investable issue is control of the enterprise-agent orchestration layer, not whether a conference workflow ultimately satisfies a narrow access-policy interpretation. If CRM, NOW or MSFT can make their collaboration and workflow interfaces the place where employees initiate ERP actions, SAP risks gradual commoditization toward system-of-record status. That would pressure SAP's ability to attach premium AI/cloud monetization to its installed base, while raising the strategic value of integration, identity, audit and workflow assets at CRM, NOW and MSFT.

Near term (days to 3 months), the headline alone is unlikely to alter estimates: large SAP deployments have long procurement, security-review and change-management cycles, and the demonstration's production economics are unverified. The relevant catalyst is customer evidence that SAP is requiring paid approved architecture or cloud migration to permit third-party agent use. Such enforcement would create implementation friction and could delay AI deployments, but it also risks accelerating CIO demand for vendor-neutral orchestration—benefiting MSFT's Power Platform/Copilot stack and ServiceNow's cross-enterprise workflow position.

The contrarian case is that SAP can turn governance into a feature rather than a moat: regulated customers may prefer SAP-approved logging, permissions and deterministic controls for financial-master-data workflows. If SAP's agent tooling proves broadly interoperable and adoption shows up in cloud backlog, the current concern becomes a modest take-rate opportunity rather than a competitive loss. Falsify the SAP-negative thesis if management demonstrates third-party agent deployments without incremental RISE dependence, maintains cloud backlog/guidance, and avoids customer or partner escalation around access restrictions over the next two reporting cycles.

Key Decisions for Investors

• No outright event trade in SAP on this item; monitor the next two earnings calls for AI/cloud backlog, RISE conversion and explicit third-party-agent policy questions. Escalate to a short only if management signals enforcement-driven migration friction alongside a cloud-growth or backlog-guide reduction.
• Maintain a 3-6 month relative-value watch: long NOW versus SAP if enterprise-agent deployments increasingly require cross-platform workflow governance. NOW's upside case is multiple expansion from becoming the policy/audit layer; exit if SAP reports material external-agent interoperability wins or NOW's subscription-growth guide weakens.
• Prefer CRM over SAP for a tactical 1-3 month basket only after independently verified production customer references emerge; the key confirmation is paid Agentforce workflows writing into ERP systems with measurable seat, consumption, or Data Cloud attach. A keynote demo without disclosed production metrics is insufficient to add risk.
• Track SIE as a read-through rather than a position: a named industrial reference can validate demand for ERP-adjacent agents, but procurement-scale deployment and security approval—not demonstration status—determine whether this becomes meaningful software spend.