November 10, 2026 SaaS Alerts release notes
Fortify Action Processor 3.179.5
Enhancements
Tenant default app management policy support
Fortify now supports the tenant default app management policy, including capturing existing settings, merging configuration changes, validating the resulting configuration, and restoring captured settings with Undo. After a write, Fortify confirms the setting on three consecutive reads. A retried write is rebuilt from the latest configuration.
App management policy expiration limits
Fortify supports tightening the 180-day limit for the tenant default app management policy, with a minimum supported value of 90 days. CIS 5.1.5.3 for blocking password addition remains on hold.
Template drift events
Fortify now generates one event per template per tenant, with drift, corrected, and resolved event types. Events are raised after template synchronization sends its reapply operations.
Custom actions use actions metadata
Organization synchronization now builds custom actions only from actions metadata entries designated as custom. One action is built for each action ID. Organization synchronization is refused when the catalog contains no designated custom action metadata. Partners may notice changes to six action titles, which are now taken from actions metadata, as well as categories being populated for licensed Microsoft actions.
FIPS TLS policy
Fortify now uses a FIPS TLS policy requiring TLS 1.2 or later, AES-GCM, P-256/P-384, and SHA-256 or later.
Fixes
Sharing configuration when no previous value exists
When applying a blank sharing configuration, Fortify now records the applied setting and keeps the tenant at none. Subsequent validation evaluates the configuration against that recorded setting. Existing entries created before this change retain the previous validation rule.
Sharing configuration defaults corrected
Fortify now accounts for the Microsoft default sharing configuration of everyone rather than the previously assumed members-may-invite behavior. When no previous setting was captured, Undo continues to restore adminsGuestInvitersAndAllMembers.
Sharing-link Undo retry handling
When restoration of an AnonymousAccess sharing-link setting is refused, Fortify now retries the operation twice at 30-second intervals. Existing handling for Internal and Direct restoration refusals is unchanged.
Teams meeting configuration restoration
Fortify now correctly handles the EnableWorkIQTranscriptAccess setting when restoring Teams meeting configurations. Snapshots created before the setting existed omit it.
Nightly action synchronization protects newer changes
Fortify now checks the last-updated state of each action document during nightly synchronization. If a document changed after the synchronization process read it, Fortify skips the update instead of overwriting the newer change.
Duplicate partner connections are removed during disconnect
Disconnect now removes every organization connection associated with the same partner.
Conditional Access pre-read failures are no longer graded as non-compliant
Fortify now returns a not-read result when a Conditional Access pre-read fails instead of grading the configuration as non-compliant. This also prevents the related Conditional Access ownership processing error.
Directory setting retry handling
Directory-setting updates now retain their status so that 404 responses can be retried correctly. A 404 response that remains after the retries is classified as a -1403 failure.
Validation failures can return no verdict
Fortify validation now returns no verdict for additional failures where a compliance result cannot be determined. Authentication, -1410, and other non-actionable failures are excluded from validation failure logging.
Cloud Apps service errors are treated as inconclusive
Cloud Apps 5xx responses are now treated as inconclusive rather than being interpreted as a rejected token.
Missing shared mailbox action documents no longer produce a compliant result
Fortify_disableSharedMailboxSignin no longer reports a compliant result when its action document is missing.
Intune device cleanup validation preserves tenant state
Intune device cleanup validation now returns both its validation result and tenant state.
