Home›Agents›SAP Joule Agents

AgentenCode evidence profileEnterprise

✓ Editorially reviewedChecked: October 1, 2026

Agent profile · Enterprise

SAP Joule Agents

SAP Joule Agents is classified by AgentenCode as a business agents from SAP. It belongs to the Enterprise category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.

SAPEnterpriseOrganizations

View profile ↓Check sources ↓

Enterpriseeditorial classification

SAPprovider

9 primary sourcessource status

October 1, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for SAP Joule Agents

Direct answer: AgentenCode currently documents 7 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.

EU AI ActEvidence context only. AgentenCode does not infer legal applicability or compliance from individual product controls.

GDPRPrivacy and security signals are documented field by field. Data residency alone is not a compliance or transfer assessment.

Privacy contextPrivacy & data2 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.

Security contextSecurity & access4 of 10 documentedEncryption, SSO, SCIM, RBAC, roles and credential handling.

Human controlHuman control0 of 10 documentedApproval, oversight, permissions and stop or rollback controls.

TraceabilityAudit & traceability1 of 8 documentedAudit logs, APIs, SIEM, observability, tracing and activity history.

Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.

Field-level evidence

Documented controls and values from primary sources.

Documented yesDocumented valueUnknown remains unknown

High confidence

API · Async

Yes — documented

Async API integration is demonstrated.

Scope: joule_studio_code_editor_sample · verified 2026-10-01 · Primary source ↗

High confidence

Deployment · Low Code

Yes — documented

Low-code agent building is documented.

Scope: joule_studio · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · Available

Yes — documented

Joule Studio documents audit logging for product-specific events.

Scope: joule_studio_classic · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Mcp · Control Tower Registration

Yes — documented

MCP destinations are governed through control-tower registration.

Scope: joule_studio_classic · verified 2026-10-01 · Primary source ↗

High confidence

Governance · RBAC

Yes — documented

Joule Studio access is controlled through assigned roles and role collections.

Scope: joule_studio_classic · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SSO · Oidc

Yes — documented

OIDC trust with SAP Identity Authentication is required for Joule.

Scope: joule_btp_trust_configuration · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SSO · Saml

No — explicitly documented

Explicit negative: SAP documents that SAML-based trust is not supported for the Joule BTP trust configuration.

Scope: joule_btp_trust_configuration · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Managed

Yes — documented

SAP operates Joule as a managed multi-tenant service on SAP BTP Cloud Foundry.

Scope: sap_joule_btp_cloud_foundry · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Available

Yes — documented

Joule is available in region-specific data centers with documented subprocessor regions.

Scope: sap_joule_supported_data_centers · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Customer Region Selectable

Yes — documented

Customers can select a supported Joule data center when provisioning/cross-consuming Joule, subject to availability and product constraints.

Scope: sap_joule_cross_consumption_data_center_selection · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · A2A · Supported

Yes — documented

A2A integration is demonstrated by SAP.

Scope: joule_studio_and_code_editor · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · Mcp · Client

Yes — documented

SAP's official Joule Studio sample demonstrates MCP server tools used by a Joule agent.

Scope: joule_studio_agent_builder · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · Mcp · Remote

Yes — documented

Joule Studio classic supports remote MCP server connections.

Scope: joule_studio_classic · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · In transit

TLS

Joule runs on SAP BTP Cloud Foundry, where SAP documents TLS protection for all user access.

Scope: joule_user_access_on_sap_btp · verified 2026-10-01 · Primary source ↗

Evidence-backed overview

What is SAP Joule Agents?

Product-specific evidence for SAP Joule Agents

This profile links 9 unique primary sources across the product profile, field-level evidence, trust controls and documented relations. The points below describe this product’s stored evidence rather than generic characteristics of Enterprise.

Data Residency

Yes · Scope: sap_joule_supported_data_centers · verified 2026-10-01.

Primary source ↗

Region auswählbar

Yes · Scope: sap_joule_cross_consumption_data_center_selection · verified 2026-10-01.

Primary source ↗

Verschlüsselung in transit

TLS · Scope: joule_user_access_on_sap_btp · verified 2026-10-01.

Primary source ↗

Audit Logs

Yes · Scope: joule_studio_classic · verified 2026-10-01.

Primary source ↗

governance · mcp · control_tower_registration

Yes · Scope: joule_studio_classic · verified 2026-10-01.

Primary source ↗

RBAC

Yes · Scope: joule_studio_classic · verified 2026-10-01.

Primary source ↗

AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.

1primary source

14field-level evidence claims

7documented trust controls

4history events

How to read the evidence

The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.

AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.

Decision context

Provider and category

SAP Joule Agents is documented under Enterprise and is associated with SAP. Category labels help navigation but do not replace product-specific evidence.

Verification status

The public profile is marked editorially reviewed and was last checked on October 1, 2026.

Trust coverage

7 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.

Source-first use

For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.

Capabilities, strengths and deployment checks for SAP Joule Agents

SAP Joule Agents is classified as Business Agents from SAP. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.

Finance

This use case is part of the stored profile for SAP Joule Agents. The related strength is “SAP-Geschäftskontext”. In a production evaluation, the practical boundary to verify is: Geschäftsrollen und Datenrechte prüfen.

HR

This use case is part of the stored profile for SAP Joule Agents. The related strength is “Integration in Kernprozesse”. In a production evaluation, the practical boundary to verify is: Kritische Buchungen oder Entscheidungen menschlich freigeben.

Supply Chain

This use case is part of the stored profile for SAP Joule Agents. The related strength is “Unternehmensdaten und semantischer Kontext”. In a production evaluation, the practical boundary to verify is: Verfügbarkeit je SAP-Produkt kontrollieren.

SAP-Prozessautomation

This use case is part of the stored profile for SAP Joule Agents. The related strength is “Agenten-Zusammenarbeit”. In a production evaluation, the practical boundary to verify is: Geschäftsrollen und Datenrechte prüfen.

What to verify before adoption

Geschäftsrollen und Datenrechte prüfen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Kritische Buchungen oder Entscheidungen menschlich freigeben. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Verfügbarkeit je SAP-Produkt kontrollieren. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.

Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.

Verified history

The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.

October 1, 2026 · Source Maintenance
October 1, 2026 · Source Maintenance
September 30, 2026 · Verification Update
September 28, 2026 · Schema Upgrade

Official sources

This profile links 9 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.

Frequently asked questions

What is SAP Joule Agents?

SAP Joule Agents is listed by AgentenCode as an enterprise agent or agentic product from SAP.

How much trust evidence is documented for SAP Joule Agents?

The current trust layer documents 7 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.

When was this profile last checked?

The current profile verification date is October 1, 2026. The linked primary sources remain authoritative if the product changes between checks.

Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.