TOI Author :: Julie Powell

Explore new and enhanced features shipping with CloudVision 2026.1.

We’ve moved feature toggles from the General Settings page and introduced a Features section with new functionality. You can now quickly filter features by name or status to easily customize your CloudVision environment and see which settings have been modified from their default state. 

We’re excited to introduce end-to-end provisioning with Studios, a major step forward in simplifying and accelerating how you manage your network. With these enhancements, Studios now supports the full provisioning lifecycle—from initial onboarding to software management and ongoing configuration—through a single, streamlined workflow. This means less manual effort, faster deployment times, and easier collaboration when using CloudVision as your network’s management plane. The new capabilities also open the door to more advanced automation, helping teams reduce errors and scale operations more effectively. Whether you're replacing devices or enforcing software compliance, Studios now offers a more powerful and intuitive way to get it done.

Network Hierarchy transforms the way you monitor and manage your campus network by providing an aggregated view of metrics and telemetry across distinct network layers. With just a few clicks, you can drill down through the aggregated state of the network to individual interfaces, providing you with both high-level and granular perspectives of the network, device, and interface states.

CloudVision provides support for microperimeter segmentation and enforcement as part of Arista’s Multi-Domain Segmentation Service (MSS) for Zero Trust Networking (ZTN).

ZTN works to reduce lateral movement into increasingly smaller areas where workloads are granularly identified and only approved connections are permitted.

CloudVision allows you to generate event notifications so that you can stay up to date on your network's status and performance. Notification configuration involves formatting notifications, configuring notification platforms, assigning notification receivers, and configuring notification rules.

Use the Authentication Studio to configure RADIUS servers for user authentication and 802.1X authentication and accounting. The 802.1X authentication protocol is a port-based network access control that provides an extra layer of security for both wired and wireless networks.  

View PTP counters to identify the types of messages being sent and received by PTP-enabled devices. Use this to troubleshoot issues with your network PTP configuration and connectivity. When announce and sync messages are present but delay request messages are missing, for instance, it may suggest that a host is having trouble locking to the boundary clock.

CloudVision will generate a Disk Utilization on CloudVision Node Breached Threshold event when disk utilization for a CloudVision node has either exceeded the default threshold or breached the user-configured threshold set in event rules.

 The Software Management Studio is used to manage EOS images and extensions and assign them to devices. You’ll use the studio’s Software Repository to upload EOS images, Streaming Agents, and extensions. You’ll then create or edit a workspace in Studios to assign software from the Software Repository to devices.

Use bearer tokens to provide custom applications or third-party applications, like Ansible, login access to CloudVision. Doing so will allow the application to make configuration changes to EOS devices. Bearer token login can be used with identity providers that issue bearer tokens and have an introspection endpoint. Okta and PingIdentity have been tested for use with CloudVision.

You can now enable CloudVision to combine the authentication and authorization requests that it sends to a RADIUS server into a single request. When RADIUS is configured as the AAA provider, CloudVision will send separate authentication and authorization requests by default. This can cause issues with One-Time Password (OTP) users, as issued passwords are only valid for one request. Note: Non-OTP RADIUS systems will be unaffected by the change. To combine authentication and authorization requests, navigate to Settings > Access Control and enable the Combine Login Auth Requests checkbox.

The Software Management Studio is used to manage EOS images and extensions and assign them to devices. You’ll use the studio’s Software Repository to upload EOS images, Streaming Agents, and extensions. You’ll then  assign software from the Software Repository to devices using a new or open workspace.

CloudVision provides more than 20 overlay options to help you visualize the properties of network devices, interfaces, and links. Use the PTP overlay to visualize the topology of PTP enabled devices and their links. At a glance, you can see which device in a PTP domain is the grandmaster and which devices belong to a PTP domain.

Provisioning Settings allows you to configure CloudVision's default behavior when pushing configuration and image changes to devices. Each setting relates to an action used in Change Control. Ordinarily you should only need to use the default settings, but you can alter them for more control over CloudVision and EOS interactions for devices in your network. 

Use an External Certification Authority (ECA) to ensure secure communication and authentication with CloudVision..By default, Streaming Agent and other applications communicate with CloudVision using mutual-TLS certificates signed by a local certificate authority (CA). You now have the option to integrate CloudVision with Venafi,  an external CA, to sign and verify these certificates.

In order to minimize the volume of change control events, CloudVision has introduced a new event, Change Control Events. Change Control Events is generated when 2 or more of the following events are triggered for the same change control:

CloudVision allows users to maintain multiple login sessions simultaneously. However, to prevent account sharing, administrators can now limit the number of active login sessions a user can have and terminate a user’s open sessions if that have reached their limit and are unable to log in.

A new role permission, Action Execution, has been introduced to control the execution of custom actions when they are run in isolation, such as via Studio Autofill actions and standalone executions in the Action editor. A custom action is a user-created action that has either been installed via a package or has been created using python script and arguments.