Sql Azure Vulnerability Assessment Rules
In brief
The documentation now notes the transition from grouped recommendations to individual recommendations and explains that the Scanner filter can locate SQL Vulnerability Assessment recommendations in alerts and recommendations experiences. It also updates the changelog link.
What Defender admins need to know
Administrators may see SQL vulnerability assessment recommendations organized differently and can use the Scanner filter to find them.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
The rules shown in your database scans depend on the SQL version and platform that was scanned.
For a list of changes to these rules, see SQL vulnerability assessment rules changelogSQL vulnerability assessment rules changelog.
Related information
@@ -14,7 +14,12 @@ Applies to: :::image type="icon" source="./media/icons/yes-icon.png"::: Azure S The rules shown in your database scans depend on the SQL version and platform that was scanned. -For a list of changes to these rules, see [SQL vulnerability assessment rules changelog](sql-azure-vulnerability-assessment-rules-changelog.md).+For a list of changes to these rules, see [SQL vulnerability assessment rules changelog](/azure/defender-for-cloud/sql-azure-vulnerability-assessment-rules-changelog).++> [!NOTE]+> - Defender for Cloud is transitioning SQL vulnerability assessment findings from the grouped recommendations model to individual recommendations. As part of this change, the recommendations **SQL databases should have vulnerability findings resolved** and **SQL servers on machines should have vulnerability findings resolved** will be **deprecated as of July 31, 2026** and fully replaced by the new individual recommendations. For details on what changed and how to adjust your workflows, see [Transition from grouped to individual recommendations](transition-grouped-individual-recommendations.md).+>+> - You can easily locate SQL vulnerability assessment recommendations in the alerts and recommendations experiences by setting the **Scanner** filter to **SQL Vulnerability Assessment**. ## Related information 