This is a What’s new preview for the next FortiSASE release. Please note that any support tickets raised for additional questions will not be considered. Other than this preview section, FortiSASE documentation still reflects the current 25.1.51 (25.1.b) release and will be updated at the end of the FortiSASE maintenance window. For details about FortiSASE maintenance, see Appendix E – Monthly maintenance.

• Added support for displaying endpoint details in Network > Managed Endpoints > Endpoints and Network > Connected Users including FortiSASE VPN Tunnel IP and FortiSASE agent session details, and the Last Seen timestamp in Managed Endpoints. The FortiSASE VPN Tunnel IP can be used with server-client applications with server traffic originating from SPA hubs destined for a FortiSASE managed endpoint.
• Added support for displaying the learned BGP multi-exit discriminator (MED) values in Health and VPN Tunnel Status > View Learned BGP Routes when Network > Network Configuration is configured with Hub selection method as BGP MED.
• Added datacenter support for Querétaro, Mexico and Sydney, Australia as Public Cloud locations.
• Added datacenter support for Sao Paulo, Brazil as a Fortinet Cloud location.

What’s new for 25.1.51 (25.1.b)

• Added support for the SD-WAN On-Ramp connection add-on license for 1-2000 FortiGate IPsec connections. Since you can purchase a maximum of eight SD-WAN On-Ramp locations for a single account, with SD-WAN On-Ramp connection add-on licenses it is possible for an account to have a maximum of 16000 SD-WAN On-Ramp connections. See SD-WAN On-Ramp.
• Added support for the agentless zero trust network access (ZTNA) bookmark portal to show private applications’ bookmarks based on the authenticated user’s permission level which is controlled by Agentless ZTNA bookmark policies. See Configuring the bookmark portal.
• Added enhancements to the Network Lockdown feature by enabling FortiClient endpoints to enter strict lockdown with a configurable grace period of 0 seconds. Also added support for detecting and exempting traffic to captive portals and domains specified under Exempt destinations. See Network lockdown.
• Added enhancements to the Geofencing feature by enabling granular control over prioritization of connection attempts and failover to connections of type On-premise device and Security PoP based on the endpoint’s country or region. See Geofencing.
• Added support for administrators to clone endpoint profiles using an existing endpoint profile, simplifying profile management and reducing configuration time. See Profiles.
• Added support to configuration of ZTNA application gateway and ZTNA destinations under Configuration > Agent-based ZTNA. These configuration settings can now be easily referenced and applied to individual endpoint profiles under ZTNA tab, streamlining ZTNA configuration. See ZTNA.
• Added enhancements to Digital Experience Monitoring (DEM), enabling FortiSASE administrators to view TCP latency metrics for endpoints as a Beta feature, offering deeper visibility into underlay network performance from the endpoint to FortiSASE Security PoP. See Digital experience: TCP latency.
• Added support for an increased maximum number of FortiAP edge devices that FortiSASE supports. See SIA for FortiAP site-based remote users.
• Added datacenter support for Madrid, Spain as a Fortinet Cloud location. See Global data centers.
• Added support for signing a preconfigured FortiClient installer using your own CA certificate or using the Fortinet CA certificate via FortiCare Support ticket request.