Blog Post

Networking Blog
4 MIN READ

Announcing General Availability for Network HUD on Windows Server 2025

Basel_Kablawi's avatar
Basel_Kablawi
Icon for Microsoft rankMicrosoft
Nov 17, 2026

When we introduced Network HUD in preview, our goal was simple: help Windows Server operators identify networking problems earlier and troubleshoot them more easily. Customer feedback has helped shape that experience. Today, we’re excited to announce that Network HUD is generally available for eligible Windows Server 2025 Datacenter Failover clusters through Windows Server Management enabled by Azure Arc!

Network HUD helps administrators identify networking conditions that can affect reliability and performance. It brings together information from network adapters, Ethernet drivers, host configuration, and connected physical switches, so teams can investigate issues with less manual correlation and guesswork.

Why we built Network HUD

Host networking problems rarely tell their whole story in one place. A VLAN is missing from a switch port. Driver versions differ across nodes. An adapter repeatedly disconnects. A PCIe bandwidth limitation constrains an otherwise capable network adapter. Investigating these conditions often means piecing together information from switches, hosts, and logs.

Network HUD brings those signals together in the context of Network ATC intents, which describe how your host adapters are configured for management, compute, and storage traffic. It continuously evaluates relevant conditions and surfaces health faults and diagnostic events, with recommended actions to help administrators investigate and resolve issues.

The goal is straightforward: make host networking problems easier to identify and troubleshoot by providing detection and guidance.

What Network HUD does

Network HUD is a cluster-aware diagnostics tool that runs locally on each node. Its detection scenarios include:

  • VLAN consistency checks:
    • Uses Link Layer Discovery Protocol (LLDP) information advertised by physical switches to identify VLAN inconsistencies within and across Failover Cluster nodes. Using this information, it also checks whether VLANs used by local virtual machine workloads are configured on the connected physical switch ports.

  • Ethernet driver checks:
    • Identifies Microsoft-provided inbox Ethernet drivers, flags major and minor driver-version differences, and warns about potentially outdated non-inbox drivers based on their reported age. These checks highlight maintenance needs; they don’t determine whether a newer driver is available.

  • PCIe bandwidth checks:
    • Compares network adapter link speeds with available PCIe bandwidth to identify potential bottlenecks. Missing PCIe information is reported through diagnostic events.
  • Adapter stability monitoring:
    • Detects repeated link disconnections and adapter resets that can affect connectivity and workload performance.
  • Network ATC configuration checks:
    • Identifies intents reporting configuration failures and missing Management, Compute, or Storage intent types that can limit diagnostic coverage.
  • Host-to-switch QoS consistency validation:
    • For storage adapters using RDMA over Converged Ethernet (RoCE), checks whether the connected physical switch port advertises Priority Flow Control (PFC) support for the SMB priority configured on the physical host. Network HUD also identifies missing LLDP information needed for physical network diagnostics.

Together, these checks give administrators more context for investigating host networking conditions and deciding what action to take.

Built for the way you operate

Network HUD is delivered through an Azure Arc extension that installs the Network HUD service and PowerShell module. Once the prerequisites are configured, enable the extension on each cluster node through the Azure portal. It integrates with the experiences you already use:

  • Windows Admin Center for a consolidated view of network health and active faults at a glance.
  • PowerShell for scripting, automation, and integration into your existing operational workflows.

It complements the rest of the Windows Server 2025 networking stack, including Network ATC for intent-based configuration and Storage Spaces Direct (S2D), turning intent-based deployment into intent-based operations.

Requirements

Network HUD supports single-node and multi-node Failover Clusters running on physical Windows Server 2025 Datacenter hosts, with Network ATC intents configured and Storage Spaces Direct enabled.

Each node must be connected to Azure Arc and have Windows Server Management enabled by Azure Arc benefits activated. These benefits are available with Windows Server licenses covered by active Software Assurance or active subscription licenses. Windows Server pay-as-you-go through Azure Arc automatically includes enrollment.

For eligible servers, administrators activate the benefits in the Azure portal under Azure Arc > Licenses > Azure Benefits – Windows Server. This activation is separate from connecting the servers to Azure Arc. See Windows Server Management enabled by Azure Arc for eligibility and activation instructions.

Network HUD requires ongoing Azure Arc connectivity and isn’t supported on virtual-machine hosts or in disconnected deployments.

Additional prerequisites include Hyper-V and its management tools, Data Center Bridging, and LLDP tools. Physical switches must meet the documented validation and configuration requirements, including the LLDP advertisements used for VLAN and PFC checks. Review the installation guide for the complete prerequisites and linked switch requirements.

Thank you to our preview community

Thank you to the customers and partners who evaluated Network HUD during preview and shared their experiences. Your feedback helps us understand the networking challenges that matter in real deployments and continues to inform the product’s direction.

Get started

  1. Review the requirements. Confirm that your Failover Cluster meets the prerequisites and that every node is connected to Azure Arc with Windows Server Management benefits activated.

  2. Enable Network HUD on your cluster nodes from the Azure portal via the Azure Arc extension. Follow the Network HUD installation guide to deploy the extension and verify startup and scenario loading. 
  3. Review network health. Use Windows Admin Center or PowerShell to view active faults and recommended actions.

For a closer look at how Network HUD works, read the overview doc on Microsoft Learn: What is Network HUD for Windows Server?

Explore the broader stack (Network ATC and Storage Spaces Direct) to get the most out of intent-based networking on Windows Server 2025.

Try Network HUD on your eligible cluster and share your feedback in the comments below. Your experiences help shape what comes next.

Updated Nov 16, 2026
Version 1.0

1 Comment

  • Love to see more and more Azure Local features being added to "vanilla" Windows Servers! Customers want more options, and this is definitely useful to have more and more stuff added to WS :-)

    Thanks for sharing :-)

     

    Happy Azure Localling :-)