November 5, 2026 SaaS Alerts release notes
Fortify Action Processor 3.177.0
Enhancements
Emergency access account exclusions for flow-block policies
Version 2 of the flow-block actions can now exclude designated emergency access accounts. Fortify maintains these exclusions during nightly validation. An explicit Exclude Global Administrators = Yes configuration continues to meet the requirements for version 2.
The Designate emergency access accounts setting is now used by these two policies.
Individual sharing can be disabled
Fortify can now disable individual sharing on the Default Sharing Policy by setting Enabled to false. Undo restores the setting captured when the action was first applied. This action is marked Review first because its effect on Microsoft Secure Score has not been confirmed.
Global Reader support for Conditional Access policies
The Global Reader role is now included in the Admin MFA version 2 and sign-in frequency/session timeout Conditional Access policy configurations. Existing tenants receive this change when the action is reapplied.
Fixes
Conditional Access policy processing
Fortify now handles additional Conditional Access policy conditions that previously caused snapshot requests to fail.
Unsupported group types are handled correctly
Fortify no longer attempts to create distribution lists or mail-enabled security groups through Microsoft Graph when restoring missing groups. These unsupported group types are now refused instead of being sent through a creation method that would fail.
Undo behavior after partially successful actions
Undo can now use captured original settings from an apply attempt that includes a failure when the same action cycle also contains a successful apply. A cycle containing only a failed apply does not restore settings.
Original settings are captured before changes are applied
Affected Fortify actions now save their previous settings before making the first configuration change.
Device cleanup stops when existing settings cannot be read
Fortify now refuses to apply the device cleanup action when its pre-check cannot read the existing configuration.
Idle timeout retry handling
Fortify now preserves the configuration information needed when retrying idle timeout changes.
Password protection captures are cleared after a refused create
When Fortify refuses to create a password protection configuration, the associated template capture is now cleared.
Completed Fortify actions remain completed after qualifying apply failures
A Fortify-owned custom action that has already achieved a baseline and satisfied result can remain completed when its newest apply attempt returns a failure, provided the qualifying completion conditions are still met.
