Microsoft's new Windows CLAT feature could help organizations move closer to IPv6-only networking without immediately replacing legacy applications that still depend on IPv4.
Key Takeaways:
Organizations are increasingly moving toward IPv6-only or IPv6-first networks as available IPv4 addresses become harder to obtain and manage. However, many business applications, services, and devices still rely on IPv4 connectivity. This dependency creates a major obstacle for enterprises that want to modernize their networks without maintaining both IPv4 and IPv6 infrastructure simultaneously.
Without a transition mechanism, enterprises often must run dual-stack environments that support both IPv4 and IPv6 across their networks. This increases operational complexity, consumes scarce IPv4 address resources, expands the network attack surface, and can drive up infrastructure costs. It also slows IPv6 adoption because organizations must wait for legacy applications to gain native IPv6 support before retiring IPv4.
Microsoft has announced the general availability of Windows CLAT (Customer-side Translator) in Windows 11 version 25H2. CLAT serves as the client-side component of the 464XLAT architecture, which translates IPv4 traffic generated by Windows applications into IPv6 traffic that can travel across IPv6-only networks. On the network side, a NAT64 provider translator converts the traffic when communication with IPv4 resources is required.
This approach allows organizations to continue using IPv4-dependent applications while deploying IPv6-only infrastructure. Windows CLAT supports Wi-Fi, Ethernet, and cellular connections and can automatically detect IPv6-only network environments. It also supports multiple standards-based methods for discovering translation prefixes, which helps enterprises integrate the technology into existing networking environments with minimal user involvement.
Windows CLAT reduces the need for dual-stack networking, but it is not a complete replacement for IPv4. Organizations still need supporting NAT64 infrastructure and must maintain translation services for applications that have not yet adopted IPv6. CLAT simplifies the transition process, but it introduces another translation layer that network teams must understand, monitor, and troubleshoot.
However, for many enterprises, this tradeoff is preferable to indefinitely operating parallel IPv4 and IPv6 infrastructures. CLAT enables a gradual migration strategy that preserves application compatibility while allowing organizations to move toward simpler, more scalable IPv6-only networks.
Windows CLAT gives enterprises a practical path to accelerate IPv6 adoption without waiting for every application and service to become IPv6-native. Organizations can allow IPv4 applications to operate on IPv6-only networks to reduce their dependence on increasingly scarce IPv4 addresses, simplify network design, and potentially lower operational costs.
For IT teams planning large-scale network modernization projects, the availability of Windows CLAT in Windows 11 version 25H2 removes application compatibility issues, which is one of the biggest barriers to IPv6-only deployments. NAT64 infrastructure remains a requirement, but Microsoft’s implementation provides a standards-based transition mechanism that can help organizations modernize their networks without disrupting existing workloads.