SAP on Azure | Workloads

How can SAP Workloads be brought to Microsoft Azure?

For companies with SAP and any non-sap systems, there are various options for completing the road to Cloud. Below is a schematic representation of the various options:

[caption id="attachment_216899" align="aligncenter" width="900"] SAP on Azure migration options[/caption]

Re-Architect your (future) SAP landscape

Important aspect in the elaboration of these choices are:

• What is the scope of the required functionality of both applications and integrations?
• When should this functionality be used?
• At which locations is this functionality required?
• Can the standard Best Practices be used or is customization required?
• What influence does the organization want to have with regard to release / innovation cycles?
• What are the compliance rules with regard to the required IT and application landscape?
• To what extent is Public or Private Cloud an option?

As a solution, a combination of IaaS, PaaS or even SaaS can be chosen in which complete components are fully transferred to the Cloud.

What does your SAP environment look like today?

This concerns the different "layers" of the Enterprise Application structure:

• Which systems and integrations are in use?
• Which applications can actually be stopped?
• Which applications can be replaced by SaaS solutions?
• What is the business impact for the business when things are migrated to the Cloud?
  The plan can then be implemented in various steps to quickly benefit from Cloud and the "As a Service".
  
  A - Lift and Shift in the Cloud
  
  Hereby the entire landscape with regard to the Test and Development environment is actually supported via the Virtual Machines in the Cloud. This Infrastructure as a Service ensures that the application landscape remains the same, but care and management - plus flexibility - is taken care of. This Brownfield migration provides immediate benefits with regard to the Infrastructure as a Service.
  
  B - Lift and Migrate in Cloud
  
  A so-called "vertical" environment consisting of production, development and testing is brought to the Cloud. Thanks to this Brownfield migration, IaaS and database licenses also provide immediate benefits. A logical follow-up to this step is to then migrate the database to SAP HANA.
  
  C - Lift & Shift / Migrate in the cloud, partly migration to HANA
  
  This Brownfield migration immediately benefits IaaS and the use of SAP HANA as the underlying database, which is cheaper than the regular databases.
  
  D - Transformation to S/4HANA and Cloud: Consolidation or (partly) reimplementation or "Greenfield"
  
  This Greenfield migration ensures that immediate benefits can be gained from the Infrastructure, the Platform and the Business. With the use of S/4HANA standard best practice scenarios become available. With the deployment of the SAP Cloud Platform, complexity with regard to integrations is avoided.
  
  A saving of 40% to 70% can be achieved for the deployment of Development, Test and Training systems; In the field of Disaster Recovery, days / weeks are changed to minutes; By using cheaper mediums, the saving of costs for making backups and archiving can go up to 60%; Deployment of Microsoft VM can be up to 40% cheaper within Azure compared to other Cloud VM providers; With the use of Azure, the up-time can be increased to 99.9% up