What SAP announced
SAP says it is making Joule Work more interoperable by using the latest Microsoft Work IQ capabilities announced at Microsoft Ignite. Joule Work gives access to processes, transactions and unified operational data. SAP says Work IQ adds organizational context from Microsoft 365 and beyond.
This is not a single product launch. It bundles several pieces:
- Shared work context through Work IQ.
- SAP business data in Microsoft Fabric.
- Agent-to-agent delegation between Copilot Studio and SAP's Joule Agents.
- Agent monitoring through SAP AI Agent Hub.
- Two-way Joule and Microsoft 365 Copilot integration.
Joule Work itself is fairly new. SAP announced it at Sapphire 2026. Techzine reported it comes as a web client, desktop app and mobile app, and also integrates with Microsoft Teams and Slack. General availability was scheduled for the second half of 2026.
What Work IQ is
Microsoft describes Work IQ as the intelligence layer that connects Copilot and agents to an organization's knowledge, business data and tools. It says Work IQ honors the permissions and controls already in place. In Microsoft's Ignite post, it grounds Copilot's responses in a user's emails, meetings, chats, files and colleagues.
Microsoft's Ignite post also lists these Work IQ details:
- Availability: Work IQ is generally available in Foundry and Copilot Studio, and reachable over MCP, REST and A2A.
- Preview items: ERP context from Dynamics 365 and the Engage feature are marked preview.
- Governance: Admins set a tenant-wide ceiling on agent actions, and each agent's policy can narrow that ceiling but never exceed it.
- Permissions: New WorkIQ.Read and WorkIQ.Act permissions separate reading from acting.
Independent roundups have noticed that Microsoft's own posts disagree on some Work IQ statuses. One guide says two Work IQ statuses conflict between Microsoft's posts. Check the status of each capability before you plan around it.
Shipping now versus still coming
Available today
Microsoft says the Joule and Microsoft 365 Copilot integration reached general availability earlier in 2026. Microsoft's October TechEd post says hundreds of customers had shown interest. Microsoft Learn documents how it works:
- User experience: Users in Copilot or Teams tag @Joule to route SAP questions to Joule. Joule users can pull Microsoft 365 context back the other way.
- Identity: Trust runs between SAP Cloud Identity Services and Microsoft Entra ID, with the Microsoft user mapped to an SAP user.
- Supported apps: S/4HANA Cloud Private and Public Edition, SuccessFactors, selected Ariba scenarios, and other SAP cloud apps that Joule supports.
- Limit: It covers standard Joule capabilities only. Custom agents built in Copilot Studio are not routed through it.
Microsoft also says customers who don't use Joule can connect Microsoft 365 Copilot to SAP today. They use MCP servers and Copilot skills to read, write and update data in SAP ERP, including RISE with SAP, S/4HANA and ECC. The MCP servers can run on SAP BTP or Azure API Management.
Still being tested or rolling out
SAP says an agent gateway and the open A2A protocol were released earlier this month. With them, Copilot Studio agents can hand SAP-specific work to Joule Agents instead of rebuilding SAP processes. SAP says security, identity and policies carry through.
Microsoft's October 26 TechEd post is more cautious. It said the A2A-based SAP Agent Gateway integration was then being tested with selected customers. It described the MCP Gateway in SAP Integration Suite as already live and documented. Treat these as two separate routes. The SAP post does not give a precise date or list supported configurations for the A2A route.
Two-way surfacing is also future tense. SAP says "soon" its agents will show SAP insights inside Microsoft 365 when they become relevant. SAP says Joule Work will get more capable "as Work IQ capabilities roll out over time."
Data and governance claims
Fabric. SAP says Business Data Cloud Connect for Microsoft Fabric gives bidirectional, zero-copy integration. The aim is for Joule Work and Microsoft Copilot to draw on the same data without duplicating it. Microsoft's Ignite post echoes this by describing SAP Business Data Cloud connectivity to Fabric. Neither source gives performance figures or implementation details.
Agent oversight. SAP AI Agent Hub is pitched as telemetry and lifecycle visibility across SAP, Microsoft and third-party agents. SAP says admins can see which agents are running, how they are used and what value they deliver. Microsoft's wording is more modest. It says SAP AI Agent Hub and Microsoft Agent 365 are being worked toward agents that can be discovered, registered, governed and observed across both environments. That does not describe a single finished control plane. Neither company has published metrics, licensing or the scope of third-party coverage.
Customer proof. SAP cites Nestlé, which uses RISE with SAP on Azure and Joule Assistants for accounts receivable. There are no outcome numbers or deployment details. Microsoft's TechEd post offers other examples, such as Rio Tinto cutting month-end close for its largest product group from three or four days to two. Those involve Power Platform with SAP, not this Work IQ integration.
Checklist for admins
- Confirm which route you need. The managed Joule-to-Copilot link covers standard Joule scenarios. Custom Copilot Studio or Foundry agents need MCP, or A2A once it is available to you.
- Check licenses. Microsoft Learn lists Microsoft 365 Copilot licenses and the matching SAP Joule licenses as prerequisites.
- Prepare identity. You need SAP BTP with Identity Authentication Service, a Microsoft Entra tenant with admin access, and working user mapping. Learn says mismatched mapping causes authentication errors.
- Enable the agent. Turn on the Joule agent in the Microsoft 365 or Teams admin center and assign it to users or groups.
- Troubleshoot. Learn's table lists the usual symptoms:
- Joule agent not visible: the agent isn't enabled in the admin center.
- Authentication error: the trust relationship is misconfigured.
- "No SAP data found": the user isn't mapped to an SAP user.
- Timeouts: a connectivity problem.
- Define agent permissions. Decide read and act policies before agents can write back to finance or HR data.
Analysis
The strategy is sound: most enterprises will run SAP next to Microsoft 365 for years, and agents that can't cross that gap are of limited use. But "exponential AI value" is a marketing phrase, not a measured result. The SAP post has no benchmarks, and its example is a single named customer with no numbers.
The governance pitch deserves the closest scrutiny. Microsoft's Work IQ controls are described for Work IQ generally. Nothing in the evidence shows they apply identically to every SAP path. Pilot with a narrow, low-risk workflow, such as a read-only procurement query. Test identity mapping and permission trimming before agents are allowed to act on SAP transactions.
Bottom line: The managed Joule and Copilot integration and the MCP route are documented and have clear prerequisites. The A2A delegation, the unified agent monitoring and the proactive cross-surfacing of insights are mostly still in rollout, so confirm availability for your tenant before committing.
References
- How SAP and Microsoft Innovate Together to Deliver AI Value for the Enterprise - SAP News Center SAP News Center · 2026-11-20T14:15:00+00:00
- SAP launches Joule Work: an AI-chatbot that turns questions into action - Techzine Global techzine.eu
- SAP with Microsoft: AI SAP Joule & Microsoft Copilot Integration | Microsoft Learn learn.microsoft.com