* Identify and Know the Environment Where You Will Migrate Azure

• Start with server and application inventory list.
• Azure has a very large support network, but it is good to ensure that the operating system version and configuration of your virtual servers are supported by Azure. For example, features such as Network Load Balancing, SNMP Service, Multipath I/O or the CentOS 6.2 version do not have Azure support.
• Determine your application dependencies and create your migration groups and post-migration actions according to dependencies. For example, your portal application may be using your file server as its data source, or there may be records in the host file of your portal application that will need to be changed post migration.
• Determine Your Service Model: you may want to convert your virtual servers where your database and applications are running to cost effective platform services instead of migrating them as they are (with the "lift and shift" method). With Data Migration Assistant and App Service Migration Assistant, you can check the suitability of your existing application / database for PaaS migration. ( https://appmigration.microsoft.com/ & https://www.microsoft.com/en-us/download/details.aspx?id=53595 )
• Scale and Determine Your Costs: determine the server configuration based on the CPU, ram, disk I/O information required on the Azure environment. For this, it is better to perform your analysis on the current environment in longer time intervals such as 1 month instead of short time intervals of 5 to 10 minutes. You can calculate your Azure costs according to the required server configuration.

You can use Microsoft Migrate Server Assessment tool or third-party tools like Cloudamize, Movere for all these items.

* Review the Network Band Width

You may need more network bandwidth, as traffic previously running over high speed and low latency LAN will pass over the WAN.

* Plan Your Identity Management

For Azure virtual servers in your domain, you will position at least one domain controller server in the Azure environment and perform sites & services configuration but consider the use of Azure AD for your applications in the PaaS model. You can expand your onPrem AD environment to Azure AD with an Azure AD Connect server that you will install in the OnPrem environment, and use solutions such as MFA, Privileged Identity Management, and SSO.

Use Tagging

You can facilitate both the financial and system management of your Azure resources with a tagging strategy that you can determine. For example, you can specify tags such as development – test, critic - noncritic or the name of your workloads (such as SAP).

* Determine Your Post - Migration Monitoring Methods

You can proactively monitor your Azure environment and solve security and performance problems by using native Azure solutions such as Azure Monitor, Azure Log Analytics, Azure Application Insights,