Joule is designed to provide a consistent, generative-AI–powered experience across SAP’s portfolio. Whether users interact with Joule in SAP S/4HANA Cloud, SAP SuccessFactors, or other SAP applications, the goal is the same: a unified experience that feels coherent, secure, and seamless across the landscape.
In practice, a set of concrete, step-by-step preparation missions helps organizations establish the technical foundation required for Joule. These step-by-step missions focus on establishing a unified Joule setup while activating Joule in key SAP applications, requiring consistent identity configuration and correct user provisioning across systems.
- Establish a Unified Joule Instance (This is a prerequisite for enabling Joule across the SAP landscape and ensures a single, coherent setup rather than isolated configurations.)
- Activate Joule for SAP SuccessFactors
- Activate Joule with SAP S/4HANA Cloud Public Edition
In many enterprise environments, identity and authentication setups have evolved over time, across multiple systems and tenants. This can make prerequisites, such as IAS, harder to assess and align than they appear at first. In this lesson, we will navigate through the key setup steps and landscape considerations to enable you to approach preparatory architecture discussions with clarity to guide discussions toward effective next actions.
Why Does It Matter?
A unified setup of Joule depends on all participating applications using the same IAS production tenant for authentication, as reflected in the Reference Architecture. This is a foundational requirement, not only for enabling Joule consistently across the SAP landscape, but also to establish coherent user experiences and strengthened security and compliance, more broadly across examples, such as mobile applications, API management, and general microservices security.
For additional CIO-level guidance on identity strategy and central identity services, refer to the following document: CIO Guide: Identity Lifecycle in SAP Landscapes
To better understand how the components in the integration architecture work together in practice, it helps to navigate through the setup journey, one step at a time. The following sequence reflects how Joule is typically prepared and enabled across an SAP landscape, from platform foundations to user experience integration.
One: BTP System Landscape and Sub-Account Setup
Technically, the journey with SAP Joule begins on SAP Business Technology Platform. Before any AI capability is activated, it is essential to understand and design the BTP system landscape.
This includes clearly outlining the required sub-accounts, which serve as segregated environments for different purposes such as:
- Development
- Testing
- Production
From an EA perspective, this step establishes the foundation for secure isolation, lifecycle management, and controlled rollout of Joule across environments.
Two: Configure Cloud Identity Services
With the platform prepared, attention shifts to Cloud Identity Services, which are critical for secure and consistent access management. In this step:
- Authentication and trust relationships are configured
- A unified identity foundation is established across applications and Joule
This is a pivotal architectural step. A consistent identity setup is not only required for Joule, but also improves the overall user experience, security posture, and compliance across the SAP landscape, creating the confidence needed to scale AI across business-critical scenarios.
Three: Configure Target System (example: SAP SuccessFactors)
Next, the backend systems that Joule will interact with must be configured. For example:
- SAP SuccessFactors
- SAP S/4HANA Cloud
- Other SAP solutions connected to Joule
This step ensures that each target system is fully integrated and authorized.
It is a repeatable step, performed for every backend system the organization wants to connect to Joule.
From an EA standpoint, this is where architectural consistency across systems becomes critical, especially in multi-solution landscapes.
Four: Setup Work Zone Integration and User/Role Sync Jobs
To complete the technical setup, SAP Build Work Zone integration is configured. This includes:
- Enabling integration between Work Zone and Joule
- Running user and role synchronization jobs
This step ensures that:
- Users see Joule in the right context
- Roles and authorizations are respected across applications
- The AI experience aligns with organizational structures
Five: Run Joule Booster
Once the prerequisites are configured, the final step is to initiate the Joule Booster.
The Joule Booster streamlines the setup by:
- Automating multiple configuration steps
- Ensuring required services and dependencies are activated consistently
For Enterprise Architects, this step reduces manual effort and helps ensure that the technical baseline for Joule is aligned with SAP’s recommended setup approach.
Once the core integration steps and components are in place, such as BTP subaccounts, Joule Booster, Cloud Identity Services, target system integration, and Work Zone setup, the focus shifts from technical wiring to how Joule is introduced, validated, and scaled in an enterprise landscape.
The following steps reflect the typical Joule enablement and rollout flow. These steps build on the integration foundation and illustrate how organizations move from initial readiness to productive usage and broader adoption.
Joule Enablement and Adoption Flow
One: Preparation
This phase ensures that the organization is ready to begin with Joule — not technically configuring anything at this point.
Validate prerequisites
Confirms that the basic technical, contractual, and landscape requirements are in place before activation begins.
Clarify dependency with Identity Authentication
Establishes how identity is handled across the landscape, which is critical because Joule relies on a consistent authentication setup to work across applications.
Get Joule and AI unit entitlement
Ensures the organization is entitled to use Joule and consume AI units at the global account level.
Plan the target
Defines what the organization is aiming for in the first step: which applications, which users, and which scope will be enabled initially. For most organizations, Joule adoption starts with a focused scope, typically a small number of applications or user groups, before expanding gradually as confidence, governance, and measurable value are established.
From an Enterprise Architect’s perspective, this is when early alignment is initiated, before projects, before timelines, and before expectations are set at unattainable levels.
Two: Test and Pilot
After the preparation activities are complete, the Test & Pilot phase focuses on validating the setup in a controlled environment. The goal is to confirm that Joule works end-to-end—technically, functionally, and organizationally before scaling to productive usage.
Set up Joule in the desired environment
Joule is enabled in a specific system landscape, typically a test or pilot environment. This allows organizations to validate identity configuration, application integrations, and the user experience without affecting productive operations.
Run the activation
The technical activation of Joule is executed for the selected SAP applications and users. This step puts the previously defined entitlements, identity setup, and target-system planning into practice.
Use experts for greater speed
SAP services, partner experts, or specialized enablement teams can support this phase to accelerate setup, reduce trial-and-error, and address issues that often surface in complex or historically grown landscapes.
Ticket Component: CA-Joule
During testing and piloting, any issues or questions are handled via the dedicated support ticket component CA-Joule. This ensures that incidents are routed to the correct teams and can be tracked, analyzed, and resolved efficiently.
From an Enterprise Architecture perspective, this phase provides important architectural feedback and confirmation, including:
- gaining confidence that the target architecture behaves as intended in a real system context
- validating key assumptions made during the preparation phase
- identifying insights and constraints that should be considered before moving to productive rollout
Three: Production
The Production phase shifts the focus from technical validation to sustainable business adoption. In this stage, Joule is no longer viewed as a pilot capability, but as a productive, enterprise-wide AI feature that must deliver value, operate reliably, and fit into existing governance and operating models.
Establish business case
Before moving to full production, the expected value of Joule is clarified and confirmed.
For Enterprise Architects, this step is about ensuring that the technical setup supports clearly articulated business outcomes and that AI adoption is anchored in broader transformation goals.
Set up Joule in production
Joule is enabled in the productive SAP landscape, using the finalized identity setup, entitlements, and application integrations. This step builds directly on the lessons learned during the Test & Pilot phase and applies them on a scale, with production-grade security, stability, and compliance requirements.
Test Joule with specific regard to roles to ensure a smooth rollout
Final validation focuses on role-based access and user experience. Joule’s behavior is tested across different business roles, authorizations, and applications to ensure that users see the right data, receive relevant guidance, and can seamlessly navigate into SAP processes. This step helps prevent surprises during rollout and supports confident adoption by end users.
From an Enterprise Architecture standpoint, the Production phase brings everything together:
- value, architecture, security, and operations
- moving from enablement to scale
- ensuring that Joule becomes a reliable, well-governed part of the organization's SAP landscape
Four: Expansion
The Expansion phase is when Joule evolves from a productive AI feature into a broader, cross-functional AI capability. Since the technical foundation is already in place, the focus now shifts to scaling value, extending reach, and deepening integration across the enterprise.
Add agents, extensibility, and more lines of business
Joule is extended beyond the initial set of use cases by introducing additional agents, enabling extensibility, and rolling out AI support to more lines of business. This may include activating new SAP-delivered agents, building custom agents, or connecting Joule more deeply into end-to-end processes. For EAs, this step is about ensuring that extensions remain aligned with core processes, data governance, and architectural principles.
Enable integration with Microsoft 365 Copilot
Joule is connected with Microsoft 365 Copilot to support a more seamless employee experience across productivity tools and SAP applications. This integration allows users to access SAP-driven insights and actions within familiar work environments, while maintaining enterprise-grade security, identity, and governance.
Set up document grounding capacity
Document grounding is configured to allow Joule to use enterprise documents—such as policies, manuals, or procedures—as trusted context. By grounding AI responses in approved documents, organizations improve relevance, accuracy, and traceability. From an architectural perspective, this step reinforces the importance of controlled data sources and governance as AI usage expands.
In the Expansion phase, Enterprise Architects help organizations scale responsibly:
- extending AI across functions without fragmenting the landscape
- integrating Joule into daily work beyond SAP applications
- ensuring that growth in AI capabilities goes hand in hand with governance, security, and data quality
Landscape considerations for a unified Joule experience:
Joule Adoption approach from preparation to expansion:
What This Means for You as an Enterprise Architect
This lesson helps you identify Joule-related preparation topics early and structure the appropriate conversations before activation begins. Understanding the different phases, from preparation through expansion, allows you to guide your organization confidently and plan next steps in advance.
When organizations move from planning into execution, SAP provides dedicated services and support options that can be triggered as needed:
A Guiding Hand to SAP Joule – SAP Joule Readiness Service
Supports organizations in preparing for Joule enablement by aligning on the SAP Joule approach, reference architecture, and unified SAP Cloud Identity Services setup, with a focus on authentication prerequisites.
Request Support
Unified Identity Services set-up guidance: Available via a service request using the XM Booking Tool
As an Enterprise Architect, your role is to recognize when these services are appropriate to discuss their value early in the preparation process, and assist your organization in connecting architectural readiness with a smooth Joule implementation.
Lesson Summary
This lesson explained the key preparation elements required to enable Joule across an SAP landscape. By walking through the end-to-end setup journey—from BTP landscape design and identity configuration to target system integration and Work Zone setup—you gained a clear understanding of how Joule is technically prepared and activated. The lesson also outlined the typical enablement and adoption flow, helping you see how preparation, testing, production, and expansion phases build on one another to support a secure, consistent, and scalable Joule experience across the enterprise.