Speaker 1: You've been in that meeting where someone says BTP and everyone nods along, it shows up on slides and in job ads, and it rarely gets explained in plain words. SAP Business Technology Platform sits under much of what SAP does today, and that's why it feels so vague. So let's take it apart slowly, with real examples and the honest limits. We'll keep the jargon to a minimum and explain the parts that matter. The plain version is simpler than the name suggests. SAP Business Technology Platform is a platform rather than an app you install and switch on. SAP describes it as an offering that brings several kinds of technology together in one place. It's also the technical foundation that many newer SAP products are built on. A useful picture is a large toolbox. You don't buy the whole thing at once, and you certainly don't use every tool in it. You open the platform, pick the services your project needs, and leave the rest alone. That detail explains something confusing. Two people can both say they use BTP and mean different things. One team might only use it to connect systems, another might only use it for reporting, and a third might be building small apps on it. SAP groups the platform into a few broad areas. Application development is about building and extending apps, and process automation is about letting software handle repetitive steps. Integration is about getting systems to talk to each other. Data, analytics, and enterprise planning is about storing numbers and turning them into something a person can read. Artificial intelligence is the newest area of all. Five areas sounds like a lot, and it is, but you almost never touch all five at once. Most people start with one, get comfortable, and then reach for a second. The scale is worth knowing, too. SAP says more than 33,000 customers use this platform. That's part of why the term shows up everywhere, even when the explanation doesn't. It's also the foundation under something called SAP Business Suite, the collection of SAP applications that most companies already run. Underneath all of those services sits something you rarely think about, and it's the place the code actually runs. The platform offers several runtime environments. One runs on Cloud Foundry and another runs on Kubernetes for teams that already work that way. A third is an ABAP environment for developers who build in SAP's own language. That spread matters. because it means you can often build with the skills your team already has instead of learning a new stack first. So the first honest takeaway is this. BTP is not a single thing with a single purpose. It's a collection of services that share one account, one security model, and one place to manage them. That leads straight to the next question, which is why SAP decided to put everything in one place to begin with. Most companies don't run SAP on its own, They run SAP for the core business, Microsoft tools for email and collaboration and reporting, and a handful of other systems for things like warehousing, HR, or billing. Each of those systems was built to do its own job well, and none of them were built to share information with the others by default, so the information gets stuck. A sales order lives in SAP, the report the leadership team wants lives in Microsoft, and somebody ends up copying numbers by hand every Monday morning while everyone pretends that's fine. Multiply that by every team in the company, and you start to see the size of the problem. SAP built this platform to sit in the middle of that mess. Its job is to connect the systems, move the data, and give teams a place to build the small pieces that don't belong in the core. SAP even frames its integration work around whole business journeys, like lead-to-cash, source-to-pay, and hire-to-retire, rather than around individual systems. There's a phrase you'll hear a lot, and it's called clean core integration. It means you keep the standard SAP core untouched and put your custom logic and your connections beside it on the platform rather than reaching into the standard code and changing it. The core stays upgradable and your custom work lives somewhere you're allowed to change. Take a practical example. A finance team wants a custom approval screen plus a report that blends SAP numbers with Microsoft data. Changing the SAP core to deliver that is risky because every upgrade can break your changes. building it beside the core keeps the core stable and puts your custom piece where you can change it freely. That's the promise and it's a good one. It's also where the honesty starts because building beside the core still means somebody has to design, build and run that new piece. The platform gives you a place to put it and it doesn't take away the work. There's a second reason SAP pushes this approach and it's about cost. SAP describes the platform as a way to lower the total cost of running a mixed set of systems because a shared place for integration and extension is cheaper than one of connections built by every team on its own. Let's walk through the five areas one at a time with a plain example for each. Integration comes first because it's the one most people need. SAP Integration Suite is the part that connects SAP to everything else and it comes with a large library of pre-built connections so you're not starting from an empty page. A simple example is a sales order in S flush FANHA that needs to trigger an update in another system, whether that system is SAP or not. Application development and automation comes next. SAP Build is the family of tools here, and it's designed so people who aren't full-time developers can still build something useful. Picture a warehouse team that needs a small app to track damaged goods. Instead of a six-month project, someone on that team can assemble it with low-code tools and connect it to SAP data. Then there's data and analytics. SAP HANA Cloud is the database piece, and there's a data and analytics layer for reporting on top of it, with SAP Business Data Cloud as the newer, fully managed option that pulls SAP data together and connects it with outside data. A common example is pulling SAP numbers into a dashboard so a manager can see what's happening without requesting a custom report every week. Artificial intelligence is where the fastest change is happening right now. There's a set of AI services on the platform and there's Joule, SAP's assistant, that answers questions and helps with tasks. If you want to build your own AI helpers, there's Joule Studio, a tool for creating agents and skills, and it became generally available in June of last year. SAP has also been adding AI to the plumbing itself. In 2025, it announced an AI-assisted experience for building integrations tools that look at your API traffic and predict where it's heading, and an adapter that lets you plug in your own large language models. It added new connectors as well for systems like Snowflake and IBM MQ, which matters if your company already runs those, There's a quieter area you might not notice at first, and it's the shared experience across SAP apps. A common look and feel single sign-on across systems and one inbox for the tasks waiting on you all live here. That's why the platform can feel like it's holding the SAP world together rather than just sitting beside it. That list is long and it keeps growing. Community estimates put the catalog somewhere around 85 to 90 services, which is a useful ballpark rather than an official number, and it changes every year. More services means more choices and choosing wrong has its own cost. There's one more connection that deserves its own section and it's the one you touch most days, which is how all of this meets the Microsoft world. Here's a point that surprises people. This platform and Azure are not competing for the same job and most companies run them side by side. SAP handles the business processes, Microsoft handles the productivity and cloud services around them and this platform is often the bridge between the two. The two companies have worked together for more than 30 years, so this isn't a new arrangement. Identity is usually the first thing to sort out, because nobody wants a second password. Microsoft Entry ID, which used to be called Azure Active Directory, can handle sign-on and the user lifecycle for SAP applications, including this platform. That's one detail worth being precise about, though. Entry ID can handle authentication, the part that proves who the user is. While SAP still decides what that user is allowed to do inside SAP, those are two different jobs and people mix them up all the time. Workflows are the next common connection. Azure Logic Apps has a documented connector for SAP, so a Microsoft workflow can reach into SAP and act on it. Azure API Management can take SAP interfaces and publish them safely with the controls you'd expect for anything exposed beyond your network. If your business users prefer Power Platform, there are documented SAP connectors there too. which lets a team build a small app in the Microsoft tools they already know. Events are where it gets more interesting. SAP Event Mesh can exchange events with Azure Event Grid, which means a business event in SAP. Like an order being released can start something on the Microsoft side automatically instead of waiting for a person to notice. Data is the connection most teams feel first. SAP data can move into Microsoft Fabric and Power BI through documented connectors, so a report can blend SAP numbers with everything else the business tracks. On the security side, Microsoft Sentinel has a documented solution for this platform, so SAP Activity can show up in the same place your security team already watches, and SAP Private Link Service can connect platform apps to Azure privately rather than across the open internet. None of that is magic, and all of it comes with conditions. Each of those connections depends on connectors, licenses, and versions that have to line up. Before you promise a manager that SAP and Microsoft will talk by Friday, check that the specific connector you need is supported in your setup. The connections are real and documented, and they still need a person who understands both sides. Once you can picture the services, the next question is where they physically live, and that's where plenty of early confusion comes from. The structure has three levels and it's worth learning because you'll see it in every setup. At the top is the global account, the contract your company has with SAP. Under that come directories, which are folders for organizing things. And at the bottom are subaccounts, where you actually deploy apps and turn on services. Each subaccount is tied to one region, the physical location where your applications and data are hosted. This is why two subaccounts inside the same company can behave differently because one might sit in Europe, while another sits in the United States. The region attached to a subaccount doesn't have to match where your office is, which is a detail people find surprising the first time they set one up. There's also a money layer on top of the structure. You buy a capacity at the global account called entitlements and quotas, and then you hand it down to the subaccounts that need it. Saying you have the platform doesn't mean you can turn on everything, because somebody has to assign the capacity first, and that assignment is where budgets are won or lost. Directories can nest up to seven levels deep, which sounds like a technical detail until you realize it's a design choice with real consequences. A common pattern is one directory per department, and inside each one separate sub-accounts for development, testing, and production, so a mistake in a test system can't reach the live one. This matters for beginners more than it sounds. If the account model is messy on day one, it's expensive to untangle later, because moving things around affects security, cost tracking, and who can see what. Getting the rough shape right early is one of the cheapest wins available. Let's make this concrete with a few short scenarios you actually run into. The first is extending S-4 and HANA without touching the core. A company needs a custom screen for a process that standard SAP doesn't cover well, so instead of modifying the SAP code, the team builds a small app on the platform that calls SAP through its interfaces. The core stays exactly as SAP shipped it, and the part you have to accept is that you now own that app, including its security and its updates. The second is connecting a system that isn't SAP at all. Say the company uses a third-party tool for warehouse management, and the warehouse team is tired of retyping orders. The integration layer on the platform connects the two with pre-built content to speed it up, and the limit is that integrations break whenever either side changes, so someone needs to keep an eye on them. The third is bringing SAP data into the Microsoft world. A finance manager wants one report that combines SAP figures with data from Microsoft tools so the SAP data flows into Microsoft Fabric through documented connectors and the report gets built there. The trouble is that the data has to be modeled sensibly or you just get a faster way to produce a confusing number. The fourth is smaller but it's spreading fast and it's adding an AI helper to a routine task. A group puts together a small helper that answers questions about a process or drafts a routine response using the platform's AI services. The limit here is the sharpest one, because an AI helper is only as good as the data and the guardrails behind it, and anything that touches a real business decision needs a person in the loop. Notice the pattern in all of them. The platform hands you somewhere to build it, and it doesn't spare you from designing it well, securing it, and keeping it running. A demo on this platform can come together quickly, which is encouraging. A production solution is a different animal with governance, monitoring, and cost control attached to it, and knowing which one you're building saves a fair amount of heartbreak. Now for the part most introductions skip, which is the mistakes that show up again and again, and the limits that come with the platform. The first mistake is treating it like one product you switch on. It's a catalog and you buy the pieces you need, so teams that assume everything is included get a surprise when half the services they planned around aren't in their contract. The second is ignoring cost. The platform has consumption-based pricing, which means some services are billed by what you use, and those numbers can climb quietly if nobody is watching. This is a common complaint in the community, and it's avoidable with a bit of governance from the start, including someone whose job is to look at the bill. The third is modifying the core because it's faster today. That's the exact thing CleanCore exists to prevent, and it's the mistake that hurts most later. when an upgrade arrives and your changes get in the way. The fourth is skipping the account model and discovering the region and entitlement limits too late. Somebody builds a proof of concept in a sub-account in the wrong region and then finds out the data can't simply move. The fifth is forgetting the on-premise side. Many companies still run SAP systems in their own data center and connecting them to the platform needs a small piece called the cloud connector. Teams that plan for a pure cloud setup sometimes discover this late The sixth is assuming that everything called part of the platform will stay part of it forever. The line between this platform, SAP Business Data Cloud, and the newer SAP Business AI platform has moved, and names keep changing. If a design depends on a specific boundary, check it against the current catalog before you commit. Beyond the mistakes, there are honest limits. Licensing is complex, with several models to choose from, including an annual subscription, a consumption agreement, and pay as you go, the platform doesn't remove the need for skills, because someone still has to understand both the business process and the technology, and the free options are restricted, which we'll get to next. None of this makes the platform a bad choice, it makes it a real one, with the same trade-offs as any serious piece of enterprise software. You can explore all of this without spending anything, and there are two main ways to do it. The first is a trial account, which is free for 90 days and open to anyone. It's meant for personal exploration and your own testing, and SAP is clear that it must not be used for production or for team development. The limits are specific and worth knowing up front. You get 4GB of memory for applications, 8GB of instance memory, 10 routes, 40 services, and 2 on-premise systems through the cloud connector. There's also no service level agreement, so don't build anything you depend on. The second option is a free tier on an enterprise account, which lets you explore certain services without the 90-day clock running out. Some services are marked free tier and some are marked always free, which means they're already included in the contract. If you need to explore without a deadline, that's the path to take. When you're ready to look around, SAP Discovery Center has guided missions that walk you through real scenarios, and the SAP Tutorial Navigator has step-by-step starter exercises. The honest limit here is simple, because the trial is for learning, so use it to understand the platform rather than to promise a customer a demo. So here's where we landed. This platform is a bundle of services rather than a single product, and it covers five broad areas, from building apps to adding AI. It sits beside your SAP systems so you can extend them without breaking the core. It connects naturally to the Microsoft tools you already use and it rewards good governance while punishing guesswork. Before we finish, here's a question for you. If your team already uses this platform, which part did you start with and what would you tell someone opening it for the first time? If this made the topic feel less intimidating, subscribe to M365FM. to master the tools and the mindset shaping the future of work.