October 20, 2026 SaaS Alerts release notes
Fortify Action Processor 3.136.0
Enhancements
Compliance checks support on-demand tenant evidence reads
Compliance checks can now use on-demand tenant reads to provide evidence for read-only controls within a coverage request.
Remediation definition versioning is supported
Remediation definitions now support versioning for grading, identifying when an update is available, template version pinning, and minimum mapping versions.
Regression information is improved
Regressions now include the reason for the regression and when it occurred. Structured findings from graded checks are also retained with the regression information.
Microsoft action grading supports definition versions
Microsoft actions can now be graded using definition versions, with version 1 receiving full Secure Score points.
Template version pinning is improved
Template application now uses the pinned remediation version and does not downgrade it. Stalled applications are requeued using their assigned version.
Template drift correction can be configured
Templates now support disabling drift correction. Drift reports also include regression reason information.
Additional CIS Microsoft 365 compliance checks are available
Compliance checks are now available for CIS Microsoft 365 controls 1.1.4, 2.1.10, 3.2.3, and 5.1.2.1.
Agent blueprint creation can be restricted
Fortify now includes the fortify_restrictAgentBlueprintCreation remediation.
Additional Entra ID device-management remediations are available
Fortify now includes the following remediations for CIS controls 5.1.4.1 through 5.1.4.5:
-
fortify_restrictEntraDeviceJoin
-
fortify_limitDevicesPerUser
-
fortify_restrictRegisteringUserLocalAdmin
-
fortify_noGlobalAdminLocalAdminOnJoin
-
fortify_enableEntraLaps
Microsoft actions account for required licenses
Twenty-five Microsoft Cloud App Security-tagged actions across Entra ID, Intune, SharePoint, Microsoft 365 admin center, and Microsoft Purview now account for the licenses they require.
ConnectWise cloud applications can be disabled
Fortify now includes the fortify_disableConnectWiseCloudApps remediation.
Fortify application credentials can be reviewed and removed on demand
Fortify now supports on-demand credential sweeps for its own application connections, with options to report or remove applicable credentials.
Application instance property lock is supported
Fortify now includes the fortify_appInstancePropertyLock remediation with enforcementScope support.
Application credential maintenance is automated
Fortify now performs a nightly credential sweep for its own application connections in removal mode. Retired credentials are recorded, and organizations that previously refused the operation are automatically repaired.
Fixes
Teams trial-tenant domains are read correctly
Teams AllowedTrialTenantDomains values are now read as domain objects.
Defender undo operations are more reliable
A race condition affecting Defender undo operations has been addressed.
Integrated Apps preserves restrictive settings
Integrated Apps now defaults to DoNotAllow and does not loosen that setting.
Scheduled sign-in session revocation handles deleted organizations correctly
Scheduled sign-in session revocation no longer continues processing after its organization has been deleted.
SharePoint timeout handling is improved
Applicable SharePoint timeout responses are now treated as transient.
Idle-timeout changes handle object conflicts more reliably
Idle timeout processing now rereads the configuration when an object conflict occurs.
Disconnected organizations are handled more safely
Disconnecting an organization now removes its backup configurations and retires orphaned processing. Run, drift, and restore operations are also prevented for disconnected organizations.
Conditional Access snapshots handle agent identities correctly
Conditional Access policy snapshot capture now skips agent-identity targeting. Restore operations also prevent the use of a deleted excluded agent identity.
Risk-based Conditional Access policies are improved
User risk and sign-in risk policies now support a sign-in frequency of Every time. Conditional Access undo operations also restore a displaced policy to its recorded state.
Risky user policy handling is improved
User risk policy processing and the fortify_signInFrequencyRiskyUser remediation now maintain a single risky user policy.
Coverage failure messages are improved
Coverage failure messages now provide partner-safe information.
ConnectWise compliance results are reported correctly
The ConnectWise remediation no longer returns a validation result that can cause nightly processing to report that compliance could not be determined.
Teams DLP processing is more reliable
Teams DLP processing now stops when the required license is unavailable, skips policies using the Applications workload, and no longer incorrectly reports successful completion in affected scenarios.
Outbound spam processing handles concurrent policy removal
Outbound spam processing now continues correctly when a related policy is removed concurrently.
Ask AI - MSFT Agent
Enhancements
Copy Intune policies between organizations
You can now copy, clone, or duplicate an Intune configuration policy to another organization, including settings catalog policies, endpoint security policies, and security baselines. All settings in the source policy are copied, and a single approval card identifies the policy, source and destination organizations, and number of settings. Copied policies are not assigned automatically and can be assigned separately. Policies containing secret values, such as passwords, cannot be copied and must be created in the Intune admin center.
Compare and match Intune policies across organizations
You can now compare Intune configuration policies, endpoint security policies, and security baselines within the same organization or across organizations. The assistant identifies differences between the policies and provides exact counts. If there are too many differences to display in a single response, the assistant indicates that additional differences exist. You can then make one policy match another while preserving selected settings and approve the changes on a card. When applying the same change across multiple organizations, you review the differences for the first organization and approve the change once for the remaining organizations. Organizations whose policies differ in other ways are skipped and identified.
Single approval for changes across up to 50 organizations
Changes that apply to multiple organizations can now be approved once for up to 50 organizations. The assistant first applies the change to one organization and, if successful, applies it to the remaining organizations at the same time. A failure in one organization does not prevent changes in the others. The approval card lists the steps and the organizations they apply to, and results identify each organization as completed, failed with the reason, or skipped. For changes involving more than 50 organizations, the assistant identifies this before approval and divides them into runs of up to 50.
Improved handling when Microsoft AI services are busy
When Microsoft's AI service is temporarily unable to handle a request because of capacity, the assistant now sends the request to a backup AI model instead of returning an error. Responses may take longer while the service is busy. The switch occurs only before a response begins, preventing duplicate responses.
Faster sign-in log searches across multiple days
Sign-in log searches covering two or more days now process portions of the requested period at the same time, improving search speed and reducing timeouts. If part of a search cannot be completed, the assistant reports how far back the available results extend instead of returning no results.
Clearer Teams error recovery guidance
When an error occurs in Teams, the message now instructs you to type /new to start a new conversation if the issue continues. The reference shown in the error message now identifies the conversation and remains the same for all messages within it, so seeing the same reference again does not indicate that the same error has occurred.
Fixes
Improved completion of multi-organization changes
Multi-organization changes now complete in a single run under typical conditions, preventing approved changes from stopping part way when required tools are reported as unavailable. If a change must pause, the assistant provides a card that resumes the operation from where it stopped.
Clearer impact information for authentication methods migration
When completing a migration to the authentication methods policy, the assistant now checks which authentication methods users have registered and identifies methods that will no longer be available after the migration, along with the number of users who have each method. This information is also included on the approval card. Completing the migration stops the legacy MFA and password reset method settings from applying, which can affect users who rely on methods that are not allowed by the new policy, such as Microsoft Authenticator, text message, or voice call.
Accurate Intune policy assignment information
Intune settings catalog and endpoint security policies now report their assignments accurately, including the groups, users, or devices targeted by the policy.
Improved handling of Intune apps that require packages
The assistant no longer creates Intune Win32 or line-of-business apps that require an app package it cannot upload, preventing apps from becoming stuck in a "Your app is not ready yet" state. This includes .intunewin, .msi, .appx, .pkg, .ipa, and .apk packages. The assistant now directs you to the Intune admin center, where the package can be uploaded and the app created.
Intune policy assignment removals can now be undone
When removing an assignment from an Intune policy, the assistant now records the assignment before removing it. The removal runs as part of the approved change without requiring a separate confirmation that it cannot be undone, and the assignment can be restored later.
Improved resumption of paused multi-organization changes
Multi-organization changes that have started now remain resumable for 24 hours from the last time they ran or you requested that they resume. If a change expires, the assistant reports how many organizations were completed and offers to set up the remaining organizations again.
Improved policy copies across multiple organizations
When copying a policy across multiple organizations, an organization that already has a policy with the same name and settings is left unchanged, provided no other changes are planned for it, and the copy continues with the remaining organizations. The final summary identifies these organizations separately. If a same-named policy has different settings, the policy is still copied.
Improved Teams approval cards for policy matching
Policy matching across multiple organizations in Teams now provides an approval card for up to 50 organizations. The card lists all settings selected to be preserved and displays each organization on a single line.
Clearer Teams approval guidance
When an approval for a multi-step change is typed into Teams instead of submitted from the approval card, the assistant now explains that the change must be approved using the Approve button on the card and directs you to that card.
Improved handling of backslashes in Intune setting values
Intune policy setting changes now correctly handle values containing a backslash, preventing these changes from incorrectly failing with a message that nothing was staged.
