Two platforms, one direction: What HPE's network management convergence actually means for your organisation

There has been an air of anticipation in the market about what will happen to Aruba Central and Juniper Mist now that both sit under the HPE Networking umbrella. Customers have been quietly optimistic about the possibilities this merger could bring, prompting plenty of questions at a recent Customer Advisory Board workshop we ran. As for the answers, well, read on.

HPE is not consolidating Central and Mist into a single platform overnight, but what they are doing is arguably more interesting. They’re deliberately converging the best capabilities of each platform towards the other, so the monitoring and troubleshooting experience becomes largely equivalent, regardless of which side of the house you came from. And they are doing this while also making a measured but significant hardware commitment that changes the economics of the choice altogether.

The dual-platform AP is the pivot point

The clearest signal of where HPE is heading is the emergence of dual-platform access points. The AP-723H is the first of these, a single piece of hardware that can run on either Mist or Central, depending on how it is licensed and managed. From Wi-Fi 8 onwards, this will be the standard model: one AP SKU, one licence, and one price point working across both platforms. The expectation is that this will become generally available in 2027.

This matters enormously for organisations that have historically had to make a binary choice between platforms at the point of hardware procurement. The decision is no longer locked in when you rack the AP. You gain the hardware, and the management decision can evolve with your needs and HPE's platform roadmap - rather than being forced at the point of purchase.

For customers already managing a mixed environment of Aruba and Juniper kit, this is particularly meaningful. Several attendees at our workshop were already operating in exactly that situation, with Juniper at the core and Aruba at the access layer, and were managing the friction between two management experiences. The dual-platform model begins to reduce that friction at the hardware level.

AOS-8 is coming to Wi-Fi 7 APs, and the timeline is now

One of the more immediately practical announcements from HPE concerns AOS-8 support for the new Wi-Fi 7 AP-7xx series. In response to customer demand and feedback, HPE is bringing AOS-8 to these access points, with a planned beta in May 2026 and general availability expected in July. This is significant because it means organisations that want to invest in current Wi-Fi 7 hardware do not need to commit to AOS-10 and the management model changes that come with it.

The practical implication is that you can buy Wi-Fi 7 access points today, run them on AOS-8 through Central, and when your organisation is ready to move to AOS-10, the hardware is already in place. This removes a common objection to hardware investment cycles, where customers hold off on new kit because they are not ready to commit to the accompanying software and management changes. HPE is decoupling those decisions, at least for this transition.

What is actually converging between Mist and Central

The convergence roadmap from HPE focuses on a clear set of capabilities moving in both directions, and it is worth being specific about what those are rather than leaving it at a high-level statement.

Marvis Actions, the AI-driven remediation capability that Mist customers have come to rely on, is being brought to Central. This has been one of the standout differentiators of the Mist platform, and its arrival in Central represents a meaningful uplift for organisations that have been managing networks through Central and have found the AI insights experience less mature by comparison.

Moving in the other direction, the global NOC view that existed in Central - but was absent from Mist - is being brought to the Mist platform. This is the kind of operational visibility that network managers and NOC teams rely on for day-to-day oversight at scale, and its addition to Mist closes a gap that some customers had noted as a limitation.

Client fingerprinting and profiling capabilities are also being significantly improved, with a shift away from static device classification towards behavioural profiling. For example, rather than simply identifying a device as an iPad, the system will be able to distinguish between an iPad used for conference room bookings and an iPad functioning as a point-of-sale terminal - because the network behaviour of those two use cases is fundamentally different. This kind of contextual intelligence has practical implications for policy enforcement, BYOD management and security segmentation.

Across both platforms, agentic AI models are being embedded in the management experience. Rather than replacing the existing assistant interface, these agent models operate in the background, with multiple specialist agents able to investigate specific aspects of a problem and then stitch their findings together to provide a more coherent and actionable response. It’s worth noting that the AI teams across Aruba and Juniper have been collaborating for some time, so the quality of responses and the depth of automated remediation will continue to improve as this collaboration matures.

The sequence matters: Monitoring converges first

HPE has been clear about the order of convergence, and it reflects a considered approach rather than an attempt to force customers through a migration they are not ready for.

1. Monitoring and troubleshooting will converge first.
2. Configuration management, which reflects deeper differences in how the two platforms model network topology and policy, will follow later and more gradually.
3. Over time the card views and dashboard experiences in Mist and Central will become increasingly similar, particularly for the operational tasks that take up most of a network team's day: identifying issues, determining root cause, reviewing client experience data and responding to anomalies.
4. The configuration and provisioning experience will retain more platform-specific character for longer, because that is where the architectural differences are most deeply embedded.

For customers wondering whether they will one day be asked to migrate from one platform to the other, this framing is reassuring. The intent is not to deprecate one experience in favour of the other, but to progressively make the operational experience equivalent, regardless of which platform you are running.

The self-driving network is the destination

The longer-term vision HPE has consistently articulated is the self-driving network. This is where the management platform evolves from surface-level data collection to AI-driven insights, recommendations, assisted remediation, and eventually autonomous operation. HPE has a five-stage model that maps this progression in the same way as autonomous vehicle development is often described - from basic sensors through to full self-driving capability.

This vision is increasingly resonating, particularly in education and other environments where lean IT teams manage dispersed infrastructure across dozens of sites. The appeal of a platform that can detect, diagnose and remediate issues without requiring a technician to be physically present, or even particularly experienced, is clear and practical rather than theoretical.

HPE right now is clear that their AI investment focuses on Day 2 and beyond operations, not on initial configuration. The value lies in ongoing issue detection, root cause analysis and optimisation, with the end result often being a configuration adjustment surfaced by the AI rather than identified through manual investigation. This is a meaningful distinction from tools that apply AI to the provisioning workflow but leave the operational burden largely unchanged.