{"id":513,"date":"2026-09-05T01:11:49","date_gmt":"2026-09-04T23:11:49","guid":{"rendered":"https:\/\/nutanix.ma\/index.php\/2026\/09\/05\/nutanix-nc2-on-azure-explained\/"},"modified":"2026-09-05T01:15:48","modified_gmt":"2026-09-04T23:15:48","slug":"nutanix-nc2-on-azure-explained","status":"publish","type":"post","link":"https:\/\/nutanix.ma\/index.php\/2026\/09\/05\/nutanix-nc2-on-azure-explained\/","title":{"rendered":"Nutanix NC2 Cloud on Azure Explained"},"content":{"rendered":"

Nutanix Cloud Clusters (NC2) on Azure comes up in almost every hybrid-cloud conversation I have now, and most of the time the person asking has a slightly wrong picture of it \u2014 either as “Nutanix hosting” or as “a VM service in Azure.” It’s neither. This is a plain explanation of what it actually is, what you’re responsible for when you run it, and the situations where it’s the right call. Nutanix’s own product page is here: Nutanix Cloud Clusters (NC2) on Azure<\/a>.<\/p>\n

What it is, precisely<\/h2>\n

NC2 runs the standard Nutanix stack \u2014 AOS, AHV and Prism \u2014 on Azure Bare Metal Infrastructure, inside your own Azure subscription and your own VNet. It is the same software you run in your data centre, on hardware Microsoft owns and you rent by the node. Nutanix’s own line on this is the right one: NC2 is different because it’s the same<\/em>. Same data plane, same management plane, same Prism Central console covering on-premises and Azure together.<\/p>\n

That has a practical consequence people underestimate: there is no new platform to learn, no application refactoring, and \u2014 because Nutanix licences are portable between on-premises and Azure \u2014 no new licences to buy when you move workloads. A VM that runs on your cluster today runs on NC2 tomorrow with the same tooling, the same snapshots, the same policies.<\/p>\n

What Nutanix handles, and what you handle<\/h2>\n

This is the part to get straight before anything else. NC2 is not a managed service.<\/strong> You decide when, where and how to deploy, expand or pull back \u2014 and you run it. The NC2 Portal automates the parts that would otherwise be painful in a cloud you don’t physically control: it detects an unplanned node failure and inserts a replacement Azure bare-metal node automatically, and it handles cluster expansion. Software lifecycle is Life Cycle Manager in Prism Central, exactly as on-premises.<\/p>\n

For a team already operating Nutanix, that’s the point. For a team that chose a managed cloud service specifically to stop operating a hypervisor, it’s a change of model, and it’s worth being honest about that up front.<\/p>\n

The networking piece is the one to understand<\/h2>\n

Flow Virtual Networking is built in, and the specific benefit Nutanix calls out is that it removes the need for ExpressRoute between NC2 and your other Azure VNets. In practice, this is what lets you run “mixed mode” applications \u2014 a front end on NC2 talking to Azure SQL, Azure Firewall or an analytics service natively inside your VNet \u2014 without a networking project in between.<\/p>\n

It’s also what makes migration clean. Flow lets you preserve your existing IP ranges and topology when workloads move, so the cutover is a move, not a re-addressing exercise. Anyone who has migrated to a cloud and then spent weeks reconciling firewall rules and DNS will appreciate how much that is worth.<\/p>\n

Where it makes sense<\/h2>\n

From the engagements I’ve seen, four situations justify NC2 clearly:<\/p>\n