Joule Work and SAP Managed Joule — Rolling Out the End-User AI Workspace
As of 2026-10-04
A rollout-focused module on Joule Work, the end-user AI workspace announced at SAP Sapphire in May 2026, and SAP Managed Joule, the SAP-operated provisioning path started in SAP for Me. It separates the generally available mobile app from the Early Adopter Care web client and desktop app (GA planned H2 2026, no announcement found as of 4 October 2026), explains what SAP provisions and what identity, role and device responsibilities stay with the customer, and shows how to extend Joule Work Desktop with a custom MCP server that meets the MCP authorization rules and the SAP API policy 4/2026. A six-step lab, a worked procurement scenario and an ADKAR-based adoption plan with five metrics close the module.
What you will learn
- State the availability status of each Joule Work surface (mobile, web, desktop, custom MCP servers) with a dated source, and separate announced from generally available
- Explain what SAP Managed Joule provisions through SAP for Me, what it removes from the customer's cockpit work and what identity and role responsibilities stay with the customer
- Design a three-population access model (pilot, observer, administrator) with a named source of truth and a revocation path for each
- Plan a staged rollout of the mobile app, the desktop app and the web client with endpoint, support and exit decisions
- Specify a custom MCP server for Joule Work Desktop that meets the MCP authorization rules: protected resource metadata, PKCE, resource parameter, audience validation and no token passthrough
- Apply the SAP API policy (version 4/2026) to a custom MCP server and design an ADKAR-based adoption pilot with five measured indicators
Module overview
Who this is for. You have already activated classic Joule for a customer (M360 covers activation, roles, identity and tenancy) and you now face the question the sponsor really asks: "What does an employee actually get on Monday, and what do we have to run?" This module covers the end-user AI workspace that SAP announced at SAP Sapphire in May 2026 — Joule Work — and the provisioning model that sits underneath it, SAP Managed Joule. It does not repeat classic Joule activation (M360), agent building (M326, M350), production testing (M374) or the general change playbook (M381); it connects them to a rollout you can scope. Its second theme is extension: how a custom MCP server is connected to Joule Work Desktop with single sign-on, and what the SAP API policy says about that. Platform vocabulary: the platform underneath is SAP Business AI Platform (formerly SAP BTP); services such as SAP Cloud Identity Services keep their names.
Prerequisites
- Completion of M360 (Joule Rollout — Activation, Roles, Identity and Tenancy) or equivalent hands-on experience activating classic Joule
- Working knowledge of MCP at the level of M327 (MCP & A2A for SAP Systems) and of OAuth 2 authorization-code flows
- Optional: access to SAP for Me and to the customer's identity-provider documentation to check the actual entitlement and trust configuration before scoping
Outcomes
- Tell a sponsor, with source and date, which Joule Work surface can be promised to users today and which is Early Adopter Care.
- Write the SAP for Me provisioning checklist and the evidence plan for a cockpit the customer cannot open.
- Produce an access model in which every population has a source of truth and a revocation path.
- Specify a custom MCP server for Joule Work Desktop that an architect can review against the MCP authorization rules.
- Run an eight-week adoption pilot with five indicators measured against the team's own baseline.
Full module available to members. The full module adds: the decision framework · the end-to-end scenario walkthrough · the KPI scorecard · the anti-patterns · the code blocks · the knowledge check · the diagrams.