When I begin a discussion on migration to Azure with an organization, it is a bit different than a greenfield discussion because we have something in our hands. We know the size, shape, and history of the application we are moving. Let’s look at things we should do in this scenario.
We want to start by assessing the applications and infrastructure, and we do this in the following way:
- Discovery, which allows us to peek under the hood of the applications and infrastructure needed to support them. This is not only the code but such things as DNS and services needed to support the application. This is helpful, as not every application is a good candidate to migrate or you may need to secure VPN connect to the internal resources that can’t be moved to Azure.
- This will lead to mapping your applications to discover all dependencies, which to me is the best exercise as every single organization I have consult with discovered something new with this process.
- Once you have...