Forget the stock answer of just click a button to create a service and off you go in the cloud. What about if you have 100's SQL Servers, some legacy applications, running on older versions and no cloud subscription? Then the path is very different.   This session focuses on the key steps you need prior to data migration such as connectivity, identity, target destination, data migration and running in the cloud.   What is the decision point to lift n shift, modernise then shift or go for the art of the possible? Is Azure SQL Managed Instance the right target? What is it? Should it be Azure SQL Azure DB? Should I run SQL Server on Infrastructure as a Service? What's difference? What pathway fits my scenario?   We will take a real world example of how you can take an application, migrate using the Azure Data Migration Service, deep dive into the Azure SQL Managed Instances and then use the built in features to tune, protect and optimise the data tier. Products: Azure Active Directory Networking Azure SQL Managed Instances Azure Data Migration Service   Background: During the past year, I have been working on architecting several projects which involve moving large volume of SQL Servers to the cloud. We’ve hit blockers, we've had success and during the journey learnt that the art of the possible sometimes scares businesses who are looking at the here and now.