SAP Joule's limits: ECC, Microsoft Copilot, MCP and the handoffs it can't see
The short answer
SAP Joule’s main limitation is that it lives inside SAP. SAP’s own training course says Joule “is natively embedded only in SAP applications that explicitly support it”. SAP provides no general-purpose API for other applications to call Joule directly. The limits that matter most follow from that. ECC and on-premise customers get Joule only through a cloud commitment. Other vendors’ agents can call Joule Agents over A2A only once SAP’s Agent Gateway is live in your tenant, and SAP is rolling it out in phases. Joule’s calls to outside agents are narrow. Agents are billed in AI Units per action, so what an agent costs depends on how many actions your cases take.
Inside SAP, none of that is a weakness: Joule has the semantics, the authorizations and the audit trail. The limits bite where work crosses systems. Take a quality claim (a generic example, not a client case) logged in the CRM, investigated in S/4HANA, argued over in Teams and settled with a credit note. Joule sees the SAP steps, Microsoft 365 Copilot the Teams thread, and neither holds the record of how the claim was decided.
Key takeaways
- Joule is extended, not embedded, outside SAP. Other systems are back ends Joule calls, but no general-purpose API lets them call Joule.
- ECC access has a price of entry. SAP’s interim offer brings Joule to ECC only through the Max Success Plan, after a commitment to SAP’s cloud. SAP’s release promises “select AI scenarios”, not the full set.
- Joule supports MCP in one direction. It can use MCP tools, but SAP documents no MCP endpoint for Joule itself. Its route in for other vendors’ agents is A2A.
- Joule and Microsoft 365 Copilot connect but do not merge. The integration is included with Joule Base, and SAP says it works “without merging them into a single system”.
- Base AI is free with SAP cloud subscriptions, but agents are not. SAP publishes AI Units per agent action and a list price for the units, but the unknown is how many actions your agents take per case.
What are SAP Joule’s limitations?
Eight, by SAP’s own documents and statements: reach outside SAP, being called from outside, ECC and on-premise, private cloud setup, other vendors’ agents, maturity, cost forecasting and where the record lives. The first two follow from a principle SAP states outright: outside SAP, Joule is extended, not embedded.
| Limit | What SAP says | What it means for an SAP owner |
|---|---|---|
| Reach outside SAP | Non-SAP systems “act as back-end data or action providers” | Joule acts on them through Joule Studio; identity stays in SAP |
| Being called from outside | No general-purpose API; non-SAP applications cannot host Joule natively | Your CRM or service desk cannot embed Joule or call it as a general assistant. Its agents can invoke specific Joule Agents over A2A once SAP’s Agent Gateway reaches your tenant |
| ECC and on-premise | Assistants and agents are “designed for cloud”; on-premise is an interim path | A commercial commitment before it is a project |
| Private cloud | Supported, with more customer-managed configuration | Budget for network, identity and role work |
| Other vendors’ agents | Outbound: text only; 60-second synchronous window, async via push notifications. Inbound: rolling out in phases, “not yet supported” per the Architecture Center | Cross-vendor agent work exists, in a narrow form |
| Maturity | Of Joule Studio, SAP’s CPO for Business Suite said in May 2026: “Anytime more complex agents were involved, it had limited capabilities.” General availability now underway in phases, per SAP’s October 2026 release highlights | Evaluate the current release, not the 2025 demos |
| Cost forecasting | AI Units per agent action; a standard list price per block of 100 units; overage at the contract’s excess-use rate | The unit price is findable. The cost of an agent depends on how many actions each case takes, which you learn by running it |
| The record | Assistants work while “maintaining audit trails” | The trail covers the SAP steps, and lives in SAP |
SAP’s course on integrating Joule with non-SAP applications allows two routes out. The first is Joule Studio, which calls other systems’ APIs “from within SAP BTP”. The second is the Joule Action Bar from SAP’s WalkMe acquisition, an overlay that “does not embed Joule into non-SAP applications at the code level.” It rules out exposing Joule “as a public REST API for arbitrary third-party consumption” and says “Identity and authorization are never delegated to non-SAP systems”. That keeps Joule’s view of a cross-system process in SAP BTP: coherent for SAP work, and the wrong place for the whole record of a process SAP touches at two steps out of five.
Does SAP Joule work with ECC?
Only conditionally, through an interim path SAP announced in May 2026. SAP’s knowledge base still files Joule on ECC on-premise under “cloud only support” and “on-premise not supported”, and the Sapphire path requires a commitment to SAP Cloud ERP.
SAP Knowledge Base Article 3733573 carries both keywords in its public preview. At Sapphire in May 2026, CEO Christian Klein said, as The Register reported: “The majority of our Joule assistants and agents [will be available] also on-prem, on ECC, and S/4HANA for customers that have already committed the majority of the landscape to the journey, as an interim solution so that they can benefit from AI while they are modernizing.” In July 2023 he had told investors the opposite. Three conditions come with the offer.
- A commitment. SAP’s Sapphire release offers “select AI scenarios” to customers “that commit to transitioning the majority of their current landscape to SAP Cloud ERP”. CIO.com reported the threshold: customers “must shift at least 50% of their maintenance spending to the cloud before they can enable Joule assistants on premises”, which an SAP spokesperson confirmed.
- A contract. The offer “will only be available to customers signing up for the Max Success Plan, a commercial deal”, The Register reported, with general availability planned for May 2026. SAP’s Q2 and Q3 2026 release highlights do not mention the offer, so ask your account team whether it is live and which scenarios it covers.
- A direction. SAP’s chief strategy officer, Sebastian Steinhaeuser, said in a media briefing reported by CIO.com that “our Joule assistants and agents are designed for cloud”.
SAP’s wording varies, from “select AI scenarios” in the release to “the majority” of assistants and agents from Klein, so get the list for your release in writing.
For an ECC owner, Joule is a RISE decision with an AI bridge attached. The alternatives are a layer of your own, or third-party agents that run against ECC directly. CIO.com reports that MyWave, an SAP partner, “offers AI agents that run natively on ECC without requiring migration or a 50% cloud commitment”. Both depend on what your contract lets non-SAP software do with SAP’s APIs, which SAP’s April 2026 API policy made a contract question. Both also depend on your custom code, covered in legacy modernisation with AI agents.
Is SAP Joule available on premise or in private cloud?
In private cloud, yes: Joule supports SAP S/4HANA Cloud Private Edition, the ERP inside RISE with SAP. On premise, only through the interim path above, for customers already committed to SAP’s cloud.
Private Edition is not the easy case. SAP’s setup lesson says it “requires a higher degree of customer managed configuration, including network connectivity, identity integration, content exposure, and role design when compared to the Public Edition.” Since SAP’s Q2 2026 release, one Joule formation can connect several Private Edition systems or clients, which matters for groups that run one system per legal entity or country.
Some of it comes included. RISE with SAP customers “will have three assistants activated within their first year”, per the Sapphire release. CIO.com reports up to three Joule Assistants at no additional cost for Cloud ERP Private customers, in finance, HR and the supply chain. Try those on your own data before buying AI Units.
Can you use SAP Joule without RISE?
For SAP’s cloud applications, yes, but for the ERP only with a commitment to SAP’s cloud. Base AI, which includes Joule, comes with every SAP cloud subscription, so SuccessFactors, Ariba or Concur users have Joule wherever the ERP runs. SAP notes that embedded AI availability varies by SAP application.
For the ERP, the routes are RISE, GROW or the interim offer above. GROW customers “receive full portfolio access at onboarding” to Joule Assistants, according to the Sapphire release. Muhammad Alam, SAP’s board member for product and engineering, said the interim offer would be open to “customers that have started their modernization journey on RISE with SAP”, The Register reported. For an ECC owner hoping for a fourth route, SAP offers none in October 2026.
Does SAP Joule support MCP?
Yes, in one direction. Joule can use tools over MCP, including MCP servers you create in SAP Integration Suite, which SAP says “are also accessible in the Joule studio”. SAP documents no MCP endpoint for Joule itself. Its route in for other vendors’ agents is A2A, which SAP’s Architecture Center calls “the preferred approach”. It runs through an Agent Gateway that SAP is rolling out in phases and that the same Architecture Center still lists as not yet supported.
In buyer terms, MCP (Model Context Protocol) is how an AI agent calls a tool, and A2A (Agent2Agent) how one agent hands a task to another. SAP’s Architecture Center, updated on 26 October 2026, and its Q3 2026 release highlights show which way work can flow.
| Direction | How | Status, October 2026 | What you need |
|---|---|---|---|
| Joule uses your tools or a third-party MCP server | MCP servers created in SAP Integration Suite, whose MCP Gateway can also front external MCP servers, used from Joule Studio | Documented in the Architecture Center | SAP Integration Suite with the MCP Gateway, plus Joule Studio |
| Joule Work uses SAP and non-SAP applications | MCP tools and A2A integrations | General availability underway in phases | Joule Work |
| Joule hands a task to your agent | A2A, outbound (“Bring Your Own Agent”) | Documented; text messages only; 60-second synchronous window, async via push notifications | Joule, an A2A server you run, and an Identity Authentication Service (IAS) App2App trust relationship |
| Your agent calls a Joule Agent | A2A through SAP’s Agent Gateway | Rolling out in phases per SAP’s TechEd 2026 guide; “not yet supported” per the Architecture Center | Joule Agents and the gateway |
| Your agent calls SAP APIs, without Joule | MCP through the MCP Gateway in SAP Integration Suite | Documented reference architecture; features depend on the service plan | SAP Integration Suite with the MCP Gateway capability |
| Your application calls Joule as a general assistant | None | Not supported, per SAP’s course | Not available |
Agent-to-agent is narrower than the names suggest. When Joule calls an outside agent, “Only the text message type is currently supported” and “Joule expects a response from the agent server within 60 seconds”. Longer tasks report back through push notifications. Inbound calls to Joule Agents are rolling out in phases per SAP’s TechEd 2026 guide. The A2A and MCP reference architecture, updated on 26 October, still says “the bidirectional communication with 3rd-party and self-hosted agents through Agent Gateway is not yet supported”. SAP’s Copilot Studio reference architecture says “The Agent Gateway is not yet generally available (GA).” Ask which applies to your tenant.
The route most buyers miss runs around Joule. The MCP Gateway exposes “SAP and non-SAP APIs as governed, MCP-compliant tools” to any agent, on-premise SAP APIs and external MCP servers included. That reference architecture shows a Copilot Studio agent calling SAP this way, “so every tool call runs in the context of the signed-in business user and respects existing SAP authorizations”, with no Joule in the path. Because SAP documents this route itself, it is the kind of pathway that SAP’s April 2026 API policy points to, so confirm it against your contract. Expect the packaging to change: the TechEd 2026 guide announces SAP Enterprise AI Gateway, built on SAP Integration Suite, with “a standardized MCP gateway” and general availability planned for Q1 2027.
On licensing, Joule Studio needs Joule, “via AI Units entitlement or zero-cost Joule Base SKU”, per SAP’s pricing page. It also needs the SAP BTP Enterprise Agreement (BTPEA), the Cloud Platform Enterprise Agreement (CPEA) or pay-as-you-go (PAYG). The MCP Gateway needs SAP Integration Suite, and the Architecture Center notes that “MCP feature availability depends on the service plan.”
SAP Joule vs Microsoft Copilot: do you need both?
They are not alternatives: Joule works inside SAP, Microsoft 365 Copilot inside Microsoft 365, and SAP offers a two-way integration between them. A company that runs both suites will usually run both assistants. It should know that the bridge links two windows without creating one record of the work that crosses them.
Joule has been generally available inside Microsoft 365 Copilot and Teams since SAP’s Q2 2025 release, and SAP’s Q4 2025 highlights report that “Bidirectional integration between Joule and Microsoft 365 Copilot has been completed.”
SAP’s setup course lists the prerequisites, among them a licensed Microsoft 365 Copilot environment, an activated Joule instance and “Proper identity alignment between SAP and Microsoft environments”. The integration is opt-in and starts with Teams. On cost, SAP’s product page says: “This AI offering is included with Joule Base at no additional cost. A subscription to Joule Base or AI Units is required to use it.” Microsoft’s licensing page now names the product Microsoft Copilot. It says the product “is available with Microsoft 365 E7 or as an add-on for eligible commercial, US Government, and education subscription plans”. What a Copilot seat returns is a separate question.
No integration fixes the next part. SAP’s course says it “connects Joule and Microsoft 365 without merging them into a single system”. In the quality claim, Joule can surface the quality notification and, with the right skill or agent, the credit note. Copilot can summarise the Teams thread where engineering and sales argued over liability. Why the claim was accepted, and the precedent it sets for the next one, sits in neither.
| SAP Joule | Microsoft 365 Copilot | The two integrated | An owned layer | |
|---|---|---|---|---|
| Native reach | SAP applications that support it | Microsoft 365 applications such as Teams and Outlook | Each in its own suite, reachable from the other | The systems you connect, through each one’s permitted interface |
| ECC and on-premise | Interim path through the Max Success Plan, after a cloud commitment | Not an ERP assistant. Copilot Studio agents can reach SAP APIs, on-premise ones included, through SAP’s MCP Gateway | Follows Joule’s terms on the SAP side | Reads ECC through the interfaces your SAP contract permits |
| Cost, per public pages | Base AI with every SAP cloud subscription; agents in AI Units, at a standard list price per block of 100 units | With Microsoft 365 E7 or as an add-on | Included with Joule Base; both licences still apply | A fixed fee to build and a recurring fee to run, no rate card, plus your own cloud and model costs; terms on the services page |
| Where the record of a cross-system decision ends up | SAP’s audit trail, for the SAP steps | Microsoft 365, for the Copilot steps | Split between the two, while the third system keeps its own | A store you own, across all three |
The right-hand column is what we build, so hold us to it. It also costs more to start than switching on an integration you already pay for.
Is SAP Joule free, and how much does it cost?
Partly free. Base AI, which covers Joule Work Base and embedded AI, comes “with every SAP cloud subscription”, with “no AI Units or additional paid license required”. Agents and SAP Joule for Consultants are Premium AI, billed in AI Units. SAP publishes how many units each consumes and a list price for the units, but not how many actions your agents will take.
The table is from SAP’s AI pricing page, except the last row, from the integration’s product page.
| What you use | How SAP charges | Published unit |
|---|---|---|
| Joule Work Base and embedded AI | Included with SAP cloud subscriptions | No AI Units consumed |
| Joule Work, Agentic Thinking | AI Units per action | Tracked at the action level |
| Joule Agents, run by Joule Assistants | AI Units per agent action; no separate charge for Assistants | 0.02 AI Units per action for standard agents, 0.05 for advanced |
| AI Features, such as Document AI | AI Units per request or per record processed | Rates in the SAP AI Features Guide |
| SAP Joule for Consultants | Per assigned user per month | 35 AI Units, including a pooled 22,900 requests per user; then 2 AI Units per 1,000 requests |
| Joule Studio | Free to design; production runtime billed on compute, storage, agent memory, workflow execution and AI tokens | Through BTPEA, CPEA or PAYG |
| Joule and Microsoft 365 Copilot integration | Included with Joule Base | Joule Base or AI Units subscription required |
AI Units are bought annually under one SKU, shared across Premium AI, and “Unused AI Units expire after 12 months.” An agent action is one step, “such as calling a service, triggering a workflow, or generating a response”. SAP’s AI Units page shows a US dollar list price and says packages “are priced in blocks of 100 units” and “can be purchased at a standard list price at the contract date”. The AI Features Guide it links to lists “the factors for converting the usage of a solution in business metrics”: rates in AI Units, not currency. Usage beyond what you bought is “charged at the applicable AI Unit rate per the excess use terms of the contract”. For those rates and terms, the pricing page points to the AI Features Guide and your SAP account executive.
So model the volume before you sign for units. As an illustration, not a quote: a standard agent taking 25 actions per case uses 0.5 AI Units per case. At that rate, 20,000 cases a year use 10,000 AI Units, or 100 blocks of 100. Joule Studio adds a second meter, BTP runtime for custom agents in production. ECC customers must also sign the Max Success Plan, a commercial deal whose terms we could not find on any public SAP page.
Is SAP Joule agentic AI?
In part. Joule is an assistant inside SAP applications. Joule Assistants and the Joule Agents they run execute multi-step workflows, and that agentic part is the paid part. Building your own agents is the least mature part, by SAP’s own account.
SAP’s pricing page describes Joule Agents as “purpose-built AI agents that automate well-defined, multi-step enterprise workflows across your organization”. The Q3 2026 highlights expand the Joule Assistants portfolio, from financial closing to purchasing, and add “dozens of specialized agents”. Those are SAP’s agents for SAP’s processes, and “well-defined” is the accurate word.
Custom agents come from Joule Studio. “Joule Studio adoption has been minimal compared to what we’d like,” Manoj Swaminathan, SAP’s chief product officer for Business Suite, said in a briefing reported by CIO.com in May 2026. “Anytime more complex agents were involved, it had limited capabilities.” CIO.com reported general availability as expected in the third quarter, a year behind the original target. SAP’s Q3 2026 highlights, published on 26 October, say “The general availability for Joule Studio is now underway in a phased approach.”
What LLM does SAP Joule use?
No single model. SAP says its platform combines third-party models with “SAP’s own foundation models for ABAP code generation and predictions on structured data” and domain models pre-trained on SAP’s code, data models and business processes. Who picks the model depends on who built the agent.
- Agents you build. With Joule Studio, business users and developers can build skills and agents “choosing from more than 70 AI models”, per SAP’s SAP Connect release of 6 October 2026.
- Agents SAP delivers. SAP makes the choice. Its 8 October 2026 post on Joule Work says each interaction can “draw on the model best suited for the task”. Its Q2 2026 highlights say “SAP Domain Models are running under the hood of Joule and Joule Studio and are not directly exposed to customers.”
At Sapphire 2026 SAP named Anthropic’s Claude among the models that will power Joule agents in HR, procurement and supply chain. It named Mistral AI and Cohere as sovereign model options on SAP’s cloud infrastructure. Mistral has since reached general availability: SAP’s Q3 2026 highlights list Mistral on SAP Business AI Platform as generally available, with Mistral models “deployed locally on SAP Cloud Infrastructure”. A fully sovereign version is planned for early 2027.
For a buyer in DACH or the Nordics, ask which model runs each SAP agent you license, in which region, and whether a sovereign option covers it: SAP names the providers, not the mapping. Joule Studio gives model choice to the agents you build inside SAP BTP. A layer you own extends that choice to the steps outside SAP. The HR workflow can run on a model hosted in an EU region and the supplier-email workflow on another, and changing either needs no SAP contract change.
When is SAP Joule enough on its own?
A period-end close in S/4HANA Cloud, a requisition raised and approved in SAP, an HR request handled in SuccessFactors: when a process starts and ends inside SAP’s cloud applications, Joule brings SAP’s semantics, authorizations and audit trail. A layer of your own on top would duplicate what Joule already knows.
Start with Joule, not with an independent build, when:
- you are moving to RISE or GROW anyway, and the assistants SAP activates in the first year are still untried on your data;
- your people live in Teams and mostly ask SAP about orders or invoices, which the Copilot integration handles at no extra cost on the SAP side;
- SAP already ships an agent for the standard process, such as financial closing, so your own would duplicate SAP’s work and miss its upgrades;
- the process is regulated inside SAP and its audit trail is the one your auditors already read.
Expect your integrator to start in Joule Studio. At Sapphire, SAP launched a EUR 100 million fund for SAP partners “to help customers deploy SAP-built AI assistants and agents”, per the Sapphire release. The fund is also open to partners that build agents with Joule Studio. For SAP-only work that is a sensible default. For a process that crosses vendors, settle two things before the statement of work is signed: which store holds the agent’s decision record, and who keeps it when the programme closes. Forward-deployed engineer vs consultant vs system integrator covers who carries the delivery risk.
The case for a layer of your own starts where the process leaves SAP and the decision depends on what happened in the other systems.
Where does cross-system context live if not in Joule?
In a layer the company owns, outside every vendor’s assistant. That layer is a context engine that holds the cross-system state, the rules and the record of how decisions were made, fed by SAP, Microsoft 365 and the CRM alike. Joule can still do the SAP steps, but by SAP’s design it remembers only the SAP part.
In the quality claim, why this claim got a credit note and the last similar one did not is recorded nowhere. That is exactly what an agent needs to handle the next claim the way your company would.
Joule can call an agent you run over A2A, within the limits above, and your agents can reach SAP through the APIs your contract permits or SAP’s MCP Gateway. SAP data can stay in Business Data Cloud, Fabric or Databricks, compared in where ERP context lives. The owned layer adds the record across all of them, readable by whichever model you choose. Audit trails for AI agents covers what it has to hold in a regulated process.
It has a cost. It is another system to run alongside SAP’s release cycle, and it carries its own cloud and model spend where Joule’s agents bundle that into AI Units. It is also worth nothing unless agents read the record back. It belongs on a process that crosses vendors and that you already measure, such as the cost of quality claims or the days a credit note takes.
That is the shape of a Nucleo engagement: forward-deployed engineers take one cross-system process and build the context engine it runs on inside your stack, model-agnostic. They put agents on top, including agents Joule can call where the process starts in SAP.
FAQ
What are SAP Joule’s limitations? Joule is natively embedded only in SAP applications, and SAP offers no general-purpose API for other applications to call it. ECC and on-premise access needs a cloud commitment. Agent-to-agent links with other vendors are narrow or still rolling out. Agent costs are hard to forecast: SAP lists AI Units at a standard list price, but what an agent costs depends on how many actions each case takes.
Does SAP Joule work with ECC? Only conditionally. At Sapphire in May 2026 SAP announced an interim path that brings Joule assistants and agents to ECC through the Max Success Plan. It is for customers that commit the majority of their landscape to SAP Cloud ERP. SAP’s release promises ‘select AI scenarios’, so get the list in writing. CIO.com reported the condition as shifting at least 50% of maintenance spending to the cloud.
Is SAP Joule available on premise? Only through SAP’s interim path for ECC and on-premise S/4HANA customers that have committed to its cloud. S/4HANA Cloud Private Edition under RISE with SAP is supported, with more customer-managed configuration than the public edition.
Does SAP Joule support MCP? Yes, in one direction. Joule can use MCP tools, including MCP servers built in SAP Integration Suite and Joule Work’s connections to non-SAP applications. SAP documents no MCP endpoint for Joule itself. Its route in for other vendors’ agents is A2A, through SAP’s Agent Gateway. SAP is rolling the gateway out in phases, and its Architecture Center still lists it as not yet supported. Outside agents can also call SAP APIs without Joule through the MCP Gateway in SAP Integration Suite.
SAP Joule vs Microsoft Copilot: do you need both? Usually both, if you run SAP and Microsoft 365. SAP’s two-way integration, included with Joule Base, lets users reach Joule from Microsoft 365 Copilot. It connects the two without merging them, so neither holds the record of work that crosses both and a third system.
Is SAP Joule free? Base AI, including Joule Work Base, comes with every SAP cloud subscription at no extra cost. Agents are billed in AI Units, 0.02 per action for standard agents and 0.05 for advanced ones. SAP sells AI Units in blocks of 100 at a standard list price. The number that is hard to know in advance is how many actions your agents take per case.
What LLM does SAP Joule use? No single model. SAP combines third-party models with its own models for ABAP code and structured-data predictions, and it chooses the models behind the agents it delivers. Custom agents built in Joule Studio can choose from more than 70 AI models. SAP named Anthropic’s Claude among the models that will power Joule agents in HR, procurement and supply chain. Mistral’s platform is now generally available on SAP Business AI Platform, with Mistral models deployed on SAP Cloud Infrastructure.
Is SAP Joule agentic AI? In part. Joule Assistants coordinate Joule Agents that run multi-step SAP workflows, billed per action in AI Units. Custom agents come from Joule Studio. SAP said in October 2026 that Joule Studio’s general availability is underway in phases. In May, SAP had admitted that the first version had limited capabilities for complex agents.
Related reading
- Salesforce fixed the CRM. Workday fixed HR. Nobody owns the handoffs.
- Microsoft Frontier Company: whose intelligence does it protect?
- Salesforce’s own partners are not seeing Agentforce ROI
- Legacy system modernization with AI agents: the mainframe and COBOL angle
- Audit trails for AI agents: what regulated enterprises actually need
- Own your intelligence: what it actually takes
Nucleo is an AI-native transformation company for European mid-caps. Our forward-deployed engineers build the context engine your company runs on, inside your stack and model-agnostic, so the work that crosses SAP, Microsoft 365 and your other systems is recorded somewhere you own. See how an engagement works, or write to us.
Sources: SAP Learning, integrating Joule with non-SAP applications; SAP Learning, setting up Joule for SAP S/4HANA Cloud Private Edition; SAP Learning, setting up Joule with Microsoft 365 Copilot; SAP Knowledge Base Article 3733573; The Register, SAP U-turn brings AI features to ECC and on-prem S/4HANA; CIO, SAP’s AI offer to legacy customers comes with a catch; CIO, SAP’s AI promises last year? Most are still rolling out; SAP, Sapphire 2026 press release; SAP, Business AI release highlights Q2 2026; SAP, AI release highlights Q3 2026; SAP, TechEd 2026 innovation news guide; SAP Architecture Center, A2A and MCP for AI agent interoperability; SAP Architecture Center, Microsoft Copilot Studio and the MCP Gateway in SAP Integration Suite; SAP, AI pricing; SAP, AI Units; SAP, Joule and Microsoft 365 Copilot; SAP, Business AI release highlights Q2 2025; SAP, Business AI release highlights Q4 2025; Microsoft Learn, Microsoft Copilot licensing; SAP, Joule Work and SAP Business AI Platform; SAP, SAP Connect 2026 press release.