SAP Joule in 2026: Joule Agents, Licensing, What It Sees and What Works With It

TL;DR

• SAP Joule is SAP's AI assistant and agent layer. It is the best way to ask questions of SAP data and run SAP processes in plain language, because it knows SAP's business objects and checks the same permissions a user has in SAP.
• Joule Base comes at no extra cost with qualifying SAP cloud subscriptions. Premium capabilities, including Joule agents, are billed in AI Units, and under the model SAP is phasing in from Q3 2026 every agent action consumes 0.02 AI Units.
• Joule sees SAP systems best. Email, chat, meetings and non-SAP systems reach it only through integrations such as Microsoft Copilot, Joule Studio agents, A2A or SAP Business Data Cloud.
• Sentra complements Joule: it joins what SAP says with what people said in email, chat and meetings, raises the gap to the owner, and serves the same company memory to Joule, Copilot and any other agent over MCP and REST.

SAP Joule: what it is and what it does

SAP Joule is SAP's generative AI assistant, embedded across SAP applications, that answers questions, guides tasks and runs agents over SAP business data. SAP describes it as "an AI solution embedded into the flow of work across SAP and non-SAP systems" that brings AI assistants and agents together (help.sap.com).

SAP announced Joule on 27 September 2023 as a natural-language generative AI copilot (news.sap.com). It runs on SAP Business Technology Platform as a multi-tenant service, with each customer's data isolated, and it bundles capabilities based on the SAP products you own (same help.sap.com source). An SAP S/4HANA customer and an SAP SuccessFactors customer get different Joules.

People use "Joule AI" and "SAP Business AI" loosely. SAP Business AI is SAP's umbrella for its AI portfolio. Joule is the conversational and agent layer inside it. For how agents differ from assistants in general, see agentic AI vs AI agents.

SAP Joule agents and the Business AI Platform

Joule agents are SAP-built AI agents that carry out multi-step business tasks inside SAP processes.

The timeline, from SAP's own newsroom:

• October 2024. At TechEd, SAP introduced collaborative AI agents in Joule, with first use cases in dispute management and financial accounting (news.sap.com).
• February 2025. SAP announced ready-to-use Joule agents across finance, service and sales (news.sap.com).
• November 2025. At TechEd, SAP said it had shipped 20 Joule agents and that Joule agents would support the agent-to-agent (A2A) protocol to work with other vendors' agents (news.sap.com).
• May 2026. At Sapphire, SAP launched the SAP Business AI Platform, which "unifies SAP Business Technology Platform, SAP Business Data Cloud and SAP Business AI," with "more than 50 domain-specific Joule Assistants" that orchestrate "a subset of over 200 specialized agents" (news.sap.com).

Two newer pieces matter for buyers. Joule Work is a workspace where you describe an outcome and Joule Assistants coordinate Joule agents to deliver it. The mobile app is generally available; desktop general availability is planned for the second half of 2026. Joule's bi-directional A2A capabilities, which let third-party agents call Joule agents, are slated for general availability in Q4 (news.sap.com). Joule Studio is SAP's tool for building custom agents, with MCP-enabled toolchains for developers (same source).

SAP Joule licensing and pricing

SAP does not sell Joule as a simple per-seat product. Its commercial model, as SAP Learning sets it out, has two tiers (learning.sap.com):

Under the new model, SAP says most generative AI features move into Base at no extra cost and the per-user packages are phased out. SAP Concur keeps a separate uplift model (same source).

What SAP does not publish on these pages is a currency price per AI Unit. That comes from your SAP account executive and your contract. To estimate agent cost, count actions, not users: an agent that runs 100,000 actions a year consumes 2,000 AI Units at the 2026 rate. Multiply by your contracted AI Unit price. SAP's Business AI Feature Catalog in SAP Discovery Center lists which features are Base and which are Premium.

What SAP Joule can see and what it can't

Joule's advantage is depth in SAP. Its limit is that most companies do not run on SAP alone.

• SAP back-end systems. SAP lists "out-of-the-box integration with SAP back-end systems," and capabilities are tailored to your SAP portfolio (help.sap.com).
• SAP permissions. Questions are processed in the scope of the user's identity and permissions, and access is restricted with the same permission checks as using Joule directly (same source).
• Documents from connected repositories. Joule ingests and references enterprise documents from repositories you connect.
• Microsoft 365, through Copilot. Joule is available as an agent inside Microsoft Copilot, and Joule can call Copilot. All queries Joule answers in its own web client are also available in Copilot (same source).

• Email, chat and meetings. Joule reaches Microsoft 365 content by handing off to Microsoft Copilot. SAP's documentation notes that "SAP is not responsible for and does not control the data processed by Microsoft 365 Copilot." The answer about an email thread comes from Copilot under Microsoft's terms, not from Joule's understanding of the SAP process.
• Non-SAP systems of record. A Salesforce CRM, a Workday HRIS or a non-SAP BI tool reaches Joule through Joule Studio agents, A2A, or data work in SAP Business Data Cloud. Each is a separate project.
• The reason behind an SAP number. SAP knows a purchase order is confirmed for 3 November. It does not know the supplier emailed on Tuesday that the date slipped, or that the plant manager said so in Thursday's operations call.

Data handling to read before rollout. SAP's Joule documentation states that interaction data is retained for one year by default, and that SAP "may use any submitted data to Joule, or data generated from the use of Joule, excluding personal data" to assess and improve Joule's capabilities (help.sap.com). Have legal review that clause against your data policy.

SAP Joule alternatives and complements

For most SAP customers, the useful question is not "Joule or something else?" but "what works alongside Joule?" Joule is the natural interface to SAP. The products below either cover the systems Joule does not, or hold the company context Joule lacks.

Sentra

Sentra connects to SAP and the rest of the stack, then joins the ERP record with what people said about it. It raises the gap to the owner with the evidence. Joule keeps running the SAP process.

Microsoft Copilot

Copilot answers from Microsoft Graph, the mail, files, chats and meetings each user can access. Joule is available inside it as an agent, so users can reach SAP data from Teams and Office. Copilot costs $30 per user per month paid yearly on a qualifying Microsoft 365 plan (microsoft.com). See our Microsoft Copilot agents guide.

Salesforce Agentforce

Agentforce runs agents on Salesforce CRM and Data 360 and lists $2 per conversation, Flex Credits, or $125 per user add-ons (salesforce.com). Our Agentforce alternatives page covers its pricing in detail.

ServiceNow AI Agents

ServiceNow builds agents in AI Agent Studio, and Action Fabric connects outside agents and tools over MCP and A2A (servicenow.com).

Glean

Glean indexes many apps for permission-aware search. It publishes no rate card; see our Glean pricing breakdown.

Works with Sentra: SAP data joined with what people said

Joule is strong at "what does SAP say?" Sentra answers "is that still true, why, and who should act?"

The mechanism:

1. Connect. Sentra reads ERP, CRM, HRIS and BI alongside email, chat, meetings and documents, through 200+ integrations. Nothing is entered by hand.

2. Understand. It works out what is true now and who owns it. It knows when a fact became true and when it stopped being true, so a confirmed delivery date that a supplier later moved is marked as superseded, with the email as evidence.

3. Act first, with approval. Sentra's agent finds the gap, works out who should act and drafts the alert. A named person approves before anything reaches anyone else.

4. Serve every agent. Sentra exposes REST and MCP. Joule Studio offers MCP-enabled toolchains for custom agents, and Joule interoperates with Microsoft Copilot, so the same company memory can reach SAP users wherever Joule or Copilot supports MCP or custom connectors.

5. Respect permissions. Answers respect each source's existing permissions, checked at query time. A failed check counts as no access.

An illustrative case: SAP shows a purchase order for a key component confirmed for 3 November, and planning runs on that date. On Tuesday, the supplier emails the buyer that the shipment will arrive on 17 November. On Thursday, the plant manager mentions a likely line stoppage in the operations call. Sentra joins the three, tells the buyer and the plant manager with the email and the meeting note attached, and the buyer approves the message to planning.

Sentra is SOC 2 Type II and ISO 27001 certified and deploys in the cloud, in an isolated VPC, or air-gapped on-premises.

To see how Sentra works next to Joule on your own SAP processes, book a demo.

How to choose

1. Start with Joule Base. If you hold qualifying SAP cloud subscriptions, activate it with the €0 SKU and test it on real SAP questions before buying anything else.

2. Price agents by action. Estimate actions per process per year and multiply by 0.02 AI Units, then by your contracted AI Unit price. Check whether each feature is Base or Premium in the Feature Catalog.

3. List what lives outside SAP. CRM, HRIS, email, chat and meetings. For each, decide whether you will build a Joule Studio agent, rely on Copilot, or connect a shared company memory.

4. Review data terms. Read the retention and improvement clauses in SAP's Joule documentation with legal before broad rollout.

5. Require approval for actions. Any agent that changes records or messages suppliers should have a named approver.

For the broader agent market, see enterprise AI agents, AI agents for business and the best enterprise AI platforms.

FAQ