You (or your customer) have finally decided to adopt Azure as a public cloud provider, and for some reason, you have to migrate your SQL Server workloads quickly. You've heard about lift & shift migrations, but you're not sure if this approach is the right one for you.
Do you need a quick and dirty migration to IaaS VMs, or should you spend some more effort to embrace PaaS services? Should you move all the databases to the same target instance, or should you use a different approach for each one? What about networking, security, and costs?
Let's talk about all these drivers, which usually lead us during our migration journey, with a particular focus on the assessment phase that, in my experience, may transform a trivial rehosting into a database modernization project.