First, the name
There is no SAP product called “SAP Joule Desktop”. SAP calls this the Joule Work desktop app, and its own community posts also write Joule Work Desktop. It is a surface of Joule Work, not a separate product - worth knowing before you go looking through SAP documentation.
What it actually is
A locally installed client that runs at machine level and, unusually for SAP, does not require an SAP system connection to get started. It targets the work that happens outside cloud-connected SAP: local files, desktop applications and Microsoft 365.
In practice it combines local files, M365 mail and calendar, SAP knowledge, connected business systems, MCP connectors and reusable skills into one workspace. A representative task: read a calendar entry and its related emails, and produce a meeting brief with source references. It generates real Office documents that open natively rather than text you have to paste somewhere.
Availability
Early Adopter Care from Q2 2026, with general availability planned for H2 2026. It was rolled out internally to SAP employees after testing with several thousand colleagues, with selected customers on the programme for macOS and Windows. It is not GA today, and you should not plan a rollout as though it were. No Linux support has been announced.
How it differs from classic Joule
Classic Joule cannot see anything on your machine - it lives in the browser, inside an SAP application. This is the inversion: local-first, works with no SAP tenant at all, and reaches SAP systems as one connector among several. Against Joule Studio classic the comparison is a category difference rather than a feature one - this is a client, not a build tool.
Extensibility is MCP
This is the part that matters if you are building. The desktop app extends through Model Context Protocol - session-scoped MCP connectors plus remote MCP OAuth - rather than a proprietary plugin model. SAP also publishes an AI Skills Library of reusable skills that import in one click and are invoked with a slash command.
The practical consequence: whatever you expose over MCP becomes reachable from the desktop. That is the same integration surface that serves Joule Work, your own agents, and whatever model you adopt next - which is exactly why we build MCP servers over SAP systems as the durable layer rather than one-off connectors.
Where the edges are
- Authorisations still apply. Connectors need valid authentication and SAP user authorizations remain in force. The backend is still the control point.
- Backend coverage is narrow today. Native integration is confirmed for S/4HANA Cloud Public Edition; on-premise S/4HANA has needed a third-party MCP server in independent testing.
- M365 access is read-only for mail and calendar in the tested build. Local file support covers Word, PowerPoint, text, CSV, JSON and images, plus OneDrive-synced files.
- Open questions. Broader SAP system support, connector governance and pricing are all unpublished. We are not going to invent numbers for them.
Why connector governance is the real question
A desktop client that can reach local files, mail and business systems in one session is genuinely useful and genuinely worth governing. The question to put to any rollout is not whether the tool is capable, but who can add which connectors, and whether you can see what was accessed afterwards. That is an observability problem, and it is the one we work on - see Boidra Platform.
Frequently asked questions
Is there a product called “SAP Joule Desktop”?
No. The desktop client is officially the Joule Work desktop app, also written as Joule Work Desktop. It is a surface of Joule Work rather than a separate product, so if you are searching SAP documentation, use that name.
Does Joule Work Desktop need a connection to an SAP system?
Not to get started. It runs at machine level and works with your local files and Microsoft 365 without an SAP tenant. SAP systems are one connector among several, which is the inversion from classic Joule - that lives in the browser inside an SAP app and can see nothing on your machine.
Does it bypass SAP authorisations?
No. Connectors still require valid authentication, and SAP user authorizations still apply. The backend remains the control point, which is the right answer for anyone worried that a desktop client widens their access surface.
How do I connect it to on-premise S/4HANA?
Through MCP. Native business-system integration is confirmed for S/4HANA Cloud Public Edition; independent testing of an on-premise S/4HANA 2023 system required a third-party MCP server. MCP is the primary extensibility mechanism rather than a proprietary plugin model.