Azure eBook series

15 lessons learned
migrating SAP
to the cloud
© 2018 Microsoft Corporation. All rights reserved.

This document is provided “as is”. Information and views

expressed in this document, including URL and other internet
website references, may change without notice. You bear
the risk of using it. This document does not provide you with
any legal rights to any intellectual property in any Microsoft
product. You may copy and use this document for your internal,
reference purposes.
Contents

Moving SAP to the cloud 4 Make the most of SAP

in the cloud  17
Our path to SAP in the cloud 7
How we optimise SAP in the cloud 19

Take a close look at your

SAP workloads 8 Secure and manage
SAP in the cloud  20
Identify application and server
dependencies 9 Azure security 21

Analyse your configuration 10 SAP security 22

Plan your costs 10 How we secure SAP in the cloud 22

How we assessed our SAP environment 11

Make the most of your
SAP investment 24
Move your SAP to the cloud 12
How we migrated SAP to the cloud 14
Checklist: 15 lessons learned
on moving SAP to the cloud 26
01
Moving SAP
to the cloud
 Chapter 01 Moving SAP to the cloud 5

SAP is the backbone of your business – from

sales to operations and from financials to
supply chain. But even for business-critical

“Moving to the
technology like your SAP implementation,
you expect and even desire change. You’re

cloud will save

adapting to changing business needs
or planning for SAP’s mandatory transition

us money, but
to HANA-only support in 2025, or you’re
looking for ways to lower the costs and

this is really
improve the performance of your SAP
deployment. Whether you’re part of a one

about becoming
million or a one billion dollar business,
managing change with your traditional

more agile and

IT infrastructure is a challenge.

Moving to the cloud can transform

the way your business uses technology
by helping you provision and consume
computing and storage as needed instead
of making expensive upfront investments
to handle infrequent heavy workloads.
It’s a fundamental shift in the way you
invest in your technology infrastructure,
and it offers nearly unlimited flexibility
in design, implementation and cost.
Making your new SAP investments in the
cloud will help you be more efficient, agile
and innovative.
innovative.
This means our teams can stop
worrying about keeping our
infrastructure up and running
and focus on innovating without
a lot of heartburn. They can run
experiments, learn and then use those
learnings to take us in new directions –
and if an experiment doesn’t work,
they can easily shut it down and move
on to something else.”

Mike Taylor
Manager of the Microsoft SAP program in Core
Services Engineering and Operations
 Chapter 01 Moving SAP to the cloud 6

Why SAP on Azure?

Microsoft and SAP have participated in an alliance for more than two decades. That alliance has
been focused on one goal: to provide businesses with a clear roadmap so they can confidently drive
innovation in the cloud. With Azure, Microsoft helps bring unparalleled performance to your entire SAP
estate. Azure enables you to run and deploy popular SAP products and solutions within minutes – on
a secure, scalable and business-proven cloud platform. The joint Microsoft and SAP ecosystem provides
unique insights and rich product integration to help you make the most of running SAP solutions and
applications in the cloud – accelerating your performance, productivity and innovation with seamless
enterprise-class support.

When you migrate your SAP workloads to Microsoft

Azure you get:

Reliable, highly available The ability to bring your own

and scalable SAP-certified SAP licence, reduce capital
infrastructure. expenses and monitor costs
for lower TCO.
Microsoft and SAP partnership
and a shared roadmap. Data analytics that powers
better, faster decisions and
Flexibility to adopt an IaaS
more innovation.
or PaaS strategy.
Freedom to move to HANA
Leading security, global reach
on your terms.
and compliance.

We know that making the shift to the cloud
with important workloads like SAP can
be daunting. Your business runs on SAP.
You can’t afford downtime and you can’t
afford mistakes. So how do you make the
move to the cloud with SAP? You could
make the journey on your own, or you
could follow the path of others who have
successfully made the journey – and learn
from their experience.
Like you, Microsoft is an SAP customer.
We’ve made the journey to SAP in the cloud
ourselves and we’ve also helped other
organisations, large and small, successfully
move their SAP workloads to the cloud.
Along the way, we’ve learned some lessons
and developed some best practices that
apply to businesses of all sizes – lessons
and best practices that can help you in
your migration. We’ve shared those lessons
throughout this eBook – and even collected
them in a handy checklist so they’ll always
be at hand.
Chapter 01 Moving SAP to the cloud 7
Our path to SAP
in the cloud
Cloud migration requires careful planning
and strategy. The key is determining your
priorities for migration and the path to the
cloud that optimises your results.
Like many organisations, Microsoft uses
SAP to run a large portion of its business,
so having a well-planned and executed
migration path was an absolute necessity
for us. You can follow the path we took
to SAP in the cloud. Just follow these steps
and take advantage of the tips we learned
along the way:
Take a close look at your
SAP workloads and plan your
migration.
Move SAP to the cloud,
minimising downtime and
ensuring success.
Make the most of SAP in the
cloud and optimise your SAP
investment.
Continue to secure and
manage SAP in the cloud.
Let’s take a closer look at the work we
did during each step and how the lessons
we learned in the process can help make
your journey to SAP on Azure easier.
02
Take a close
look at your
SAP workloads

The first step in your journey to SAP
on Azure is making sure you have a good
understanding of your existing SAP
application, including the underlying
infrastructure of your application workload,
the dependencies and the IT resources your
application is consuming. This information
will help you develop an effective strategy
for your migration.
For example, like Microsoft, your organisation
likely runs SAP applications across a range of
physical or virtual servers. While your current
management tools might represent these
clearly, to kickstart your migration journey,
you’ll need an assessment mechanism
that can feed data into subsequent steps.
Discovering servers and virtual machines
is usually a straightforward process. It relies
on interaction directly with the endpoint
(using an agent) or the managing hypervisor,
like Microsoft Hyper-V. Ultimately, the goal
of the assess phase is to collect server and
application information, including type,
configuration, usage and applications that
might be running.
Chapter 02 Take a close look at your SAP workloads 9
Identify application and
server dependencies
Once you’ve gathered information about
all the servers and virtual machines
you discovered, it’s time to map any
dependencies or communications among
your SAP application, third-party applications
and the underlying infrastructure. This
is a critical step because it helps you discover
application dependencies, so you can:
Decide what you can retire.
Across all SAP workloads, are there
any workloads that are running on old
hardware that aren’t used often or that are
used by very few people? Are there any
application roles that you can consolidate?
Now is the right time to streamline and
right-size your SAP workloads.
Decide what you can replace.
Look for systems that you can replace
with software as a service (SaaS) offerings.
For example, SAP has SaaS solutions
like Concur, SuccessFactors, Ariba and
others. Microsoft has SaaS products – like
Dynamics CRM Online – that provide
integration into SAP business processes.

Prioritise workloads for migration.
It’s also important to determine migration
risk. Migration risk usually depends on two
factors:
Business impact. How important is the
workload to your business operations?
Complexity. How complex is the
application and how well does your team
understand it?
A critical workload will score a higher risk
even if it’s simple. A more complex, but less
critical workload might end up with a lower
risk score – and so might be a better
candidate for early migration.
Analyse your
configuration
Configuration analysis ensures your
SAP workload will function as expected
on Azure. This process provides insight
into your SAP workloads, the best way
to migrate them and any modifications
you need to make to ensure a successful
migration. At this stage, you need to look
at your SAP configuration and its cloud
compatibility. Can it be migrated with its
current configuration? Or do you need
to provide workarounds or recommend
configuration changes? Does anything
about the solution need to change?
Chapter 02 Take a close look at your SAP workloads 10
Plan your costs
Evaluate the potential cost savings of your
migration. For example, you can use the
Total Cost of Ownership (TCO) Calculator to
calculate your TCO for Azure and compare
it to that of a comparable deployment
that uses your on-premises infrastructure.
On-premises servers and virtual machines
are often over-provisioned, using less than
20% of capacity. If you were to take the
physical configuration of your on-premises
server and map this to an IaaS VM series
type, you would likely find that you were
paying for more performance and scale
than you need.
Based on your assumptions and inputs for
configuration requirements for running
SAP workloads – including compute,
storage, network and database – you can
predict the cost of resources to be used
on the cloud and estimate the cost
savings you can realise by migrating your
workloads to Azure.

How we assessed our
SAP environment
Running SAP in the datacentre presented
several day-to-day challenges for our Core
Services Engineering and Operations (CSEO)
team. On-premises infrastructure costs
were high, and the infrastructure failed
to support peak load and was hampering
digital transformation.
The team looked at the SAP system – which
ran on over 600 servers and virtual machines –
looking for machines that weren’t used
often or that only had a few users. Could
we consolidate functionality into one
app? It was the perfect time to streamline,
right-size and eliminate physical servers
and on-premises virtual machines. As part
of the assessment, the team looked at the
performance and capabilities of physical
servers and virtual machines. We also looked
for systems that they could replace with
a SaaS solution. All these considerations
helped them define the strategy that best
met migration requirements.
Lessons learned
Along the way, the CSEO team learned
some valuable lessons about the
assessment phase of migration:
Chapter 02 Take a close look at your SAP workloads 11
Understand suitability and
migration efforts.
Before performing an IaaS migration, the
team needed to understand the complexity
of the SAP workloads, the underlying
infrastructure, the size of each workload
and related databases (in terms of velocity,
volume and variety) and the requirements
for seasonal elasticity.
Clean out your closet.
Moving to the cloud is an opportunity
to throw out the stuff you’re not using.
When you own that old on-premises server,
it doesn’t matter how much old stuff you
have buried in there. When you’re on the
cloud, the cost of carrying around a lot
of dead weight can add up fast.
Ensure that you don’t overprovision
your virtual machines.
It’s important to make sure that you
provision enough resources so that
you don’t have to keep increasing your
system weekly.
Determine Azure region strategy
before moving.
Azure regions have truly global reach,
so make sure that your resources are hosted
in an Azure region or regions that provide
the best connectivity for your company.
For a closer look see, Building an agile
and trusted SAP environment on
Microsoft Azure.
03
Move your SAP
to the cloud
 Chapter 03 Move your SAP to the cloud 13

Once you’ve completed your discovery and

assessment, it’s time to prepare for the next
step – the actual migration. This is where,
after you‘ve determined your migration
goals and gathered all requirements
and constraints, you can choose the best
approach to meet your ultimate business
requirements.

When migrating SAP to the cloud,

you’ll take one or more of these approaches:

Re-host Rebuild
‘Lift and shift’ your Rebuild your solution using
current solutions to VMs cloud-native technologies to
in the cloud. get the most from the cloud.

Refactor Replace
Make minimal changes Replace portions of your
to your solution so it works current solution with SaaS.
in the cloud.

Re-architect
Change how your
solution works to
optimise it for the cloud.
 Chapter 03 Move your SAP to the cloud 14

For example, you might lift and shift your

SAP database – using SQL Server Always
On or SAP HANA System Replication
to seamlessly replicate your on-premises
data to the cloud – while you refactor the
application tier of your SAP workloads
so they connect to data in the cloud.
And you might decide that a SaaS
As you choose
solution like SAP Concur makes sense
for expense management.
your strategy,
we recommend
How we migrated
SAP to the cloud that you migrate
Along with planning which aspects of our SAP
environment to rehost, refactor, rearchitect,
lower-risk SAP
rebuild or replace, the CSEO team also
looked at the migration from a standpoint
solutions before
of horizontal and vertical workloads. The
horizontal set of workloads was a complete
more critical
sandbox environment that cut across all
workloads, so the team gained experience
ones.
across the SAP environment. The vertical
workload was a low-risk system, but it
included sandbox, development, test and
production environments, so we gained
experience in real-world use. We were already
using server virtualisation in our on-premises
datacentres, so the team took advantage
of the virtualised state of the infrastructure to
create a new virtualised environment in Azure
with minimal changes to the server operating
system (OS) and OS-level configuration.
We also made only small changes to the
configuration of SAP applications.
 Chapter 03 Move your SAP to the cloud 15

The team used a lift-and-shift (rehost) processes. It was also a great way to spot
strategy to take servers from the any issues in production early on.
on-premises environment and
As a result of the migration, the team
re-create them as Azure VMs that
realised that developers need help as they
had roughly the same available resources
refactor, rearchitect and rebuild their apps
and configurations. Because we run
to integrate SAP with Azure services. This
multiple sandbox, test, development and
is why we created the SAP ABAP SDK for
production environments, the team used
Azure, which simplifies SAP integration,
the horizontal strategy on the sandbox
and the SAP Web Services Platform for
environment as a series of test cases
Azure, which enables partner applications
or mini pilot migrations. It was perfect
to integrate with SAP in a consistent and
for initial experimentation. We used the
efficient way.
vertical strategy to adjust their internal

Enterprise Global trade Supply chain Business Object event

resource planning services management intelligence repository

On-prem On-prem On-prem On-prem

Production Azure
physical virtual virtual virtual

On-prem On-prem On-prem On-prem

Test Azure
physical virtual virtual virtual

Dev Azure Azure Azure Azure Azure

Sandbox Azure Azure Azure Azure Azure

Simplified view of the Microsoft SAP landscape


Lessons learned
Migrating our SAP infrastructure helped
us to learn a few things:
Consider moving low-risk systems
to the cloud with the vertical strategy
right away.
When we started, we planned to use the
horizontal strategy and then the vertical
strategy. But because one of our end-to-end
systems was low risk, we used it as a test case
for the vertical strategy to get experience
with a production environment in Azure.
Consider building new systems
in the cloud from the start.
When we built a new system, we weren’t
sure whether to put it on-premises and
then move it or to build it in Azure from
the get-go. It was low business impact,
so we built it in Azure. We saved money
and learned about cluster set-ups and
production environments in Azure.
Chapter 03 Move your SAP to the cloud 16
Understand migration strategies and
how they can be best applied to your
environment.
Understanding what to move and when to
move it is a big part of moving SAP to Azure.
The horizontal and vertical strategies
discussed in the first resource provided
below give you practical, business-friendly
guidance on migration strategies.
Predict known business events.
Don’t move systems when they’re highly
critical. We schedule around events like
product releases, quarterly financial
reporting and big projects that go live
in the production environment.
For a closer look, see Strategies for
migrating SAP systems to Microsoft Azure
and Streamlining business processes with
SAP connectors and Azure services.
04
Make the
most of SAP
in the cloud

Once you’ve made the move to the cloud,
you’ll want to optimise your SAP cloud
environment to gain business and cost
efficiencies.
You’d typically size on-premises servers
and storage infrastructure for the next
three to five years, based on the expected
maximum use and workload during the
lifespan of the asset. But often the full
capacity of the hardware isn’t used outside
of peak periods – or isn’t needed at all.
Maintaining these on-premises systems
is costly.
The cloud gives you more flexibility. For
example, the optimisation capabilities of
Azure empower you to combat infrastructure
underutilisation and overprovisioning. This
makes it possible for you to quickly and
easily scale your SAP systems up or down
for current and short-term needs, not for
maximum load over the next three to five
years. This also enables you to optimise
continuously. As your needs change, you can
reoptimise your environment based on your
current needs – not yesterday’s.
Here are some other examples of cloud
optimisation capabilities you can use
to keep your SAP cloud environment
optimised:
Cost Management to decrease cost and
increase agility.
You can use capacity management tools
like Azure Cost Management to help you
Chapter 04 Make the most of SAP in the cloud 18
size your SAP workloads in Azure, so you
pay only for what you need, when you need
it. This reduces the total cost of ownership
of unused hardware and ongoing server
maintenance and gives you the agility
to size your SAP workloads for now and
easily change your set-up as needed
to handle future requirements.
High availability and scalability.
For scalability and high availability of the
SAP application layer, you can deploy and
assign multiple SAP app instances to SAP
redundancy features like logon groups and
batch server groups. You can configure
these app instances on different virtual
machines in Azure for high availability. SAP
automatically dispatches the workload
to multiple instances per the group
definitions. If an instance isn’t available,
business processes can still run via other
SAP app instances that are part of the
same group.
Rolling maintenance.
The scale-out logic of SAP app instances
can be used for rolling maintenance. You
can remove one virtual machine (and any
SAP instances running on it) from the SAP
system for maintenance activities without
affecting production. After you finish your
work, you can add the virtual machine
back, and the SAP system automatically
uses the instance again.

How we optimise
SAP in the cloud
Like you, we want our SAP environment
to be agile, efficient and able to grow
and change with our business. This
requires monitoring the environment and
optimising it to:
Increase cost savings by using our Azure
infrastructure more efficiently.
Create a more agile, scalable and
flexible SAP on Azure solution.
By optimising SAP on Azure, the CSEO team
positioned our SAP environment to grow
and change with our business needs. It’s
now leading our digital transformation and
empowering everyone in our organisation
to achieve more. Put simply – Azure makes
our SAP solution better.
Lessons learned
In the process of optimising our SAP
environment on Azure, we learned
several lessons:
Monitor technology advances.
Azure technology and available virtual
machine sizes and features always advance.
Keep up-to-date with new capabilities
and use them to achieve the best possible
benefits for your business.
Chapter 04 Make the most of SAP in the cloud 19
Consider optimising your SAP
environment before and after
moving to Azure.
You can optimise your environment
before migrating by ensuring that retired
systems aren’t migrated, that your SAP
infrastructure inventory is accurate and that
your disaster recovery plan is tested and
in place. You don’t want to waste migration
time on systems or data that you don’t
need.
Design for high availability in your
production systems with Windows Server
Failover Clustering, SQL Server Always
On and SAP features like logon groups,
remote function call groups and batch
server groups.
Snooze so you don’t lose.
Slash your costs by taking advantage of one
of the cloud’s best benefits: snooze your
usage of Azure when your teams are out
of the office on nights and weekends.
For a closer look, see Optimising SAP
for Azure.
05
Secure and
manage SAP
in the cloud
 Chapter 05 Secure and manage SAP in the cloud 21

Given the increasing number of threats

to your cyber infrastructure, your solution
is only as good as your ability to secure and
manage it. At Microsoft, we wanted to get
visibility into and control over how SAP
in the cloud is used and the security of SAP.
Avoiding business disruptions, meeting Azure security
compliance goals and protecting our own Data security and encryption.
data and customer data were all important.
Use built-in industry-leading controls
We use Azure services in combination
and capabilities to enable data security
with SAP capabilities to provide integrated
and encryption.
cloud security and compliance for our
SAP workloads and their underlying Security monitoring and
infrastructure and data while supporting threat detection.
more complex configurations and more Use the Azure logging and monitoring
user-accessible SAP solutions. capabilities and artificial intelligence for
real-time visibility, threat detection and
event analysis.

Single sign-on.
Seamlessly access all SAP applications with
a single credential by using Azure Active
Directory single sign-on integration.

SAP security
Native malware protection.
Take advantage of the native malware
protection, OS-level controls, OS
hardening and patch management built
into your chosen operating system.
Role-based user access.
Use HANA’s role-based access
architecture to deploy privileges to your
user base, restrict actions that specific
users can perform in the HANA database
and restrict data that specific users can
view through reports.
Access anywhere.
Enable user access via web or mobile
devices – ensuring users can perform only
the activities for which they’re authorised –
by using the Fiori Gateway user interface.
For compliance, we already knew that
Azure is an industry leader in compliance,
providing more certifications than any
other cloud provider. This meant we could
focus on internal business processes
to complete our compliance solution.
Chapter 05 Secure and manage SAP in the cloud 22
How we secure SAP
in the cloud
Like other SAP users, we need to make
sure that our SAP infrastructure and data
are secure. So we developed a strategy
to protect SAP assets and data with Azure
security solutions and SAP tools. The
strategy is to make our Azure and SAP
infrastructure secure by design by using
integrated systems, tight controls and
effective monitoring that enables us to
mitigate current and emerging security risks.
We focus on protecting Microsoft assets
and data in a high-profile environment
while streamlining compliance with existing
regulations like Sarbanes-Oxley (SOX) and
newer ones like the General Data Protection
Regulation (GDPR).
Our S/4HANA security redesign initiative
incorporates the robust Microsoft enterprise
security framework and principles that
we have developed over time. It takes
advantage of the Azure-specific security
framework that has positioned Azure as
a cloud services leader and it incorporates
the security tools and technology that SAP
and its partners have developed.
 Chapter 05 Secure and manage SAP in the cloud 23

Lessons learned Our move to

As we secured our SAP infrastructure, we S/4HANA continues
learned a few lessons: Our move to S/4HANA is a long-term
Always keep security in mind. project, as it would be for any business.
As our journey continues, we’ll integrate
Protecting business data is a top priority
industry best practices into every facet
at Microsoft. When migrating SAP workloads
of the security infrastructure that we build
to Azure, we needed to consider all the
for S/4HANA on Azure. This allows us
compliance and data security aspects
to be agile and efficient and to provide
of hosting data in the public cloud.
scalability in our SAP environment – for
Balance security needs with the ability ourselves and for you, our customers.
to troubleshoot.
In Azure, we don’t open all ports on the
cluster installation. We open only the
ones that are really needed. We want the
environment to be somewhat open to help
with troubleshooting, but we don’t want
it to be too open.

Capture all application and data legal

requirements during planning.
Because complying with legal
requirements for data safety and security
can be complicated, we needed to work
with the stakeholders and data owners for
each application to capture all corporate
and legal compliance needs. Plan for this
up front.

For a closer look, see Protecting SAP

S/4HANA data on Azure at Microsoft.
06
Make the most
of your SAP
investment
 Chapter 06 Make the most of your SAP investment 25

Learning and
Electronic
Shared SAP Succession
HR Recruiting
System ECC Success
EREC
Factors

Shared SAP Governance, Global Business Master Data

Planning and Duet for CIM Customer
Finance System Risk and Trade Governance
Consolidation DUET Finance Mgmt
RMCA Control GRC Screening MDG
BPC CFM
GTS

Integrated Sourcing and

Supply Chain Business Dir. Network
SCM Mgmt SCM Planning IBP Ariba

OEM
Services
Commerce Services
Billing CC
OER

Customer Expense
Enterprise Project Mgmt Mgmt
Services CPM Concur

Adobe
Solution Business
SAP Document
Manager Objects
Platform Services
SOLMAN BOBJ/DS
ADS

Azure SAP SaaS

SAP use at Microsoft

At Microsoft, we’re running 100% of our

Next Steps
SAP applications on Azure. While our initial
Learn more about SAP on Azure
migration is complete, the CSEO team’s
optimisation efforts are ongoing as we Try Azure for free
continue to lower our operating costs
and improve our efficiency. We’re also
on guard for security threats and new ways
to prevent attacks. And, as we noted earlier,
we’re now in the process of moving the
company to S/4HANA.

With virtual machines sized to handle even

a Microsoft-sized SAP ERP system, Azure
can handle the smallest to the largest SAP
deployment – so no matter the size of your
business, Azure will help you make the most
of your SAP investment.
Checklist:
15 lessons
learned on
moving SAP
to the cloud
 Checklist 15 lessons learned on moving SAP to the 27
cloud
Tips for assessing your SAP environment

 1. Understand suitability and migration efforts.

Before performing an IaaS migration, a best practice is to assess the complexity of your SAP
workloads, the underlying infrastructure, the size of each workload and related databases
(in terms of velocity, volume and variety) and the requirements for seasonal elasticity.

 2. Clean out your closet.

Moving to the cloud is an opportunity to throw out the stuff you’re not using. When you owned
that old on-premises server, it didn’t matter how much old stuff you had buried in there. When
you’re on the cloud, the cost of carrying around a lot of dead weight can add up fast.

 3. Ensure that you don’t overprovision your virtual machines.

It’s important to make sure that you provision enough resources so that you don’t have
to keep increasing your system weekly.

 4. Determine an Azure region strategy before moving.

Azure regions have truly global reach, so make sure that your resources are hosted in an Azure
region or regions that provide the best connectivity for your company.

Tips for migrating SAP to the cloud

 5. Consider moving low-risk systems to Azure with the vertical strategy right away.
In evaluating when to use a vertical strategy, keep in mind that a low-risk end-to-end system
might be a good candidate for testing this strategy and gaining experience with a production
environment in Azure.

 6. Consider building new systems in Azure from the start.

When building new systems, consider building low-business impact systems in Azure.
This might save you money and help you learn about production environments in Azure.

 7. Understand migration strategies and how they can be best applied

to your environment.
Understanding what to move and when to move it is a big part of moving SAP to Azure.
The horizontal and vertical strategies discussed in Strategies for migrating SAP systems
to Microsoft Azure provide practical, business-friendly guidance.

 8. Predict known business events.

Don’t move systems when they’re highly critical. Consider scheduling around events like product
releases, quarterly financial reporting and big projects that go live in the production environment.
 Checklist Lessons learned on moving SAP to the 28
cloud

Tips for optimising SAP in the cloud

 9. Monitor technology advances.

Azure technology and available virtual machine sizes and features always advance. Keep
up-to-date with new capabilities and use them to achieve the best possible benefits for
your business.

 10. Consider optimising your SAP environment before and after moving to Azure.
You can optimise your environment before migrating by ensuring that retired systems aren’t
migrated, that your SAP infrastructure inventory is accurate and that your disaster recovery
plan is tested and in place. You don’t want to waste migration time on systems or data that
you don’t need.

 11. Design for high availability in your production systems with Windows Server Failover
Clustering, SQL Server Always On and SAP features like logon groups, remote function call
groups and batch server groups.

 12. Snooze so you don’t lose. Slash your costs by taking advantage of one of the cloud’s
best benefits: snooze your usage of Azure when your teams are out of the office on nights
and weekends.

Tips for securing and managing SAP in the cloud

 13. Always keep security in mind.

Protecting business data is a top priority. When migrating SAP workloads to Azure,
consider all the compliance and data security aspects of hosting data in the public cloud.

 14. Balance security needs with the ability to troubleshoot.

In a cluster installation, consider how you balance security with the ability to troubleshoot. A
best practice is to open only the ports that are really needed. You might want the environment
to be somewhat open to help with troubleshooting, but you don’t want it to be too open.

 15. Capture all application and data legal requirements during planning.
Because complying with legal requirements for data safety and security can be complicated,
it’s a good idea to work with the stakeholders and data owners for each application to capture
all corporate and legal compliance needs. Plan for this up front.
 Checklist Lessons learned on moving SAP to the 29
cloud

Next Steps
Learn more about SAP on Azure

Try Azure for free

Contact us