SAP Business AI, Joule, Copilot: The Terminology Map

What is SAP Business AI? The answer in one breath

If you searched “what is SAP Business AI” and got ten different answers, the fault is not yours: SAP redrew the map at Sapphire and again at TechEd, and most material still online predates both.

Here is the version that holds as of November 2026. SAP Business AI is SAP’s umbrella brand for AI woven through its business applications and its platform. At SAP Sapphire in May 2026, SAP introduced SAP Business AI Platform, and its own description is the cleanest orientation available: the platform “now unifies SAP Business Technology Platform, SAP Business Data Cloud and SAP Business AI into a single, governed environment” (SAP Sapphire 2026 press release). The old brand did not disappear; it became one of three things inside a named platform.

Under that umbrella, every name answers one of five questions:

Who touches it? Joule Work, Joule Assistants and Joule Agents — the interaction layer.
Who builds it? Joule Studio — no-code and pro-code, “choosing from more than 70 AI models” (SAP TechEd 2026 press release).
What runs the workloads? SAP AI Core (engine) and SAP AI Launchpad (management plane), with the generative AI hub inside AI Core.
What grounds the answers? SAP Business Data Cloud and the SAP Knowledge Graph solution, which gives agents “a structured map of business entities, processes and relationships”.
Who polices it? SAP Enterprise AI Gateway, SAP AI Agent Hub, and the AI Governance Assistant aimed at EU AI Act obligations.

One absence matters early: the word “copilot” appears nowhere in SAP’s naming for any of this. Reading the Sapphire and TechEd releases line by line, SAP consistently says Joule. “Copilot” belongs to Microsoft, and that single distinction resolves most of the confusion we see in architecture documents.

The terminology map

The table below is the reference we wish existed when this all landed. “Official status” is our judgement: SAP’s own name, SAP’s own but new, or a community habit SAP never wrote down.

Name	Official status	What it is	The usual misreading
SAP Business AI	Official, pre-2026 umbrella	AI embedded across SAP apps and services	Taken for a purchasable product
SAP Business AI Platform	Official, introduced May 2026	The unified environment spanning BTP, Business Data Cloud and Business AI	“So BTP is gone” — unified, not retired
“BAIP”	Community shorthand	Acronym for the platform above	Appears in third-party posts; SAP’s own pages spell the name out
Joule	Official, but now overloaded	The AI assistant family and its conversational surface	Read as one single product with one licence
Joule Work	Official, announced Sapphire 2026	The central AI workspace and primary engagement layer: web, desktop, mobile, voice	“A rebrand of SAP Mobile Start” — side effect, not scope
Joule Assistants	Official	Domain-specific assistants (finance, supply chain, HCM, CX, procurement)	Confused with agents a partner builds
Joule Agents	Official	Task-executing agents orchestrated by assistants and workflows	Confused with external A2A agents
Joule Studio	Official	SAP’s AI-first development environment for agents, apps and agentic workflows, accessible through Joule Work	Assumed to replace BTP development entirely
SAP AI Core	Official, mature	Engine for AI workflows and model serving workloads	Mistaken for “the UI”
SAP AI Launchpad	Official, mature	Management plane for AI runtimes, scenarios and users	Treated as its own platform
generative AI hub	Official (lowercase in docs)	Curated model access and governance inside SAP AI Core	Cited as a standalone service
SAP Business Data Cloud	Official	The data foundation for AI-ready, governed data	Collapsed into “just SAP Datasphere”
SAP Knowledge Graph	Official, solution	Business entity/process/relationship map that grounds agents	Assumed to be a graph database to deploy
SAP Enterprise AI Gateway	Official, announced TechEd 2026	Centralised control of AI traffic: authn, policy, routing, monitoring, usage, auditing	Believed to be GA; SAP plans GA Q1 2027
SAP AI Agent Hub	Official, announced TechEd 2026	Catalog that makes agents discoverable, including in Joule Work conversations	Mixed up with an agent store
Microsoft 365 Copilot	Microsoft’s name, not SAP’s	External copilot that can reach SAP through a managed integration	Called “the SAP copilot”

Read the names from the top down

Beginners usually work bottom-up, from infrastructure to interface, which is backwards for this vocabulary. SAP’s 2026 messaging is written top-down, so read it that way.

Engagement. Joule Work is the surface people live in. SAP’s product page calls it “one AI workspace for every team” and “the new UI for AI”, shipped as web, desktop and mobile apps (Joule Work). The Sapphire release is more pointed: instead of navigating applications and retyping data across screens, “users will now interact primarily with Joule”.

Domain intelligence. Joule Assistants and Joule Agents do the work inside a process. SAP Autonomous Suite “will deploy more than 50 domain-specific Joule Assistants across finance, supply chain, procurement, human capital management and customer experience”, orchestrating “a subset of over 200 specialized agents”. RISE with SAP and SAP GROW now include the assistant portfolio, which is why this name appears in commercial conversations, not just technical ones.

Build and extend. Joule Studio is where custom agents, applications and workflows get made. SAP calls it “SAP’s AI-first solution for building enterprise agents, applications and agentic workflows”, usable with the no-code, pro-code and AI frameworks of a developer’s choice, then refines it as “SAP’s AI-first development environment that is accessible through Joule Work” (Sapphire release, TechEd release). The launch blog adds the plumbing: LangChain, Pydantic AI and LlamaIndex for pro-code, embedded n8n, and a managed runtime sandboxed by NVIDIA OpenShell (New Joule Studio blog).

Runtime. Two services, one job each, in SAP’s own words: “SAP AI Core provides an engine that lets you run AI workflows and model serving workloads”, while “SAP AI Launchpad manages a number of AI runtimes” and lets different user groups access and manage their AI scenarios, with the AI API covering lifecycle across SAP and partner runtimes (SAP AI Launchpad overview). Curated LLMs and SAP’s own SAP-RPT tabular models are reached through the generative AI hub, which SAP calls “the generative AI hub component in SAP AI Core” (generative AI hub, TechEd innovation news guide).

Context and governance. SAP Business Data Cloud plus the SAP Knowledge Graph ground the answers. SAP Enterprise AI Gateway governs the traffic: SAP states it is part of SAP Business AI Platform, builds on SAP Integration Suite, manages MCPs, APIs, A2As and LLMs, and plans GA in Q1 2027. Bringing your own model instead of the catalogue is a different path, with its own traps, and we cover it separately below.

Where the naming genuinely overlaps (confusion is normal)

These are the collisions we expect to still be arguing about in 2027. None of them are your fault, and several are not fully resolved by SAP itself.

“Joule” is now a prefix, not a product. Older material treats Joule as one assistant bolted onto S/4HANA. Current material uses Joule Work, Joule Assistants, Joule Agents and Joule Studio — four scopes sharing one word. When a colleague says “enable Joule”, ask which one; the licence, the entitlement and the administrator all differ.

Joule versus Copilot is a two-vendor problem, not a synonym pair. Microsoft frames the territory as three layers: the managed, bidirectional integration between Joule and Microsoft Copilot; custom agents in Copilot Studio; and enterprise builds in Microsoft Foundry with MCP tools against SAP APIs (About SAP with Microsoft AI). SAP’s side of the bridge is documented under SAP’s own name (Integrating Joule with Microsoft 365 Copilot). “The SAP copilot” means Joule; “Copilot with SAP” probably means a Microsoft-side connector that never touches Joule. That ambiguity causes real design errors, because the two routes have different identity, licence and data-residency consequences. Our walkthrough of the bridge, including identity trust and licence gates, is SAP Joule + M365 Copilot on Azure.

Build-time versus run-time is where Joule Studio and AI Core get merged. In our reading, Studio is the authoring environment with a managed runtime attached, while AI Core and AI Launchpad are the service plane you entitle and administer in a subaccount. A post that says “we deployed the agent on AI Core” and one that says “we built it in Joule Studio” are not contradicting each other; they describe two ends of one pipeline.

The generative AI hub is a component, not a platform. People cite it as though it were a sibling of SAP AI Core. SAP’s documentation puts it under SAP AI Core, and the innovation news guide says “generative AI hub component in SAP AI Core”. Note SAP’s casing too: lowercase “generative AI hub” — a style nit, but it signals you are quoting rather than paraphrasing.

“BTP was renamed to BAIP” is community interpretation. Several third-party explainers announce a rename. SAP’s wording is unification: the platform unifies SAP Business Technology Platform, SAP Business Data Cloud and SAP Business AI, and BTP still appears in SAP’s own tag lists and documentation. Saying “SAP renamed BTP” in front of an SAP architect starts an unproductive argument; saying “BTP is now inside the Business AI Platform story” does not.

Old surfaces keep their names in the wild. Joule Work also has a mobile app, and SAP’s own community topic page is blunt: “With the new release V3.0, SAP Mobile Start got rebranded as the Joule Work mobile app” (topic page) — while still listing SAP Mobile Start how-tos. The store listing carries the new name (App Store). Expect old names to survive in internal docs long after the rebrand.

Deprecated parts still circulate in code. AI Launchpad’s documentation tree marks Functions Explorer deprecated and Orchestration Workflow V1 deprecated beside the current V2. Older tutorials copy those paths; when a snippet fails on a current subaccount, deprecation is usually the explanation.

How to say it in a meeting

Three scripts we use, by audience:

Executive: “Business AI is what we already buy from SAP, embedded in the apps. The 2026 change is that it, our data foundation and our BTP build services are now sold and governed as one platform, and the everyday interface becomes Joule Work.”
Architect: “Engagement through Joule Work; domain behaviour through Joule Assistants and Agents; custom builds in Joule Studio; model access via the generative AI hub in SAP AI Core with SAP AI Launchpad as control plane; grounding in Business Data Cloud and the Knowledge Graph; AI traffic governed by the Enterprise AI Gateway once it lands.”
Developer: “You will live in Joule Studio and the AI Core APIs. Choose between curated hub models and a bring-your-own endpoint, and treat MCP servers and A2A as integration decisions, not brand decisions.”

The docs namespaces are a cheap way to keep ownership straight, because SAP’s URL folders mirror who owns what:

help.sap.com/docs/joule/...                       → Joule assistants and their integrations
help.sap.com/docs/ai-launchpad/...                → SAP AI Launchpad (management plane)
help.sap.com/docs/sap-ai-core/generative-ai/...   → generative AI hub, inside SAP AI Core

What This Guide Does Not Cover

Licensing and entitlement math. Which package unlocks which assistant is a contract question. SAP says the assistant portfolio ships with RISE with SAP and SAP GROW; we do not translate price.
Step-by-step builds. Provisioning AI Core, registering an external Azure OpenAI deployment and the failure points that eat setup time live in SAP BTP and Azure OpenAI integration.
Infrastructure and landing zones. Network, identity and environment design for SAP on Azure is a separate conversation — that material lives in Azure Landing Zone for SAP: Architecture, Subscriptions, and Governance.
Model quality. No benchmarks and no recommendation of one vendor’s model over another’s.
Non-SAP agent frameworks beyond the naming needed to place them in the map.
Anything after 8 November 2026. This moves at conference cadence; we pinned dates and status wording rather than trust memory.

FAQ

Is SAP Business AI the same thing as Joule?

No. SAP Business AI is the umbrella brand; Joule is the family of assistant and agent experiences underneath it, plus the workspace (Joule Work) and the build environment (Joule Studio). SAP’s 2026 platform wrapper, SAP Business AI Platform, additionally contains what used to be discussed separately as SAP BTP and SAP Business Data Cloud. Shortcut: Business AI is the brand, Joule is what you talk to, AI Core is what you consume.

Do I still say “copilot” when talking about SAP?

Not for SAP’s own products. SAP has never shipped a product named Copilot; its name for that role is Joule, and since May 2026 the engagement layer is Joule Work. Keep “Copilot” for Microsoft 365 Copilot, Copilot Studio and GitHub Copilot, and say which vendor’s side of the bridge you mean, because a Microsoft-side connector and the managed Joule integration carry different identity, licence and data-residency consequences.

Where do the LLMs actually run — SAP AI Core or Azure OpenAI?

Both patterns exist. Curated models are accessed through the generative AI hub component inside SAP AI Core, and SAP also publishes its own models, such as the SAP-RPT tabular family, on the platform. Or you register an external endpoint, such as an Azure OpenAI deployment, and route calls through it. The trap: “SAP AI Core” names the runtime either way; “generative AI hub” names the curated access layer inside it.

Is SAP BTP dead now that there is a Business AI Platform?

No. SAP’s statement is that the Business AI Platform unifies SAP BTP, SAP Business Data Cloud and SAP Business AI into one governed environment. Documentation, entitlements and subaccounts still speak BTP, and SAP’s own materials keep using the name. What changed is the framing: BTP is now the build-and-run portion of a larger platform story, which is why newer titles such as SAP Certified Solution Architect - SAP Business AI Platform reference the platform (SAP Learning).

References

SAP News Center, SAP Unveils the Autonomous Enterprise (12 May 2026) — platform unification wording, Knowledge Graph, Joule Work, Joule Studio, 50 assistants / 200 agents
SAP News Center, SAP TechEd 2026: The Autonomous Enterprise Becomes a Reality (27 October 2026) — “more than 70 AI models”, Joule Studio accessible through Joule Work, SAP Enterprise AI Gateway, SAP AI Agent Hub
SAP, New Joule Studio: enterprise-scale agentic development (13 May 2026) — build / contextualize and reason / govern, LangChain, Pydantic AI, LlamaIndex, n8n, NVIDIA OpenShell
SAP, SAP Business AI Platform — official “what is” copy and named members
SAP, Joule Business AI Solutions — the Joule family division of labour
SAP, Joule Work — “one AI workspace for every team”; web, desktop, mobile
SAP Help Portal, SAP AI Launchpad overview — AI Core as engine, Launchpad as management plane, AI API
SAP Help Portal, generative AI hub — hub documented inside SAP AI Core; orchestration V1 deprecated
SAP, TechEd 2026 innovation news guide — “generative AI hub component in SAP AI Core”, gateway GA planned Q1 2027, new certifications
SAP Learning, SAP Certified Solution Architect - SAP Business AI Platform and SAP Certified Joule Studio Developer
Microsoft Learn, About SAP with Microsoft AI (last updated 2026-09-11) — Joule/Copilot managed integration, Copilot Studio, Foundry with MCP
SAP Help Portal, Integrating Joule with Microsoft 365 Copilot
SAP Community, Joule Work Mobile App topic page — “SAP Mobile Start is now Joule Work mobile app” (V3.0 rebrand), plus the Joule Work App Store listing

Next steps

See the vocabulary applied to one concrete integration: SAP Joule + M365 Copilot on Azure.
Browse the rest of the topic in the SAP AI category or the full tutorial index.

All sources above were reachable on 8 November 2026. Where SAP’s pages are silent — English GA wording for Joule Work and Joule Studio, the exact model list you are entitled to — we write “announced” or “planned” rather than invent a date.