Concept card

Joule and Microsoft 365 Copilot — bidirectional integration

As of 2026-09-25

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Joule and Microsoft 365 Copilot?

A managed, bidirectional integration lets Microsoft 365 Copilot/Teams users tag '@Joule' to reach SAP S/4HANA Cloud, SuccessFactors and selected Ariba scenarios, and lets SAP Joule users pull Microsoft 365 email, Teams and calendar context — built on identity federation between Microsoft Entra ID and SAP Cloud Identity Services, requiring three separate admin-owned setup steps and two independent vendor licenses.

Two vendors, one trust relationship, two entry points

Microsoft's own documentation (learn.microsoft.com, "SAP with Microsoft: AI SAP Joule & Microsoft Copilot Integration," last updated 2026-09-11) describes this as a managed, bidirectional feature — not a custom agent someone builds in Copilot Studio, and Microsoft is explicit that the two are different things covered by different articles. A user in Microsoft 365 Copilot or Teams can tag "@Joule" and ask an SAP-related question, which is routed to SAP Joule for processing; a user inside SAP Joule can separately ask for Microsoft 365 context — emails, Teams chats, calendar items — without leaving the SAP interface. Neither side needs a custom-built connector: SAP handles the natural-language processing for SAP-specific tasks, Microsoft handles the Copilot/Teams experience, and a trust relationship between the two identity systems carries the request across.

Why it matters

This is a managed feature, explicitly distinct from custom Copilot Studio or Microsoft Foundry agents built against SAP data — Microsoft documents the two as separate scenarios with separate articles, and confusing them misleads a client about build effort.
Setup requires three configuration passes owned by three different admin roles (BTP subaccount, Entra ID, Microsoft 365) across two organizations — 'enable the integration' is a coordination project, not a checkbox.
No bundled licensing exists: a client needs Microsoft 365 Copilot licenses and SAP Joule licenses independently, a budget line to raise before scoping, not after a demo has set expectations.

Key points

Architecture: Microsoft Entra ID authenticates the M365 user; SAP Cloud Identity Services (IAS) maps that identity to an SAP user; SAP Joule on BTP and Microsoft Copilot/Teams are the two user-facing interfaces.
Direction 1: '@Joule' in Copilot/Teams routes an SAP-related question to Joule (e.g. leave balance to SuccessFactors, PO delivery date or invoice status to S/4HANA Cloud).
Direction 2: from inside Joule, users pull Microsoft 365 context — email, Teams chats, calendar — without leaving the SAP interface.
Supported applications named by Microsoft: S/4HANA Cloud Private and Public Edition, SuccessFactors, SAP Ariba (selected scenarios only), plus other Joule-supported cloud apps per SAP's current list.
Explicitly excluded: custom agents built in Copilot Studio or Microsoft Foundry against SAP data — a separate, differently documented scenario.
Setup is three steps under three different admin roles: SAP Cloud Identity Services configuration (BTP), Entra ID app registration and SSO (Microsoft), Joule agent enablement in the M365/Teams admin center.
Licensing: Microsoft 365 Copilot license per user plus corresponding SAP Joule licenses — two independent purchases, no documented bundle.

Terms used on this page

Identity federation: The mechanism by which a Microsoft Entra ID user identity is trusted and mapped to a corresponding SAP user via SAP Cloud Identity Services, without a shared login.
SAP Cloud Identity Services (IAS): SAP's identity proxy that maps the federated Microsoft user to an SAP user before Joule processes a request.
@Joule tag: The prompt tag used inside Microsoft Copilot or Teams to route a question to SAP Joule for processing.
Managed integration: Microsoft's term for this SAP-Joule/Copilot feature, as distinct from a custom agent built in Copilot Studio or Microsoft Foundry against SAP data.
SAP Note 3722273: The SAP Note Microsoft points to for the latest known issues and fixes for the Joule-Copilot integration.

Sources

Full card available to members. What the full card adds: the full decision framework · the common pitfalls and their fix · the cheat sheet · the facts worth quoting.

Open in the app →