Cisco will stop selling its Azure Local bundles on October 24, 2026, ending a short-lived hardware option for organizations that wanted to run Microsoft’s on-premises hyperconverged platform on Cisco UCS servers.
Cisco’s July 24 end-of-sale notice lists several Azure Stack HCI/Azure Local bundle SKUs based on C220 and C240 M7 servers. It offers no direct successor, instead steering customers toward unspecified alternative HCI products using Cisco Compute. The Register first reported that Cisco linked its decision to Microsoft’s changing Azure Local hardware ecosystem.
For buyers, the immediate distinction matters: this is an end of sale, not an abrupt support cutoff. Cisco says hardware with active, paid support contracts will remain covered under the terms of those contracts, and lists January 24, 2027 as the last ship date.
Azure Local has increasingly favored systems where Microsoft and the OEM share responsibility for the complete platform, including firmware and driver servicing. Microsoft documentation describes Premier Solutions and Integrated Systems as the supported paths for newer catalog hardware, with Solution Builder Extensions used to coordinate OEM firmware and driver updates with Azure Local servicing.
That model reduces the flexibility traditionally associated with validated nodes: servers assembled or configured from approved components, where the customer has more responsibility for lifecycle management. Microsoft’s current Azure Local materials still discuss validated hardware and older validated-node deployments, but the direction of travel is clear—new deployments are being oriented toward pre-integrated, jointly supported systems.
Cisco evidently chose not to build a replacement offering within that tighter model. The company’s notice does not explain whether the cost of certification, ongoing update integration, support obligations, or expected demand drove the decision.
Administrators planning node additions or hardware refreshes should also assume that a Cisco bundle may no longer be an available like-for-like purchase after October. A move to another Azure Local vendor could require validation of cluster compatibility, support ownership, licensing, and whether a mixed-node configuration is permitted for the intended release.
Cisco’s departure follows its 2023 decision to discontinue HyperFlex, its own HCI platform. For Microsoft customers, the result is a narrower choice: Cisco can remain part of the compute and networking stack, but it will no longer sell a branded Azure Local appliance path after this fall.
For buyers, the immediate distinction matters: this is an end of sale, not an abrupt support cutoff. Cisco says hardware with active, paid support contracts will remain covered under the terms of those contracts, and lists January 24, 2027 as the last ship date.
Microsoft is tightening the support boundary
Azure Local has increasingly favored systems where Microsoft and the OEM share responsibility for the complete platform, including firmware and driver servicing. Microsoft documentation describes Premier Solutions and Integrated Systems as the supported paths for newer catalog hardware, with Solution Builder Extensions used to coordinate OEM firmware and driver updates with Azure Local servicing.That model reduces the flexibility traditionally associated with validated nodes: servers assembled or configured from approved components, where the customer has more responsibility for lifecycle management. Microsoft’s current Azure Local materials still discuss validated hardware and older validated-node deployments, but the direction of travel is clear—new deployments are being oriented toward pre-integrated, jointly supported systems.
Cisco evidently chose not to build a replacement offering within that tighter model. The company’s notice does not explain whether the cost of certification, ongoing update integration, support obligations, or expected demand drove the decision.
Existing customers should verify more than entitlement
Cisco Azure Local customers should inventory the exact SKU, Azure Local version, OEM support dates, and their available update path before making expansion plans. The key question is not simply whether the cluster still runs today, but whether its firmware, drivers, and operating-system releases will remain in a supportable combination as Azure Local evolves.Administrators planning node additions or hardware refreshes should also assume that a Cisco bundle may no longer be an available like-for-like purchase after October. A move to another Azure Local vendor could require validation of cluster compatibility, support ownership, licensing, and whether a mixed-node configuration is permitted for the intended release.
Cisco’s departure follows its 2023 decision to discontinue HyperFlex, its own HCI platform. For Microsoft customers, the result is a narrower choice: Cisco can remain part of the compute and networking stack, but it will no longer sell a branded Azure Local appliance path after this fall.
References
- Primary source: The Register
Published: 2026-07-30T01:09:58+00:00
Cisco 'retires' its Azure Local offering rather than catch up to Microsoft’s changed hardware requirements
Redmond now allows only locked-down rigs with joint software and hardware support for its on-prem hyperconverged cloud and Switchzilla won't go therewww.theregister.com - Related coverage: meraki-go.xgslb-v3.cisco.com
- Related coverage: techcommunity.microsoft.com
- Related coverage: cisco.com
- Related coverage: learn.microsoft.com
OEM license for Azure Local overview - Azure Local | Microsoft Learn
Learn about the OEM license for Azure Local, its benefits, license requirements, activation, and more.learn.microsoft.com
