Amy great blog and AVS is a great solution but knowing your routing requirements is key. There are many many many considerations and limitations depending on how you wish to inspect inbound, outbound and internal AVS traffic. Having done a couple of AVS implementations I've found this to be the biggest hurdle. The official documentation around this is difficult to find and in some cases incomplete, this is a good starting point but it needs work - https://github.com/Azure/AzureCAT-AVS/tree/main/networking. If you're wanting to use 3rd Party NVA's ensure you do your planning and understand what you need to have in place and what you can and cannot do. Your existing environment and VM's have to meet strict requirements for vMotion migrations too, its not as simple as just deploying an HCX appliance and away you go. Deploying an AVS cluster is child's play as you say, integrating with your wider ecosystem is not quite as clear cut.