For the past decade, most companies running SAP have lived with a quiet frustration. The data that drives the business, orders, invoices, headcount, inventory, sits inside SAP. But the decisions about that data get made in Teams meetings, Word documents, and Excel spreadsheets. Switching between the two has always meant lost time, lost context, and decisions made on stale information.
What Microsoft and SAP announced at Sapphire 2026 is a direct attempt to close that gap permanently. The two companies are moving from simple integration, where one system can pull data from another, toward what they are calling agent-to-agent coordination. SAP's AI layer, called Joule, and Microsoft's Copilot will now be able to hand tasks to each other and execute them without a person managing the handoff. Nestlé is already piloting this at Sapphire, demonstrating early scenarios where Microsoft's Copilot Studio orchestrates Joule's capabilities using an open, vendor-neutral coordination standard.
This matters because of how work actually happens at large organisations. A procurement manager discussing a supplier issue in Teams no longer needs to separately log into SAP to check inventory levels or raise a purchase order. The AI systems, in theory, handle the back-and-forth across both platforms. The same logic applies in HR, finance, and logistics.
The data side of this announcement is just as important, and perhaps less understood. A product called SAP Business Data Cloud Connect for Microsoft Fabric is due in the second half of 2026. It allows SAP data and non-SAP data to be shared and used together in real time, without creating multiple copies that go out of date. For a finance director who has ever tried to reconcile SAP reports with a Power BI dashboard, this directly addresses why that is so painful today.
But there is a harder reality sitting behind all of this. Gartner estimates that around 17,000 SAP customers will still be running older ECC systems when support ends in December 2027. These organisations will stop receiving security patches and legal updates unless they pay for extended maintenance or migrate. Nearly half of the original 35,000 ECC customer base has not yet moved to the newer S/4HANA platform. The AI features being showcased at Sapphire are only accessible to organisations that have made that move, or are on SAP's cloud subscription programmes.
This creates a fork in the road that is arriving faster than many organisations realise. Staying on older SAP systems means staying locked out of the AI capabilities both companies are building. Moving means a migration that typically takes two to three years for large organisations, which means the window to begin planning is already narrow.
Microsoft's push here is not purely altruistic. Azure is competing with Google Cloud and Amazon Web Services for SAP workloads, and the AI partnership with SAP gives Microsoft a specific advantage. The expanded RISE with SAP acceleration programme on Azure, which will more than double the number of supported customers in 2026, is a direct attempt to capture migration decisions before they go to competitors. Companies like Maersk have already moved 500 SAP servers and a petabyte of data to Azure in six months with near-complete uptime, and are now using AI to let teams query invoices and shipment data in plain language.
The honest picture is that the AI being demonstrated at Sapphire is real but not yet widespread. Only around 3 percent of SAP customers are running SAP's own AI tools in production today, while 77 percent of companies actively using AI are doing so with non-SAP tools like Microsoft Copilot. The agent-to-agent capability announced this week is partly an answer to that gap, allowing the Microsoft tools already in use inside these companies to reach into SAP data and workflows without requiring organisations to adopt a separate SAP AI product first.
For any business still on older SAP systems, the AI announcements at Sapphire are both an incentive and a pressure. The capabilities being built are genuinely useful. But accessing them requires a migration decision that most organisations have been postponing.