Operations | Monitoring | ITSM | DevOps | Cloud

When SAP unveiled the Business AI Platform at Sapphire 2026, it folded BTP, Business Data Cloud, and Business AI into a single governed environment. BTP didn’t disappear but became essential architecture underneath SAP’s agentic AI direction. A big part of the repositioning included cloud and AI enablement of existing systems, data and enterprise context: the cloud half of every hybrid SAP estate just got more capable and more strategic, and SAP Cloud Connector plays a central role.

Drift Happens. Six months ago, your SAP landscape passed audit cleanly. Today? You couldn’t say for certain without a manual scramble across Basis, security, and infrastructure teams to reconstruct what’s true right now. You did exactly that for the audit, after all. That gap between “was compliant” and “is compliant” is where most SAP security programs quietly fail.

Since our firm first published the Cloud ERP (then it was “RISE”) F.A.Q., a lot has changed with SAP, the market, and adoption trends. It’s worth a revisit: how Cloud ERP is packaged and sold by SAP has changed significantly, as has our guidance for customers adopting the solution. Perhaps the most notable change is the maturity of the Cloud ERP Private and Public solutions.

If you’ve spent any time in the SAP ecosystem, you know the “Configuration Tax.” It’s that invisible, compounding fee paid in hours, manual effort, and caffeine. SAP teams pay tax every time new systems or integrations are brought under observability and management. For years, the industry accepted that observability required a heavy initial lift.

Most large enterprises elect a hybrid approach to SAP operations, but this is a more recent trend. And, as SAP operations professionals, we are still learning about the impacts of this choice and approach, even though it’s often the most sensible and pragmatic. Years ago, everything ran on-premises.

Migrating to SAP S/4HANA is one of the most consequential system changes your organization will undertake. The technical complexity alone is significant. But the real risk is operational: maintaining uninterrupted service delivery while transforming the core systems your business depends on. Failure to manage this well causes outages, data inconsistencies, user disruption, and cost overruns. None of those are acceptable outcomes. The good news is these risks are manageable.

Automating root cause analysis is often regarded as the holy grail of IT operations. A solution capable of automatically identifying issues, resolutions and even prevention. Performed correctly, automated root cause analysis accelerates MTTI (Mean Time to Identify) and MTTR (Mean Time to Resolution). But for many platforms, this goal remains elusive: complexity, differences between deployments and different architectures make automating root cause challenging.