SAP has shipped more than 50 domain-specific Joule Assistants orchestrating over 200 specialised agents across its cloud portfolio — and at Sapphire 2026 it reframed all of it as the "Autonomous Enterprise." Yet most SAP customers still haven't turned these capabilities on in production. This guide covers what's actually available, module by module, so you can find the capabilities that matter for your team.

What changed at Sapphire 2026

In May 2026, SAP pulled Joule, its agents, and its data layer under one banner — the Autonomous Enterprise, built on the SAP Business AI Platform (BTP + Business Data Cloud + Business AI in one governed environment). Note the platform is being delivered component by component through 2026, not as a single GA release. The pieces that actually matter for activation:

  • The Autonomous Suite — SAP's wording is that the suite will deploy more than 50 domain-specific Joule Assistants, orchestrating a subset of over 200 specialised agents across finance, supply chain, procurement and HR. Both figures are deployment targets, not a count of what is generally available today — and SAP does not publish a live GA count. Claude is described by SAP as a primary reasoning and agentic capability, alongside models from Google, OpenAI, Mistral and Cohere under an explicitly open, multi-model approach.
  • Joule Studio — SAP's fully managed agent builder. Free through the end of 2026 (SAP's June 2026 commercial material covers design-time and runtime under fair-use limits), and it draws on BTP Units rather than AI Units. Still in SAP Early Adopter Care as of the Q2 2026 release highlights, with GA forecast for Q3 2026 (unconfirmed as at September 2026 — check the current release highlights) — so treat it as a sandbox, not a production platform.
  • Business Data Cloud + Knowledge Graph — the "trusted knowledge core" every agent reasons over. The unglamorous layer that decides whether any of the above works — and the part most customers haven't built yet.

The order matters more than the agent count: a clean, governed data foundation first, automation second. Not sure where you stand? Take the 2-minute Reality Check →

Read the hierarchy before you count anything

SAP stacks four layers, and mixing them up is the most common mistake in SAP AI conversations. Domain (Finance, Spend, Supply Chain, HCM, CX) → Autonomous Domain Blueprint, the commercial package a customer actually buys, sized by user count and agent activity → Joule Assistant, the role-facing coordinator your people talk to → Joule Agent, the task executor underneath.

SAP publishes 50 Joule Assistants across the five domains — HCM 12, Finance 12, Spend 11, CX 10, Supply Chain 5 — each coordinating several agents. It does not publish a flat agent catalogue or per-agent GA dates. So when a vendor deck says "200+ agents", that is the layer nobody buys or switches on individually; the assistant is the unit that shows up in a user's day, and the blueprint is the unit that shows up on the invoice.

What the blueprint actually is. SAP names two blueprints per domain — Finance: Accounts Receivable and Financial Close; Spend: Sourcing and Procurement Operations; Supply Chain: Replenishment and Logistics Execution; HCM: Core HR and Payroll, and Learning and Talent Management; CX: Service Resolution and Sales Execution. Each bundles assistants and agents, an embedded SAP Success Plan (Foundational / Advanced / Max), Joule Base and Premium features, and Intelligent Packages that draw on Business Data Cloud credits. Sizing is T-shirt (S/M/L) on three variables: how many users touch the assistants, how much process scope is covered, and the volume of agent activity. A seller-facing Autonomous Domain Configurator is planned for Q3 2026. All of this is from SAP’s own public lesson, Exploring Autonomous Domain Blueprints — open on learning.sap.com, no partner login required.

Two cautions. First, the blueprint has no SKU, no price list and no Help Portal documentation — it lives in SAP's go-to-market and enablement material. Treat it as a sales configuration layer, not something you provision. Second, it is not a new currency: you still buy AI Units for Premium AI, BTP credits for Joule Studio and AI Foundation, and BDC credits for Intelligent Packages, on top of Base AI at zero cost. The blueprint decides how many of each. The cost deep-dive covers the AI Units mechanics →

The module guides below are organised by agent, because that is the level at which activation, prerequisites and limitations actually bite. To see the assistant layer per domain, and how SAP's counting compares to Oracle's and Microsoft's, use the Embedded AI Ledger — every row is tagged agent, assistant or agentic application.

Available Now

Coming Soon

HCM

SuccessFactors (HCM)

Coming Soon
Before you start

All Joule features require SAP BTP integration. Most capabilities are available on S/4HANA Cloud (public and private edition). On-premise S/4HANA has limited Joule support. Check your BTP Global Account → Entitlements → search 'Joule' to see what's available in your license. And before switching any of it on: run the Data Readiness Checklist on the process first — permissions, field population, variants, documents.

Between the Hype

This guide pairs with the newsletter. The guide shows you what's available — the newsletter tells you what it means for your strategy.

Subscribe on LinkedIn →