@@ -1,6 +1,6 @@ --- layout: Conceptual-title: Classic configuration vulnerability findings in Microsoft Defender for Cloud - Microsoft Defender for Cloud | Microsoft Learn+title: Classic Configuration Vulnerability Findings in Microsoft Defender for Cloud - Microsoft Defender for Cloud | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/azure/defender-for-cloud/configure-vulnerability-findings-classic breadcrumb_path: /azure/breadcrumb/defender-for-cloud/toc.json feedback_help_link_url: https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/bd-p/MicrosoftDefenderCloud@@ -43,9 +43,9 @@ spProducts: platformId: 8371bbb2-fbc1-8e45-87f7-9c5b3d66befa --- -# Classic configuration vulnerability findings in Microsoft Defender for Cloud - Microsoft Defender for Cloud | Microsoft Learn+# Classic Configuration Vulnerability Findings in Microsoft Defender for Cloud - Microsoft Defender for Cloud | Microsoft Learn -This article shows you how to view, remediate, and disable SQL vulnerability assessment findings when you use the classic configuration in Microsoft Defender for Cloud. You can review scan history, disable specific findings, and manage vulnerability assessments programmatically by using PowerShell, Azure CLI, or Resource Manager templates. For an overview of vulnerability assessments, see [SQL vulnerability assessment](sql-azure-vulnerability-assessment-overview).
+When you use the classic configuration in Defender for Cloud, you can view, remediate, and disable SQL vulnerability assessment findings. You can also review scan history, disable specific findings, and manage vulnerability assessments programmatically by using PowerShell, Azure CLI, or Azure Resource Manager templates. For an overview of vulnerability assessments, see [SQL vulnerability assessment](sql-azure-vulnerability-assessment-overview).
 
 Important
 
@@ -55,13 +55,13 @@ Important 
 Express Configuration is now available for Azure SQL Managed Instance and Azure Synapse Analytics Workspaces. Express Configuration extends the Microsoft-managed setup for Azure SQL Database at no extra cost.
 
-Express Configuration lets you enable SQL VA without a storage account. Express Configuration is the recommended mode. It offers the same security value as Classic Configuration with a simpler setup.
+By using Express Configuration, you can enable SQL VA without a storage account. Express Configuration is the recommended mode. It offers the same security value as Classic Configuration with a simpler setup.
 
 A unified REST API (v2026-04-01-preview) manages SQL VA across Azure SQL Database, SQL Managed Instance, Synapse Workspaces, and SQL on machines (Azure VM and Arc-enabled SQL).
 
 ## Prerequisites
 
-First, check whether you use the [express or classic configuration](sql-azure-vulnerability-assessment-overview#configuration-models).
+Check whether you use the [express or classic configuration](sql-azure-vulnerability-assessment-overview#configuration-models).
 
 To find your configuration type:
 
@@ -77,11 +77,11 @@ Select **Scan History** in the vulnerability assessment pane to view previously 
 ## Exempt specific findings (recommendations)
 
-Not all SQL VA findings might be relevant to your organization or configuration, and you might choose to ignore them regardless of their status. To do this, you can [create an exemption](/en-us/azure/defender-for-cloud/exempt-resource) at the subscription or management group level so the recommendation no longer affects your secure score or compliance for that scope.
+Not all SQL VA findings might be relevant to your organization or configuration. You might choose to ignore them regardless of their status. You can [create an exemption](/en-us/azure/defender-for-cloud/exempt-resource) at the subscription or management group level so the recommendation no longer affects your secure score or compliance for that scope.
 
 Note
 
-- The exemption setup succeeds, but it will not take effect unless the **["Azure CSPM" standard is assigned](/en-us/azure/defender-for-cloud/assign-regulatory-compliance-standards)** on the selected scope.
+- The exemption setup succeeds, but it doesn't take effect unless the **["Azure CSPM" standard is assigned](/en-us/azure/defender-for-cloud/assign-regulatory-compliance-standards)** on the selected scope.
 - Creating an exemption requires [specific permissions](/en-us/azure/defender-for-cloud/exempt-resource#prerequisites).
 
 ## Manage vulnerability assessments programmatically
@@ -143,9 +143,9 @@ You can use Azure CLI commands to manage your vulnerability assessments programm 
 ### Manage vulnerability assessments with Resource Manager templates
 
-To configure vulnerability assessment baselines using Azure Resource Manager templates, use the `Microsoft.Sql/servers/databases/vulnerabilityAssessments/rules/baselines` type.
+To configure vulnerability assessment baselines by using Resource Manager templates, use the `Microsoft.Sql/servers/databases/vulnerabilityAssessments/rules/baselines` type.
 
-Ensure you have enabled `vulnerabilityAssessments` before you add baselines.
+Ensure you enable `vulnerabilityAssessments` before you add baselines.
 
 The following ARM template snippet defines vulnerability assessment baseline resources for rules VA2065 and VA1143 in the `master` and `user` databases:
 
@@ -199,7 +199,7 @@ For `master` database and `user` database, the resource names are defined differ - Master database - "name": "[concat(parameters('server\_name'),'/', parameters('database\_name'), '/default/VA2065/**master**')]",
 - User database - "name": "[concat(parameters('server\_name'),'/', parameters('database\_name'), '/default/VA2065/**default**')]",
 
-To handle Boolean types as true/false, set the baseline result with binary input like "1"/"0". The following example shows a baseline resource that uses a binary value for rule VA1143:
+To handle Boolean types as true or false, set the baseline result with string values such as `"1"` or `"0"`. The following example shows a baseline resource that uses a binary value for rule VA1143:
 
 ```json
    {