Some of the best features of Azure Stack HCI are that, as we are primarily a Microsoft Windows Server organization using Microsoft Windows Server on most of our servers, we already own data center licenses for Microsoft operating systems. The hypervisor, Azure Stack HCI, actually comes with that license, which allows us to switch from VMware to Azure Stack HCI without any additional cost, significantly reducing our operational costs, especially now that Broadcom has purchased VMware, to $0. This difference is extremely significant for someone who already holds data center licensing for Microsoft. For those familiar with Hyper-V, the learning curve is not so bad as it is very similar. We have utilized the virtual machine support feature in Azure Stack HCI for managing both Windows and Linux workloads, and so far we have been very satisfied. However, we've had some small difficulties in migrating our VMs over from VMware to Azure Stack, as there are some intricacies that can be complex at times. The migration tool, which is still only in beta and has not fully released yet, functions but can be tricky for certain configurations or specific features from VMware. We've encountered issues with configurations such as shared VMDKs that do not convert appropriately, necessitating changes in VMware prior to completing the conversion; otherwise, the VM simply won't convert.
