Cisco Azure Local retirement follows Microsoft hardware rule changes

Cisco Azure Local retirement will remove the networking vendor’s on-premises Microsoft cloud bundles from sale in October, after Microsoft changed the hardware and partner models it supports for the product. The move matters for infrastructure buyers because Cisco is leaving without a direct successor, steering customers toward other hyperconverged infrastructure options on Cisco Compute instead.

Cisco disclosed the decision in a July 24 end-of-life and end-of-sale notice. The company said it would stop selling the Azure Local bundles in October and would not provide a like-for-like replacement. The notice told customers to consider alternative HCI solutions using Cisco Compute.

Azure Local is Microsoft’s on-premises hyperconverged cloud stack. Microsoft has recently positioned it more around sovereign cloud use cases than conventional HCI, according to The Register, which may reduce the urgency for Microsoft if a smaller x86 server partner steps away.

Why is Cisco retiring Azure Local?

Cisco has not given a detailed business rationale for exiting the product. A Cisco spokesperson directed The Register to a June 16 Microsoft blog post, where Microsoft said it had removed the option to deploy Azure Local on “Validated Nodes.”

That change is central because Cisco’s Azure Local products were understood by The Register to fall under the Validated Nodes model. With that deployment path no longer available, Cisco appears to have chosen not to convert its offering into one of Microsoft’s remaining supported models.

Microsoft’s current alternatives are “Premier Solutions” and “Integrated Solutions.” In both models, Microsoft and the hardware or solution provider tie together their support arrangements more closely than under Validated Nodes.

Microsoft pre-sales Azure technical architect Sarah Lean described Validated Nodes on her personal blog as the most flexible way to run Azure Local. She wrote that customers could either buy a complete configuration from a vendor or assemble systems using individual components from a validated list, while keeping control of the hardware, software deployment, firmware, driver updates and Azure Local operating system maintenance.

Cisco’s decision suggests the company did not see enough upside in doing the integration and support work needed for a Premier Solution or Integrated Solution. That is a notable signal for buyers running mixed on-premises and cloud-adjacent infrastructure, even if Cisco is not a major force in the x86 server market.

What this says about Cisco’s HCI position

Hyperconverged infrastructure has already been a difficult category for Cisco. In 2023, the company discontinued its own HyperFlex product and recommended Nutanix to customers instead.

The Azure Local exit keeps Cisco from making another direct push in the category under Microsoft’s stack. It also leaves customers that were considering Cisco hardware for Azure Local with a procurement question: move to another Microsoft-approved Azure Local partner model, or evaluate non-Microsoft HCI options running on Cisco Compute.

Independent analyst Michael Warrilow offered one possible explanation last week, writing that Azure Local is “not yet a suitable candidate for traditional data centre requirements.” If Cisco shares that view, the engineering and certification investment required to stay in Microsoft’s program may have looked hard to justify.

Cisco has not said how many customers bought its Azure Local bundles, how much revenue the product generated, or whether existing deployments will receive any support beyond the published end-of-life terms. Those omissions make it hard to assess customer exposure, but the direction is clear: Cisco is stepping back while Microsoft tightens control over how Azure Local reaches on-premises hardware.

This story draws on original reporting from The Register.