Category Archives: Migration to Azure

Microsoft Azure has achieved many certificates and attestations concerning the platform’s regulatory compliance. A specific example relevant to the discussion of operational security, is the ISO/IEC 27001:2013 Information Security Management Standards certification. This standard was created and is maintained by … Continue reading →

In planning for and Azure migration you will also want to give due consideration to the role of the Azure virtual network. An Azure virtual network is a representation of your own network in the cloud. The organization that provisions … Continue reading →

In planning for migration, there are some components that are common for all deployments. Two such obvious components you need to consider are storage and networking. Any IaaS Deployment in Azure will make use of Azure Storage, so let’s cover … Continue reading →

All workload dependencies on one or more databases will need to be mapped out as a part of the planning effort. Performance will be considered in the next section, so in this section, determine the database engine product in use … Continue reading →

Here we need to understand what the source hardware specifics are, as well as the minimum, maximum, and average (Min/Max/Avg) capacity levels for each aspect of the workload. Start by recording the CPU information (number of cores and clock speed) … Continue reading →

This section pertains to the type of storage required, quantity of storage and redundancy needed. The amount of storage the targeted workload uses, plus any amount it is expected to grow over time, should be documented. Also, data that is … Continue reading →

Microsoft has validated many workloads with Azure Site Recovery. If a workload is not listed in this table, it does not mean the workload cannot be protected/migrated. It simply means that the workload has not been validated. Workload Replicate Hyper-V … Continue reading →

An application that is targeted for migration into Azure must have all dependencies fully mapped out. It is a best practice to move dependencies along with the application that requires it, but this is not always possible. If it is … Continue reading →

This consideration has to do with whether the workload to be migrated depends on clustering or load-balancing services. Shared-disk clusters are not supported in Azure and so these must be excluded until they are rearchitected. Clusters that use application-layer data … Continue reading →

Some applications are intolerant of network latency, and migrating these to a hosting location that is further away from end users or application dependencies may introduce errors. Alternately, increased latency may produce frustration with users of the application. Record the … Continue reading →