2 October 2026 7 min read

SAP Connect 2026: What to Watch in BTP, Integration and Business AI

SAP Connect 2026 is where SAP has to prove that the Autonomous Enterprise it pitched at Sapphire can run across the systems you already own. The headline will be Joule Work and autonomous processes. The part that decides whether any of it reaches production sits lower in the stack: BTP’s place in the new SAP Business AI Platform, SAP Integration Suite, API governance, and the rules for connecting SAP and non-SAP AI.

Where and when?

SAP Connect 2026 runs October 5-7 in Las Vegas, with a free virtual track on October 6-7. It is a cross-functional adoption event, not a developer conference, so it is the natural place to test whether SAP’s platform claims hold up in real, multi-system processes.

This is a preview written before the event. Treat specific product news as watch items, not confirmed launches. If you lead integration, architecture, or an SAP program, here is what to watch and why it matters before the keynote.

Why SAP Connect matters now

Connect is SAP’s deployment checkpoint. Sapphire sold the vision in May. Connect has to show it working across finance, spend, supply chain, HR, and customer processes.

Cross-functional enterprise automation cannot be proven inside one application. A cash, procurement, or supply workflow needs identity, policy, data, events, APIs, and human approvals to work across several systems at once. That is what SAP has to demonstrate here, across six co-located line-of-business experiences under one event.

Three pressures make this edition matter more than a normal roadmap update:

The migration clock. SAP Business Suite 7 stays in mainstream maintenance only through the end of 2027. Connect lands about 15 months out, so practical guidance on clean core, hybrid integration, and phased coexistence carries real weight.
Customer scrutiny. In the 2026 DSAG Investment Report, 79% of respondents flagged cost-effectiveness as a challenge, and only 35% said SAP’s target architecture strongly shaped their plans. Interest in the vision does not equal budget.
Position in the calendar. Connect is the business-process layer between Sapphire’s vision and SAP TechEd’s implementation detail in late October. A big integration claim here with no architecture or hands-on follow-through is itself a signal.

If autonomous processes are the promise, integration is the mechanism that makes them possible.

Is your integration layer ready for SAP Business AI?

We get your SAP and non-SAP estate agent-ready – governed APIs, controlled integrations, and clear ownership – so autonomous processes run in production, not just in a demo.

BOOK AN SAP INTEGRATION WORKSHOP

Foundation first. Agents second.

Justyna Łukaszuk PMO Manager

Foundation first. Agents second.

BOOK AN SAP INTEGRATION WORKSHOP

Justyna Łukaszuk PMO Manager

Theme to watch: SAP BTP integration

BTP has not disappeared. Its capabilities now sit inside the SAP Business AI Platform, and SAP Integration Suite is being positioned as the control plane where agents actually act.

Do not read the repackaging as a rename. The practical shift is that integration now has to connect not just apps and data, but the AI agents and the tools they call. That means governance across identity, policy, runtime, and monitoring. SAP Integration Suite is the layer where it all has to hold together, across SAP and non-SAP estates.

This is why agentic AI raises the bar for integration rather than removing it. Agents still need contracts, authentication, throttling, observability, and safe back-end behavior. Faster, less predictable consumers make disciplined integration more important, not less. It is the same pattern we see whenever enterprise AI agents move from pilot to production.

Watch for substance, not counts:

Capability	What to watch at Connect
Joule-assisted integration	GA by edition and region, testing, ownership of generated flows, human review
Edge Integration Cell	Offline resilience, B2B coverage, observability parity, cost vs cloud runtime
Event-driven triggers	How events become agent actions, catalog governance, replay and lineage
PI/PO migration	Supported artifacts, custom mappings, realistic effort and timelines

The real test: SAP’s Autonomous Enterprise will succeed or fail at the integration layer, not in the Joule demo.

Theme to watch: API integration

SAP has pulled API management and agent-readiness into one governed layer with API-Centric Integration and an MCP Gateway. The open question is whether that simplifies your operating model or just moves it into a new SAP-specific runtime.

API-Centric Integration treats an API as a first-class artifact: contract, connectivity, transformation, security, traffic control, and lifecycle in one place. The Model Context Protocol (MCP) then exposes enterprise capabilities as tools an agent can discover and call.

The distinction that matters is protocol support versus enterprise readiness. Proving an agent can call a tool is easy. Doing it with delegated identity, least privilege, approval controls, transaction safety, and a full audit trail is the enterprise problem. It is the same integration gap that stalls AI in production.

There is also a commercial layer that is easy to miss. SAP’s updated API Policy restricts agentic and generative AI access to APIs outside SAP-endorsed architectures, and DSAG has asked SAP to clarify the rules for third-party agents and non-SAP scenarios. So any “openness” claim at Connect needs testing on four layers at once:

Protocol. Supported MCP/A2A versions, discovery, and compatibility.
Identity. User versus agent identity, delegated authorization, and least privilege.
Governance. Tool approval, policy enforcement, human checkpoints, and audit.
Commercial. Permitted API uses, required SAP services, pricing, and support.

If SAP answers only the protocol layer, read “open” cautiously.

The enterprise questions to ask after the keynote

Judge announcements by deployability, not demo polish. Five clusters separate progress from noise.

Availability. Is it generally available, in preview, or roadmap? Which regions, editions, and prerequisites?
Architecture. Can agents act across non-SAP systems as first-class participants, with identity propagated and artifacts portable?
Governance. Who is accountable for an autonomous action, and can you trace one outcome end to end through policy, APIs, and the back-end transaction?
Economics. Is there one understandable model across BTP capacity, Integration Suite messages, AI tokens, and agent execution?
Migration. How much PI/PO content converts automatically, and can you modernize incrementally before 2027?

SAP will have made real progress if customers leave Las Vegas with an architecture they can approve, a cost they can model, a migration path they can schedule, and controls their security and audit teams accept.

Summary: what we will be watching

SAP Connect 2026 is a test of whether SAP can make autonomous processes operationally boring: secure APIs, predictable integration, explicit entitlements, observable execution, and safe failure modes. Five takeaways to carry into the event:

Integration is the story, not Joule. The interface gets the keynote. The integration and API layer decides production.
BTP moved, it did not vanish. Watch how it is packaged inside the Business AI Platform and whether you can still adopt integration without a full platform commitment.
“Open” is a claim to test. Protocol support is not enterprise interoperability. Check identity, governance, and the API Policy too.
Ask for evidence, not counts. Named production customers with measured outcomes beat “200+ agents.”
Mind the migration clock. With 2027 approaching, coexistence and PI/PO migration matter as much as the AI story.

Sources

contact

Thank you for your interest in Multishoring.

We’d like to ask you a few questions to better understand your IT needs.

Justyna PMO Manager

Signed, sealed, delivered!

Await our messenger pigeon with possible dates for the meet-up.