Joule Rollout — Activation, Roles, Identity and Tenancy
As of 2026-09-25
The rollout companion to M358 and M359: how to actually provision Joule through SAP BTP customer-managed provisioning, sourced entirely to SAP's Integration Guide (help.sap.com, dated 2026-09-14). Covers the two general prerequisites plus the BTP global-account requirement, the single-Cloud-Identity-Services-tenant and Global User ID (user_uuid) rule and its failure mode, the SAP Build Work Zone requirement table and its one-instance-per-Joule rule, the three-step provisioning procedure and the booster's re-run error, the extensibility_developer and end_user application roles and how to assign them, the App2App/Cli2Joule developer onboarding flow, the Joule Preview Landscape's two- and four-week release cadences, conversation-log governance, the irreversibility of unsubscribing, and the one-formation-per-product-tenant rule that governs every multi-entity rollout.
What you will learn
- State the two general Joule prerequisites (product licence, AI Unit SKU 8019164 or Joule Base) and the Joule-specific SAP BTP enterprise global account requirement
- Explain the one-SAP-Cloud-Identity-Services-tenant rule and the Global User ID (user_uuid) mechanism, and what breaks when it is misconfigured
- Apply the one-IAS-tenant-per-independent-entity rule to a multi-business-unit client and derive the correct subaccount architecture
- Execute the three-step customer-managed provisioning procedure and recognise and recover from the 'already in a formation' booster error
- Assign the extensibility_developer and end_user Joule application roles through SAP BTP role collections
- Explain the Joule Preview Landscape's release cadence (framework: 2 weeks, content: 4 weeks) and its current EU10/EU30 availability
- Explain the consequences of unsubscribing from Joule and the documented recovery path
Module overview
Who this is for. You are the person who will actually be in the SAP BTP cockpit provisioning Joule, not the person presenting the demo. This module is the rollout companion to M358 and M359 (Joule in CX, Joule and Microsoft 365 Copilot): both of those modules told you to "plan the tenant question in week one" and pointed here for the how. Everything below is sourced to SAP's own Integration Guide "Integrating Joule with SAP Solutions" (help.sap.com, PUBLIC, dated 2026-09-14), the document system administrators and technical consultants are explicitly told to use for exactly this task.
Prerequisites
- M333 (AI & LLM Fundamentals for SAP Consultants) or equivalent
- Working knowledge of SAP BTP cockpit navigation: subaccounts, entitlements, Security → Role Collections
- Basic familiarity with SAP Cloud Identity Services (Identity Authentication, Identity Provisioning) is helpful but not required
Outcomes
- Run a complete Joule prerequisite audit for a client before touching the BTP cockpit, catching missing entitlements before they block the booster.
- Design a multi-subaccount, multi-IAS-tenant Joule architecture for a client with several independent business units.
- Execute customer-managed provisioning end to end: trust configuration, user attributes, booster run, role collection creation and assignment.
- Advise a client accurately on Preview Landscape timing, conversation-log governance, and the irreversibility of unsubscribing.
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.