Microsoft Defender for Cloud
Architecture and deploymentDeploy vulnerability assessment on your Azure SQL databases (Classic)
In brief
The article now directs administrators to review prerequisites, including enabling Microsoft Defender for Azure SQL, and clarifies that express-configuration vulnerability assessment scans do not require a storage account.
What Defender admins need to know
Review the prerequisites before enabling classic vulnerability assessment; no immediate action is required.
Summaries are generated from the documentation change itself.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
Deploy vulnerability assessment on your Azure SQL databases (Classic)
In this article, you learn how to enable vulnerability assessment classic, so you can find and remediate database vulnerabilities. Before you begin, review the prerequisites, including enabling Microsoft Defender for Azure SQL. We recommend that you enable vulnerability assessment using the express configuration so you aren't dependent on a storage account (generally available for Azure SQL Database, Azure Managed Instance and Azure Synapse Analytics Workspace).
Prerequisites
If your environment still depends on storage-account based scanning, you can enable vulnerability assessment in the classic configuration.
If you have Azure SQL databases with vulnerability assessment enabled in the classic configuration, you can enable the express configuration so that assessmentsvulnerability assessment scans don't require a storage account.
If you have Azure SQL databases with vulnerability assessment disabled, you can enable vulnerability assessment with the classic configuration.
@@ -1,17 +1,17 @@ --- title: Deploy vulnerability assessment on your Azure SQL databases (Classic) description: Learn how to enable the classic configuration of SQL vulnerability assessment on Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics.-ms.date: 12/10/2024+ms.date: 07/03/2026 ms.service: defender-for-cloud ms.topic: how-to-ms.custom: sqldbrb=3+ms.custom: sqldbrb=3, msecd-doc-authoring-1013 #customer intent: As a database administrator, I want to enable SQL vulnerability assessment in classic mode when storage-account based scans are required. ai-usage: ai-assisted --- # Deploy vulnerability assessment on your Azure SQL databases (Classic) -In this article, you learn how to enable [vulnerability assessment](sql-azure-vulnerability-assessment-overview.md) classic, so you can find and remediate database vulnerabilities. We recommend that you enable vulnerability assessment using the [express configuration](sql-azure-vulnerability-assessment-enable.md) so you aren't dependent on a storage account (**generally available for Azure SQL Database, Azure Managed Instance and Azure Synapse Analytics Workspace**).+In this article, you learn how to enable [vulnerability assessment](sql-azure-vulnerability-assessment-overview.md) classic, so you can find and remediate database vulnerabilities. Before you begin, review the [prerequisites](#prerequisites), including enabling Microsoft Defender for Azure SQL. We recommend that you enable vulnerability assessment using the [express configuration](sql-azure-vulnerability-assessment-enable.md) so you aren't dependent on a storage account (**generally available for Azure SQL Database, Azure Managed Instance and Azure Synapse Analytics Workspace**). ## Prerequisites @@ -26,7 +26,7 @@ By default, when you enable the Defender for Azure SQL plan in Defender for Clou If your environment still depends on storage-account based scanning, you can enable vulnerability assessment in the classic configuration. -If you have Azure SQL databases with vulnerability assessment enabled in the classic configuration, you can enable the express configuration so that assessments don't require a storage account.+If you have Azure SQL databases with vulnerability assessment enabled in the classic configuration, you can enable the express configuration so that vulnerability assessment scans don't require a storage account. If you have Azure SQL databases with vulnerability assessment disabled, you can enable vulnerability assessment with the classic configuration.