Sql Azure Vulnerability Assessment Rules Changelog

@@ -10,6 +10,16 @@ ai-usage: ai-assisted  This article details the changes made to the SQL vulnerability assessment service rules. Rules that are updated, removed, or added will be outlined below. For an updated list of SQL vulnerability assessment rules, see [SQL vulnerability assessment rules](sql-azure-vulnerability-assessment-rules.md). +## July 2026++> [!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](/azure/defender-for-cloud/transition-grouped-individual-recommendations)**.++|Recommendation ID  |Recommendation Title  |Change details  |+|---------|---------|---------|+| 82e20e14-edc5-4373-bfc4-f13121257c37 | SQL databases should have vulnerability findings resolved | Deprecated |+| f97aa83c-9b63-4f9a-99f6-b22c4398f936 | SQL servers on machines should have vulnerability findings resolved | Deprecated |+ ## September 2023  |Rule ID  |Rule Title  |Change details  |