MicrosoftHi Karl-WE
I need clarity on the following comment that you made on Mar 04 2024 01:12 PM:
>> There are only limited scenarios where Azure Stack HCI wouldn't be a good path to transition to for both VMware and existing Hyper-V customers, but that's just my fav.
I find the Azure Stack HCI to be limiting for Enterprise Virtualization. The number of nodes per cluster is limited to 16 as compared to 64 in Hyper-V with Windows Server. Hyper-V supports SAN storage and Azure Stack HCI does not.
The other major limitation is that there is no easy way to capacity balance the Az Stack HCI clusters while provisioning from Azure Portal. You have to do that manually. What I mean here is that if you have 2 Az Stack Clusters with the same characteristics, it will show as 2 separate clusters and the target deployment cluster must be manually selected.
This means the administrator must capacity balance these multiple clusters which is tedious and unnecessary.
Please correct me if I am missing something here.
Regards, Sunil
