Microsoft’s internal IT organization completed one of the most visible and complex SAP migrations in the enterprise world: transitioning its entire SAP operations, including finance, human resources, and supply chain systems, to Microsoft Azure. This move, which Microsoft revisited in a recent blog post, offers key insights for SAP customers evaluating or executing cloud migrations. It also provides a real-world case study of what’s required to optimize SAP workloads for cloud environments.

Inside Microsoft’s SAP Cloud Migration

Looking back on Microsoft's SAP cloud migration, the company had been considering the move as early as 2013. However, it wasn’t until 2017 that Azure introduced virtual machine SKUs large enough to support Microsoft’s extensive SAP ERP landscape, according to Hans Reutter, Microsoft Digital engineering manager and leader of the migration effort. “It wasn’t just the size, it was the complexity,” Reutter explains. He points to the challenge of coordinating multiple enterprise-scale purchasing processes that had to converge seamlessly at the point of sale to ensure a smooth customer experience. “All of these production landscapes were highly dependent on each other because of the traffic that flows back and forth between them.” According to Microsoft, the move resulted in increased system performance and agility, particularly in the ability to scale environments dynamically to meet seasonal or functional demand. Just as important, the migration aligned internal IT operations with the same Azure-based architecture offered to customers, allowing Microsoft to dogfood and refine Azure SAP capabilities.

Optimizing SAP for Azure

According to another blog post from Microsoft, the migration of SAP to Azure was only the beginning. By managing capacity and sizing SAP systems on Microsoft Azure, Microsoft could realize improvements across cost, flexibility, and performance. Microsoft reported a lower total cost of ownership, as it only pays for the resources needed at any given time, thereby eliminating expenses tied to unused hardware and ongoing server maintenance. One of the most significant efficiencies came from reducing core counts — moving from 64-core physical machines to 32-core virtual machines for nearly every server migrated. This new level of agility also enabled Microsoft to adjust its SAP infrastructure on demand. In one instance, the team scaled a virtual machine from 8 CPUs to 16, doubled its memory, and added Azure premium storage within minutes to meet short-term requirements. Once the need had passed, they easily reverted to the original setup, demonstrating how the cloud environment supports rapid reconfiguration while maintaining cost efficiency.

What This Means for SAPinsiders

SAP on the public cloud has matured into a proven model for enterprise ERP. Microsoft’s journey validates Azure as a scalable, secure, and cost-effective platform for running large-scale SAP workloads. With SAP ending mainstream maintenance for ECC in 2027 and most enterprises facing modernization mandates, hyperscaler-based SAP deployments are becoming a widespread path forward, especially for firms already invested in Microsoft technologies. Optimizing for the cloud is just as crucial as migrating. SAPinsiders evaluating cloud moves should plan for post-migration enhancements early in the process. Key best practices include integrating native observability tools (e.g., Azure Monitor for SAP), using infrastructure-as-code (IaC) for SAP landscape deployments, and continuously optimizing compute and storage configurations. Microsoft’s success demonstrates that automation, telemetry, and elasticity are critical to unlocking cloud ROI. Cloud migrations can utilize a phased approach for managing risk during a complex SAP migration. For CIOs considering a shift to Azure, Microsoft’s phased approach offers a practical roadmap for managing risk during a complex SAP migration. As Hans Reutter explains, the team took both a horizontal and vertical view, starting with the least critical systems, such as sandboxes, to build confidence and validate their strategy. By layering the migration from low-risk to high-risk systems, they could catch issues early without impacting critical operations. It’s a model that emphasizes control, learning, and risk mitigation — key priorities for IT leaders managing large-scale ERP transformations.