Using Azure VMware Solution for Branch Office Migration

Azure provides a migration tool that can help transition from VMware to Azure. You can set up a VM in your current VMware environment that takes snapshots and transfers the data to Azure. When you're ready, it can even shut down the VMware VM and start the Azure version. This tool can give you some cost estimates, but be careful because public clouds charge per VM rather than per node, which can lead to higher costs if you're not fully utilizing those VMs. Additionally, storage costs might not factor in how cloud providers compress data. It’s crucial to analyze your resource usage to avoid unnecessary expenses. Aim to consolidate workloads where possible to maximize efficiency! Good luck!

I’d be cautious about AVS; some say it’s really pricey. Considering directly migrating to standard Azure VMs might save money. Also, think about replacing some of your services with alternatives that don't rely on VMs—lift-and-shift often isn’t the best route for cost efficiency.

Definitely use the Azure migrate tool! It has everything you need to assess your current setup, plan a target architecture, and carry out the migration. Before jumping into migration, focus on cost analysis and overall architecture to understand your specific needs better. The intricacies of VCF and VM payments in the cloud might require a bit of guidance, so it’s worth the effort up front!

There are definitely options with Azure VMware Solution (AVS) or moving directly to Azure native VMs. If you go with AVS, remember it requires a minimum of three nodes, typically on the AV64 SKU (64 vCPUs each). Make sure your VCF license covers the new setup; otherwise, it might cost more than anticipated. For connectivity from your branches to Azure, ExpressRoute or VPN is recommended. The newer AVS SKU runs on native Azure hardware, simplifying connectivity. You also get NSX included for network expansion and HCX for VM migration, so consider looking up demos to see how the process works.