By Vaidya Aiyer, VP of Enterprise AI · Published September 1, 2026
Previously in this series: The Copilot You Already Have →
Continue reading: Six Days Out: The Full Case for Copilot for SAP (Part 4) →
Two weeks from today, we're showing this live. Before that, I want to make the case concrete, because "connect Copilot to SAP" means nothing until you see the actual questions it answers, and understand just how little has to change to make it work.
Here's something I don't think gets said enough. Your company already has Microsoft 365. Nearly everyone in the building is already living in Teams, Outlook, Word, and Excel every single day. That's not a new rollout. That's just Tuesday.
What most people don't realize is that Copilot isn't a separate app sitting off to the side. It's built into all of it. You can ask a question from inside Teams, in the middle of a chat with your team. You can ask from Outlook, while you're reading an email. You can ask from Word, while you're drafting a document. You can ask from Excel, while you're building a model. Wherever you already are, Copilot is already there too.
Most business users have had Copilot available to them for a while now and have mostly used it for the obvious stuff — drafting emails, summarizing documents, cleaning up a spreadsheet. What they haven't done is ask it a question about SAP. Not because it wouldn't be useful. Because it couldn't reach SAP data. Until now, that connection just didn't exist.
Here's a real situation I keep running into. In most companies, only a portion of employees actually work inside SAP day to day — that's simply the nature of the role. Finance, procurement, and operations teams typically need it. Plenty of other business users don't. But nearly everyone across the company uses Microsoft 365.
That's exactly why this is the lowest hanging fruit I've seen in a long time. You're not asking IT to roll out SAP access to people who've never needed it as part of their job. You're not buying new software or introducing a new app nobody's used before. You're taking a tool that's already sitting on every desktop, inside an interface everyone already opens forty times a day, and pointing it at data it simply couldn't reach before. The infrastructure is already fully deployed. It has been for years. All that changes is what people can now ask it.
Finance: "Show me all open POs over 90 days for this vendor." "What's our AP aging by region this month?"
Sales and Distribution: "Which customers have open orders past their requested delivery date?" "What's our order backlog by product line?"
Materials Management: "What's our current stock for this material across all plants?" "Which POs are still awaiting goods receipt?"
Production Planning: "What's our capacity utilization this week?" "Which work orders are behind schedule?"
None of these are hypothetical. They're pulled from the actual playbook we're giving away to every registrant — 100+ of them, across FI, SD, MM, PP, and more, on ECC or S/4HANA. And every one of them can be asked from wherever the person already is — Teams, Outlook, Word, Excel — without ever opening a separate tool.
Every one of these questions used to be a ticket. Someone waits. A stretched IT team eventually gets to it, if it doesn't get deprioritized first. Multiply this by however many of these questions get asked in a given week across your business, and you start to see the actual size of what's sitting in that queue.
Now imagine all of it answered directly, in plain English, from inside the tool someone's already using, the moment they ask.
September 15. Two weeks out. Full session, live demo, real SAP data, plain-English questions asked directly from Microsoft 365, across every module above. Every registrant gets the complete 100+ use case playbook, free, whether or not you can make the live session.