FortiSASE Proactive Software Maintenance - FortiSASE release 26.2.2

Scheduled Maintenance Report for FortiSASE

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Aug 04, 2026 - 00:00 UTC

Scheduled

Anticipated Impact: Potential for short interruption of customer instances and configuration portal during the window.

The Operations team will be installing a rolling software update. There is potential for short connectivity impact (approximately ~1-2 minutes) for each customer instance and the configuration portal while these components are updated. No other impact on service delivery is expected.

Tenant upgrades to 26.2.2 will be processed Tuesday, August 4th through Thursday, August 6th. Upgrades will follow your assigned maintenance window, consistent with prior scheduled maintenances. Customers who have configured a preferred maintenance window in the FortiSASE portal will be upgraded during their selected hours. For details on maintenance window scheduling, see:

https://docs.fortinet.com/document/fortisase/latest/administration-guide/190872/appendix-e-monthly-maintenance

For FortiSASE-v7.4 release:

For integrating a private AD server without exposing it to the internet, added support for creating an AD connector API key in FortiSASE. This API key is used to configure the FortiClient EMS AD Connector to establish a tunnel with FortiSASE. This feature requires a FortiSASE instance supporting FortiClient 7.4.
Added support for ZTNA UDP traffic forwarding from FortiClient 7.4 endpoints. This feature requires an instance supporting FortiClient 7.4, FortiClient 7.4.1 or later installed on endpoints and the FortiGate ZTNA application gateway to be running FortiOS version 7.6.0 or later.
Added new best practice recommendation to detect a newer Security PoP location with superior performance for the same geographic region and guide the user on how to migrate to the new security PoP.
Support has been added for automatic endpoint vulnerability patching in the Operations > Endpoints > Endpoint details pane.
Added support for Secure Browser SSO domain integration where an email address domain for end users to log into is integrated with Secure Browser to support BYOD use cases without using a deployment script.
Added enhancements to SCIM server support including support for large SCIM user populations, support for on-demand provisioning from Entra ID after initial provisioning, and support for more robust handling of error conditions.
Added support for the optional Local ID type in the IPsec Phase 1 settings for the on-ramp tunnel custom device type for third-party devices that require using an IP address for the local ID type.
A RADIUS server timeout option has been added in Access & authentication > RADIUS when creating or editing a connection.
FortiClient 7.4.7 support has been added for the Linux platform for IPsec and SSL VPN tunneling.
Support has been added for the latest FortiClient version for mobile platforms (Android and iOS).
Added support for the MSI version of the FortiClient Windows installer since it was unavailable for new instances created in FortiSASE-v7.4 from 25.4.b to 26.2.1.a.
The FortiSASE Network Tools page (https://speed.fortisase.com/) supports performing speed tests both on and off FortiSASE tunnels.
Added support for Public Cloud security PoPs: Monterrey (Mexico).
Added support for Fortinet security PoPs: Taipei (Taiwan).
Updated support for Fortinet security PoPs: Off-shore Dubai (United Arab Emirates).

For further information on what's new: https://docs.fortinet.com/document/fortisase/latest/release-notes/661728/whats-new

If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #576521.
Posted Jul 30, 2026 - 21:11 UTC
This scheduled maintenance affects: Fortinet Cloud Locations (Ashburn, VA, US (IAD-F1), Dallas, TX, US (DFW-F1), Dubai, UAE (DXB-F1), Frankfurt, Germany (FRA-F1), Hong Kong, China (HKG-F1), Komagome, Japan (TYO-F1), London, United Kingdom (LON-F1), Miami, FL, US (MIA-F1), Ottawa, Canada (YOW-F1), Paris, France (PAR-F1), San Jose, CA, US (SJC-F1), Singapore (SIN-F1), Sydney, Australia (SYD-F1), Tokyo, Japan (TYO-F2), Toronto, Canada (YTO-F1), Valbonne, France (NCE-F1), Vancouver, Canada (YVR-F2), Bangalore, India (BLR-F1), Frankfurt, Germany (FRA-F2), San Jose, CA, US (SJC-F2), Pune, India (PNQ-F1), London, United Kingdom (LON-F2), Paris, France (PAR-F2), Singapore (SIN-F2), Miami, FL, US (MIA-F2), Dallas, TX, US (DFW-F2), Istanbul, Turkey (IST-F1), Johannesburg, South Africa (JNB-F1), Dubai, UAE (DXB-F2), San Jose, CA, US (SJC-F3), Frankfurt, Germany (FRA-F3), Paris, France (PAR-F3), Ashburn, VA, US (IAD-F3), London, United Kingdom (LON-F3), Plano, TX, US (DFW-F3), Madrid, Spain (MAD-F1), Singapore (SIN-F3), Toronto, Canada (YTO-F2), Sydney, Australia (SYD-F2), Paris, France (PAR-F4), Frankfurt, Germany (FRA-F4), São Paulo, Brazil (GRU-F1), Vancouver, Canada (YVR-F3), San Jose, CA, US (SJC-F4), Burnaby, Canada (YVR-F4), Ashburn, VA, US (IAD-F4), Plano, TX, US (DFW-F4), Madrid, Spain (MAD-F2), Komagome, Japan (TYO-F4), Auckland, New Zealand (AKL-F1), London, United Kingdom (LON-F4), Frankfurt, Germany (FRA-F5), Toronto, Canada (YTO-F3), Singapore (SIN-F4), Miami, FL, US (MIA-F3), Burnaby, Canada (YVR-F5), Bangalore, India (BLR-F2), Ashburn, VA, US (IAD-F5), Sydney, Australia (SYD-F3), Dubai, UAE (DXB-F3), Taipei, Taiwan (TPE-F1), Ashburn, VA, US (IAD-F2), Tokyo, Japan (TYO-F3), San Jose, CA, US (SJC-F5), Kamloops, Canada (YKA-F1)), FortiSASE Services (FortiSASE Portal, Endpoint Management), and Public Cloud Locations (Johannesburg, South Africa (JNB-G2), Milan, Italy (MIL-G1), Tel Aviv, Israel (TLV-G1), Hamina, Finland (HEL-G2), Eemshaven, Netherlands (AMS-G2), Tel Aviv, Israel (TLV-G2), Madrid, Spain (MAD-G2), Melbourne, Australia (MEL-G2), Santiago, Chile (SCL-G2), Seoul, South Korea (SEL-G2), Doha, Qatar (DOH-G2), Ashburn, VA, US (IAD-G2), The Dalles, OR, US (PDX-G2), Jakarta, Indonesia (JKT-G2), Milan, Italy (MIL-G2), São Paulo, Brazil (SAO-G2), Mumbai, India (BOM-G2), Las Vegas, NV, US (LAS-G2), Dammam, Saudi Arabia (DMM-G2), Taipei, Taiwan (TPE-G2), Osaka, Japan (OSA-G2), Hong Kong, China (HKG-G2), Dallas, TX, US (DFW-G2), Sydney, Australia (SYD-G2), Querétaro, Mexico (QRO-G2), Dublin, Ireland (DUB-A1), Perth, Australia (PER-A1), Auckland, New Zealand (AKL-A1), Delhi, India (DEL-G2), Chicago, IL, US (ORD-A1), Zurich, Switzerland (ZRH-G2), Warsaw, Poland (WAW-G2), Buenos Aires, Argentina (BUE-A1), St. Ghislain, Belgium (BRU-G2), Lima, Peru (LIM-A1), London, United Kingdom (LON-G2), Manila, Philippines (MNL-A1), Toronto, Canada (YTO-G2), Paris, France (PAR-G2), Frankfurt, Germany (FRA-G2), Singapore (SIN-G2), Miami, FL, US (MIA-A1), Montreal, Canada (YMQ-G2), Dubai, UAE (DXB-A1), Tokyo, Japan (TYO-G2), Bangkok, Thailand (BKK-A1), Columbus, OH, US (CMH-G2), Moncks Corner, SC, US (CHS-G2), Cyberjaya, Malaysia (KUL-A1), Bogotá, Colombia (BOG-O1), Vinhedo, Brazil (VCP-O1), Paris, France (PAR-O1), Mumbai, India (BOM-O1), Sydney, Australia (SYD-O1), London, United Kingdom (LON-O1), Muscat, Oman (MCT-A1), Milan, Italy (MIL-O1), Frankfurt, Germany (FRA-O1), Jeddah, Saudi Arabia (JED-O1), Abu Dhabi, UAE (AUH-O1), Ashburn, VA, US (IAD-O1), Stockholm, Sweden (STO-O1), Chicago, IL, US (ORD-O1), Osaka, Japan (OSA-O1), Montreal, Canada (YMQ-O1), Melbourne, Australia (MEL-O1), Amsterdam, Netherlands (AMS-O1), Santiago, Chile (SCL-O1), Dubai, UAE (DXB-O1), Monterrey, Mexico (MTY-O1), Riyadh, Saudi Arabia (RUH-O1)).