Completed -
The scheduled maintenance has been completed.
Aug 7, 00:01 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 4, 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:
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).
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #576521.
Jul 30, 21:11 UTC
Completed -
The scheduled maintenance has been completed.
Aug 1, 00:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 27, 00:00 UTC
Scheduled -
Anticipated Impact: Endpoint Management connections will reestablish, potentially delaying ZTNA updates up to 5 minutes during a single maintenance window.
What to expect during your maintenance window: * EMS connectivity may reestablish, briefly affecting Endpoint Management functions including ZTNA rules. * Temporary impact may last up to 5 minutes.
Note: This maintenance does not impact overall data flow or network connectivity.
This proactive maintenance will follow the same maintenance window scheduling as tenant upgrades and each customer instance will only be impacted once during the week.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #578972.
Jul 24, 20:43 UTC
Completed -
The scheduled maintenance has been completed.
Jul 30, 21:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 30, 17:00 UTC
Scheduled -
Anticipated Impact: FortiSASE UI might be inaccessible for up to 5 minutes
Our Operations team will be performing multiple proactive Software updates on the backend that powers FortiSASE. During the scheduled maintenance window, the FortiSASE UI might be inaccessible for up to 5 minutes. There is no impact to data flow.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #576521.
Jul 24, 18:50 UTC
Completed -
The scheduled maintenance has been completed.
Jul 29, 14:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 29, 10:00 UTC
Scheduled -
Anticipated Impact: Miami Analytics tenants only – Temporary disruption of real-time logging, log forwarding, and historical log access.
To enhance service resilience, the FortiSASE Operations team will migrate Analytics tenants from the MIA-F1 to the MIA-3 PoP. This will occur across a series of rolling maintenance windows. Each customer will be affected only once.
What to expect during your maintenance window:
Temporary disruption of real-time logging and log forwarding. Reset of historical log data available within the SASE portal.
Change in Log Forwarding egress IP to 176.23.135.199.
Note: This maintenance does not impact overall data flow or network connectivity. If you use IP filtering for Log Forwarding, please ensure the new IP is added to avoid disruption.
If you have any questions regarding this maintenance, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #576211.
Jul 24, 18:38 UTC