Reaching The Cloud: The Keys to a Successful Enterprise Migration to Azure

Posted by Gali Kovacs Topics: Azure, Data Migration

Making an Enterprise Cloud migration plan is a process that can be daunting for any IT specialist. 

In the first stages, the personnel that will make up the enterprise migration team should be selected and a full view of the current environment should be assessed.

When it comes to Azure, tools such as the Migration Assessment Tools and ASR Deployment Planner will give users insight into which parts of their workload will benefit from a move to the cloud, allowing them to consider how the migration will impact overall performance and affect costs.

There are six main points to consider when planning your Enterprise Migration to Azure:

  1. The method for migration
  2. Gaining Suport
  3. How to accomplish the move
  4. Storage configuration options
  5. Security solutions
  6. Hybridizing your data center.

1. Enterprise Migration Methods

Analysis has shown that optimal migration to the cloud can be nested under two model types: Infrastructure-as-a-Service (IaaS) and Platform-as-a-Service (PaaS). Each of these two models has two variations:

IaaS (Infrastructure-as-a-Service)


Redeploys your current setup on an IaaS without making changes. Also known as Lift and Shift.


Fits existing coding into the new cloud environment by modifying or extending the code currently in place

The PaaS options are as follows:

PaaS (Platform-as-a-Service)


Existing code is run on top of the cloud


Discards the existing code in favor of re-architecting on top of the cloud


The model a company chooses to use should reflect its business type and goals. 

The PaaS model, for instance, will benefit companies that work primarily online and with software development. This is because Azure PaaS offers services such as Azure App Services, which provide serverless architecture capabilities that allow R&D teams to focus on innovating for the company, rather than maintaining infrastructure.

The fastest method to accomplish migration is the IaaS rehosting, aka “Lift and Shift.” Rehosting uses the infrastructure components of Azure. Other options include a mixed IaaS-PaaS configuration, or completely replacing the service a company offers with a new one based in the cloud.

2. Gaining Support

Microsoft provides out-of-the-box support of hybrid cloud for enterprises. With products such as Windows Azure Stack, for example, Microsoft has enabled enterprises to deploy a true hybrid cloud.

Windows Azure Stack brings Azure Resource Manager, blob storage, and fault domains (among other features) to your on-premises data center, transforming it to a true, scalable private cloud solution.

3. Accomplishing the Move

The objective of the move should result in a lower TCO and improved performance at lower costs. By setting your goals early on, you will be able to take advantage of Azure VM Sizing to make sure these parameters are met.

Azure runs on the proprietary Hyper-V platform from Microsoft, which makes lift-and-shift rehosting procedures onto the cloud’s blob storage from an on-premises Hyper-V environment as simple as transferring a VHD from the old environment to the new one.

Azure also offers Microsoft Virtual Machine Converter and Azure Site Recovery (ASR). The popularity of running Linux on Azure virtual machines has also lead Suse and RedHat to offer their own services in Azure through BYOL or monthly fees.

The Azure Website Migration Assistant tool can help in automated assessment and migration of websites running on IIS.

4. Finding the Appropriate Storage Type

Regardless of whether a migration is based on an IaaS or PaaS model, storage costs will increase over time. To keep rising costs under control, it is crucial to select a storage account type that appropriately meets the application’s performance, read/write operations, and replication requirements.

The right storage service will be determined by the data types in use: both IOPS and throughput will be factors to consider. Make certain you understand the IOPS nuances for different types of storage and test this with tools like IOMeter and SQLIO to simulate workloads.

Pro tips: For some virtual machine tiers, you can use storage spaces to combine the IOPS from several disks. Also, you get temporary SSD storage when creating a VM, which can be utilized for things such as Pagefile or SQL TempDB.

One way to tackle storage in Azure is to use the concept of managed disks, which overcomes a lot of limitations inherent in storage accounts 

Enterprise Migration to AzureMoving cold storage data to the Azure Cool Blob storage format is another way to keep costs down. It is both cost effective and simpler to accomplish than alternatives. Since Cool Blob is meant for infrequent access, it is ideal to use for data archives.

With Azure’s StorSimple solution, for instance, you get to build on your prior expertise of on-premises storage solutions, but with a unified management console for both on-premises and cloud storage workloads.

Another option to maintain compatibility with enterprise-grade products is to use NetApp®Cloud Volumes ONTAP® (formerly ONTAP Cloud), which not only provides the familiar Cloud Volumes ONTAP features on NetApp FAS products, but also automates data movement in the cloud and provides a central console for operational insights and resource cost monitoring. 

Certain virtual machine tiers allow users to combine IOPS from more than one disk by taking advantage of storage space. When creating a virtual machine, users are granted temporary SSD storage that can be used for Pagefile or SQL TempDB. 

Becoming familiar with the use of managed disks will also help deal with storage issues with Azure.

5. Security and Availability Solutions

Public cloud usage comes with a major concern: security. With some loss of data sovereignty and infrastructure control, it is important to make sure to have a strategy for encrypting all at-rest data in place. 

For Windows, Bitlocker Drive Encryption and Azure Key Vault can be an excellent starting point while devising this strategy.

Linux users can supplement Azure Key Vault with DM-Crypt. Another important technology that helps encrypt data at rest is Azure Storage Service Encryption (SSE), which encrypts the data as it is stored in Resource Manager Storage Accounts.

The Azure marketplace also hosts many third-party vendors who offer their own encryption services. A service such as BYOL can offer a low-cost solution to protecting expensive appliances.

Networking resources will not get lost in an infrastructural move to the cloud. Built-in technologies like  network security groups and Azure WAF can control the flow of traffic with the aid of technologies like route tables and User Defined Routes.

These technologies can also be used to setup advanced use cases like forced tunneling.

Azure Virtual network gateway helps setup traditional VPN connections for use cases such as Site-to-Site VPN and Vnet-to-Vnet VPNs . Apart from this, always ensure that you have a holistic view of threat vectors through the Azure Security Center. 

It should go without saying that any security measures that are enacted should stay within RTO and RPO objectives. Depending on your environment and availability requirements, it will be wise to take advantage of tools such as availability sets, ASR and Azure backup, and guest clustering.

All of these features have capabilities that will meet specific backup and data recovery goals. Availability sets use fault domains and update domains to guarantee uptime while performing planned or unplanned maintenance.

ASR and Azure backup are parts of Microsoft’s Operations Management Suite (OMS) which keep data regularly backed up in redundant storage spaces. Guest clustering uses Storage Spaces Direct for high-availability and load-balancing features of VM workloads.

For more on security solutions and Azure resilience, refer to this guide.

6. Deploy and Manage

After spending considerable time on assessment, planning, and testing out your new environment, you are finally ready to move your workload to Azure. Now you need to think about migrating huge amounts of data to the Azure data centers.

Tools such as Azure Storage Explorer and AzCopy can help move data to and from the blob-based Azure storage. Objects such as files and VHD can be easily migrated using these native tools.

What if your data is too big to migrate through these conventional tools?

Consider using import/export, with which you can ship hard drives with the on-premises data to Azure data centers.

In the case of hybrid deployments, use of exclusive networks such as ExpressRoute can significantly reduce transfer time. Azure Site Recovery, already mentioned, is also a good feature to help you move VM-based and physical server workloads to the cloud.

And don’t forget to make use of the SQL Database Migration Tool to move SQL databases from on the premises to the cloud. A tool that can help you in this process is Data Migration Assistant (DMA), which detects compatibility issues and allows you to move data to an Azure SQL database. Existing NetApp users can leverage the familiar SnapMirror® technology to migrate data from on the premises to the Azure cloud.

Similarly, the Azure Website Migration Assistant tool can help in automated assessment and migration of websites running on IIS.