SAP Joule Integration Readiness

Summary

The two-way integration between SAP Joule and Microsoft 365 Copilot is now live, making it easier to work across both platforms. But for many organizations, the gap between what the integration promises and what it requires in practice is larger than expected. Before committing, there are four areas every organization should understand first.

The Integration of Joule and Microsoft 365 Copilot

The launch of the two-way integration between Joule – SAP’s generative AI copilot for SAP and third-party applications – and Microsoft 365 Copilot – The AI assistant embedded within an enterprise license – in Q4 2025 was a major milestone in the SAP and Microsoft partnership. The goal of the integration is to let users access SAP data directly from Microsoft Teams and Microsoft 365 Copilot without switching between applications. Conversely, it also enables users in Joule to use information from Microsoft 365, including emails, calendar events, and Teams conversations, to make more informed decisions.

Enterprise integrations are rarely as simple as they appear at launch. The organizations that get the most from it are those that understand what it requires before they begin. There are four areas to consider.

Your SAP Landscape

Deployment Type	Details
On-premise S/4HANA	Joule is not natively supported, and SAP has confirmed this is not on the current roadmap for classic on-premise systems. If your organization is running on-premise ECC or S/4HANA on-premise, this integration is not currently available to you, regardless of what Microsoft Licenses are in place.
S/4HANA Cloud Public Edition	Joule is supported, but only from release 2408 onwards. If your system is on an earlier release, an upgrade is required before any integration work can begin.
S/4HANA Cloud Private Edition	Joule entitlements are included by default in Cloud ERP contracts. If you are an existing RISE customer, you will need to request them from your SAP Account Executive.
Additional SAP Cloud Applications	Beyond just S/4HANA, Joule is available in a range of SAP cloud applications including SuccessFactors, Ariba, and Concur, with the level of capability varying across these products. It is worth mapping which applications your users work in and confirming they are supported in your deployment model.

The Licensing Position

Licensing Level	Details
Baseline integration	To enable the connection between the two services, you need Joule Base active on your SAP BTP account and a standard Microsoft 365 license for each user. This covers the core setup but provides a limited experience.
Fuller integration	To access Microsoft 365 Copilot’s AI capabilities from within Joule, a Microsoft 365 Copilot license is also required. This is a premium add-on, priced separately from a standard Microsoft 365 subscription, and for a large workforce the cost can be significant. It should be factored into the business case before any implementation work begins.
Existing Copilot deployments	Even in organizations that have already licensed Microsoft 365 Copilot, active weekly usage can often run below the number of licenses purchased. If Copilot has been licensed but not meaningfully rolled out across the business, addressing this first will make the Joule integration more impactful.

The Technical Foundation

Configuration Area	Details
Identity services	SAP and Microsoft each manage user identity through their own services, SAP Cloud Identity Services and Microsoft Entra ID respectively. For the integration to work, both need to recognize the same user. If the two identities are not correctly linked, authentication will fail. This is a common issue in organizations that have grown through acquisition, run multiple SAP systems, or have managed their SAP and Microsoft identity setups independently.
Trust relationship	Establishing a trust relationship between SAP Cloud Identity Services and Microsoft Entra ID.
App configuration	Configuring the relevant app registrations, API authorizations, and BTP destinations.
Identity Authentication	Ensuring all connected SAP solutions operate under the same SAP Identity Authentication tenant.
Best practice	Involving both SAP and Microsoft technical teams early, ideally at the architecture stage, is the most effective way to avoid the rework that typically follows a missed identity requirement.

What the Integration Does not Cover

Limitation	Details
Custom agents	Custom agents are not supported. Any agents built in Microsoft Copilot Studio cannot be routed through the Joule and Microsoft 365 Copilot integration. Custom scenarios require a separate implementation approach via the SAP OData Connector and Power Platform.
Content display	Some content cannot display in Microsoft 365 Copilot. Certain outputs that Joule renders natively cannot be fully visualized within the Copilot chat interface. In those cases, users are redirected to the Joule web client to complete the interaction.
S/4HANA tenant support	Only one S/4HANA tenant can be connected at a time. Organizations running multi-system landscapes will need to consider this as part of their architecture planning.

How this Affects Business Decision-Making

None of the prerequisites mentioned should be a reason to step away from this integration. The case for connecting SAP’s business data with Microsoft’s collaboration and AI tools can be strong.

Organizations that begin with a proof of concept before the right foundations are in place can find the gap between demonstration and production readiness larger than expected. Organizations that have a clear plan across all four areas are best placed to deliver business value faster.

A structured readiness assessment before implementation begins is the most practical way to protect the business case and ensure the integration delivers what it promises.

How Can JNC Help

At JNC, we help organizations understand whether they are ready for the integration of Joule and Microsoft 365 Copilot into their landscape via readiness assessments. JNC works with SAP customers to understand the complexity and give a clear picture of what is needed before implementation can begin.

We can help with:

SAP landscape and deployment review – confirming whether your current environment supports Joule and identifying any gaps
Licensing position assessment – mapping your SAP and Microsoft license entitlements against what the integration requires
Identity and technical readiness – evaluating your current identity setup and what needs to be in place before go-live
Implementation support – guiding the integration from readiness through to deployment

As we have no commercial interest in recommending a particular licensing route or platform, our advice is independent and focused on what is right for your organization.