Joule and Microsoft 365 Copilot Integration

What you will learn

• Scope a Joule and Microsoft 365 Copilot request as one or two work packages by naming which direction (Copilot calls Joule, Joule calls Copilot) each requirement needs
• Check the four prerequisites of the SAP integration guide, section 4.14, and run the pre-flight ladder before touching Microsoft Entra
• Draw a tenant plan that respects the 1:1 relationship between a Joule environment and a Microsoft Entra ID tenant, including a dedicated test tenant
• Configure the Copilot-to-Joule direction in eight steps: Entra application, Corporate IdP, system type 'M365 Copilot for SAP Joule', Joule Booster or formation, Custom Engine Agent install
• Test the integration with a persona-based pack that proves authorisation parity and the answer-source label
• Name the owners of the Entra application, the Joule app package and the system, and reconcile the Microsoft Agent Registry with SAP AI Agent Hub by hand

Module overview

Who this is for. Your client runs SAP and Microsoft 365 side by side, and a steering committee member has asked: "Can Joule and Copilot just talk to each other?" After this module you can scope the answer as work packages, walk the configuration path from SAP's integration guide, plan the tenants so the test landscape does not break, and name who owns which agent registry afterwards. It assumes AI and LLM fundamentals and pairs with Joule rollout: activation, roles, identity, tenancy; underneath the marketing, the Microsoft 365 Copilot integration is an identity-federation exercise between two cloud identity systems. For the protocols that sit next to it see MCP and A2A, for building your own Joule agents “Building Joule Agents with Joule Studio”. Facts are as of 28 October 2026.

Source: SAP — Bi-directional integration between Joule and Microsoft 365 Copilot (product page for both directions)

Prerequisites

• AI & LLM Fundamentals for SAP Consultants or equivalent working knowledge of agents and identity
• Basic familiarity with SAP BTP subaccounts and SAP Cloud Identity Services
• Basic familiarity with Microsoft Entra ID concepts (tenants, app registrations) is helpful but not required

Outcomes

• Scope a Joule–Microsoft 365 Copilot integration request into one or both configuration directions with the correct prerequisites for each.
• Plan a Joule development/test landscape that respects the 1:1 Entra-tenant constraint without a failed first attempt.
• Produce a cutover checklist for the Copilot-to-Joule direction that accounts for the Custom Engine Agent propagation delay.
• Present the SAP/Microsoft data-responsibility boundary accurately to a client's security or data-protection stakeholder.