Express Configuration Vulnerability Findings - Microsoft Defender for Cloud | Microsoft Learn
In brief
The documentation was edited for clearer wording, formatting, and navigation across Express/Classic configuration guidance, scan history, finding exclusions, Logic Apps notifications, API usage, and Resource Manager baseline examples.
What Defender admins need to know
Administrators can follow the revised instructions more easily; no action is required.
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.
Express configuration vulnerability findingsConfiguration Vulnerability Findings - Microsoft Defender for Cloud | Microsoft Learn
Microsoft Defender for Cloud provides vulnerability assessment for your Azure SQL databases. Scans detect software vulnerabilities and return findings. You can remediate vulnerabilities or disable findings when needed.
Before you begin, confirm which configuration model your environment uses.
Make sureBefore youknowcontinue, find out whether you're usinguse the express or classic configuration modelbefore you continue..To see which configuration you
're using:use:- In the Azure portal, open the specific resource in Azure SQL Database, Azure SQL Managed Instance, or Azure Synapse.
- Under the Security heading, select Defender for Cloud.
Express Configuration is generally available for Azure SQL Managed Instance and Azure Synapse Analytics Workspaces. Express Configuration extends the generally available Microsoft-managed experience for Azure SQL Database, at no additional cost.
By using Express Configuration allowsConfiguration, you tocan enable SQL VA without configuringsetting up a customer-managed storage account. Express Configuration is the recommended enablement mode andmode. It provides the same security value as Classic Configuration but with a simplifiedsimpler setup.
A unified REST API (v2026-04-01-preview) manages SQL VA consistently across Azure SQL Database, SQL Managed Instance, Synapse Workspaces, and SQL on machines (Azure VM and Arc-enabled SQL).
View scan history
In the Azure portal, open your database resource and under Security, select Defender for Cloud under Security to open the vulnerability assessment pane. Select Scan History to view a history of all scans previously run on this database.
Express configuration doesn't store scan results if they're identical to previous scans. The scan time shown in the scan history is the time of the last scan where the scan results changed.
Disable specific findings from Microsoft Defender for Cloud (preview)
If you have an organizational needyour organization needs to ignore a finding rather than remediate it, you can disable the finding. Disabled findings don't impact your secure score or generate unwanted noise. You can see disabled findings in the "Not applicable" section of the scan results.
When a finding matches the criteria you've defined define in your disable rules, it wondoesn't appear in the list of findings. Typical scenarios might include:
- Disable findings with medium or lower severity
- Disable findings that are non-patchable
Important
To disable specific findings, you need permissions to edit a policy in Azure Policy. LearnFor more ininformation, see Azure RBAC permissions in Azure Policy.
To create a rule, go to Microsoft Defender for Cloud in the Azure portal and select Recommendations to find the relevant recommendation.
Configure email notifications using Azure Logic Apps
To receive regular updates ofabout the vulnerability assessment status for your database, you can use the customizable Azure Logic Apps template.
UsingBy using the customizable Azure Logic Apps template lets you:template, you can:
- Choose
the timing ofwhen to send the email reports. - Have a consistent view of your vulnerability assessment status that includes disabled rules.
- Send reports for Azure SQL Servers and SQL VMs.
- Customize the report structure and appearance to match your organizational standards.
Manage vulnerability assessments programmatically
You can manage SQL vulnerability assessment programmatically by using REST APIs, Azure Resource Manager templates, PowerShell, or Azure CLI.
Unified SQL vulnerability assessment API (recommended)
TheUse the unified SQL vulnerability assessment API version 2026-04-01-preview is recommended for Azure SQL Database, Azure SQL Managed Instance, Azure Synapse Analytics workspaces, and SQL on machines.
- SQL vulnerability assessment settings API reference
- SQL vulnerability assessment baseline rules API reference
Use the ARM template for Azure SQL logical server with express configuration to create a new Azure SQL logical server with express configuration for SQL vulnerability assessment.
To configure vulnerability assessment baselines by using Azure Resource Manager templates, use the Microsoft.Sql/servers/databases/sqlVulnerabilityAssessments/baselines type. Make sureEnsure that vulnerabilityAssessments is enabled before you add baselines.
The following examples show how to set up baselines by using ARM templates:
SetupSet up a batch baseline based on the latest scanresults:results.{ } }Set up batch baseline based on specific
results:results.{ } }Set up baseline for a specific
rule:rule.{ } }Set up batch baselines on the master database based on the latest scan
results:results.{
Manage vulnerability assessments with PowerShell
Express configuration isnPowerShell cmdlets don't supported in PowerShell cmdlets,support express configuration, but you can use PowerShell to invokecall the REST API and access the latest vulnerability assessment capabilities by using the REST API.features. For example, you can:
- Enable express configuration on an Azure SQL Server.
- Set up baselines based on the latest scan results for all databases in an Azure SQL Server.
- Review the Express configuration PowerShell commands reference.
Manage vulnerability assessments with Azure CLI
@@ -1,6 +1,6 @@ --- layout: Conceptual-title: Express configuration vulnerability findings - Microsoft Defender for Cloud | Microsoft Learn+title: Express Configuration Vulnerability Findings - Microsoft Defender for Cloud | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/azure/defender-for-cloud/configure-vulnerability-findings-express 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,7 +43,7 @@ spProducts: platformId: 52d87869-1645-e590-7b7c-11520761d886 --- -# Express configuration vulnerability findings - Microsoft Defender for Cloud | Microsoft Learn+# Express Configuration Vulnerability Findings - Microsoft Defender for Cloud | Microsoft Learn Microsoft Defender for Cloud provides [vulnerability assessment](sql-azure-vulnerability-assessment-overview) for your Azure SQL databases. Scans detect software vulnerabilities and return findings. You can remediate vulnerabilities or disable findings when needed.
@@ -51,9 +51,9 @@ Microsoft Defender for Cloud provides [vulnerability assessment](sql-azure-vulne
Before you begin, confirm which configuration model your environment uses.
-- Make sure you know whether you're using the [express or classic configuration models](sql-azure-vulnerability-assessment-overview#configuration-models) before you continue.
+- Before you continue, find out whether you use the [express or classic configuration model](sql-azure-vulnerability-assessment-overview#configuration-models).
- To see which configuration you're using:
+ To see which configuration you use:
1. In the [Azure portal](https://portal.azure.com), open the specific resource in Azure SQL Database, Azure SQL Managed Instance, or Azure Synapse.
2. Under the **Security** heading, select **Defender for Cloud**.
@@ -67,21 +67,21 @@ Important
Express Configuration is generally available for Azure SQL Managed Instance and Azure Synapse Analytics Workspaces. Express Configuration extends the generally available Microsoft-managed experience for Azure SQL Database, at no additional cost.
-Express Configuration allows you to enable SQL VA without configuring a customer-managed storage account. Express Configuration is the recommended enablement mode and provides the same security value as Classic Configuration with a simplified setup.
+By using Express Configuration, you can enable SQL VA without setting up a customer-managed storage account. Express Configuration is the recommended enablement mode. It provides the same security value as Classic Configuration but with a simpler setup.
A unified REST API (v2026-04-01-preview) manages SQL VA consistently across Azure SQL Database, SQL Managed Instance, Synapse Workspaces, and SQL on machines (Azure VM and Arc-enabled SQL).
### View scan history
-In the [Azure portal](https://portal.azure.com), open your database resource and select **Defender for Cloud** under **Security** to open the vulnerability assessment pane. Select **Scan History** to view a history of all scans previously run on this database.
+In the [Azure portal](https://portal.azure.com), open your database resource and under **Security**, select **Defender for Cloud** to open the vulnerability assessment pane. Select **Scan History** to view a history of all scans previously run on this database.
Express configuration doesn't store scan results if they're identical to previous scans. The scan time shown in the scan history is the time of the last scan where the scan results changed.
### Disable specific findings from Microsoft Defender for Cloud (preview)
-If you have an organizational need to ignore a finding rather than remediate it, you can disable the finding. Disabled findings don't impact your secure score or generate unwanted noise. You can see disabled findings in the "Not applicable" section of the scan results.
+If your organization needs to ignore a finding rather than remediate it, you can disable the finding. Disabled findings don't impact your secure score or generate unwanted noise. You can see disabled findings in the **Not applicable** section of the scan results.
-When a finding matches the criteria you've defined in your disable rules, it won't appear in the list of findings. Typical scenarios might include:
+When a finding matches the criteria you define in your disable rules, it doesn't appear in the list of findings. Typical scenarios might include:
- Disable findings with medium or lower severity
- Disable findings that are non-patchable
@@ -89,7 +89,7 @@ When a finding matches the criteria you've defined in your disable rules, it won
Important
-To disable specific findings, you need permissions to edit a policy in Azure Policy. Learn more in [Azure RBAC permissions in Azure Policy](/en-us/azure/governance/policy/overview#azure-rbac-permissions-in-azure-policy).
+To disable specific findings, you need permissions to edit a policy in Azure Policy. For more information, see [Azure RBAC permissions in Azure Policy](/en-us/azure/governance/policy/overview#azure-rbac-permissions-in-azure-policy).
To create a rule, go to Microsoft Defender for Cloud in the [Azure portal](https://portal.azure.com) and select **Recommendations** to find the relevant recommendation.
@@ -110,21 +110,21 @@ To view, override, or delete a rule:
### Configure email notifications using Azure Logic Apps
-To receive regular updates of the vulnerability assessment status for your database, you can use the [customizable Azure Logic Apps template](https://github.com/Azure/Microsoft-Defender-for-Cloud/tree/main/Workflow%20automation/Notify-SQLVulnerabilityReport).
+To receive regular updates about the vulnerability assessment status for your database, use the [customizable Azure Logic Apps template](https://github.com/Azure/Microsoft-Defender-for-Cloud/tree/main/Workflow%20automation/Notify-SQLVulnerabilityReport).
-Using the customizable Azure Logic Apps template lets you:
+By using the customizable Logic Apps template, you can:
-- Choose the timing of the email reports.
+- Choose when to send the email reports.
- Have a consistent view of your vulnerability assessment status that includes disabled rules.
- Send reports for Azure SQL Servers and SQL VMs.
-- Customize report structure and appearance to match your organizational standards.
+- Customize the report structure and appearance to match your organizational standards.
### Manage vulnerability assessments programmatically
You can manage SQL vulnerability assessment programmatically by using REST APIs, Azure Resource Manager templates, PowerShell, or Azure CLI.
# [Unified SQL vulnerability assessment API (recommended)](#tab/unified-api)
-The unified SQL vulnerability assessment API version `2026-04-01-preview` is recommended for Azure SQL Database, Azure SQL Managed Instance, Azure Synapse Analytics workspaces, and SQL on machines.
+Use the unified SQL vulnerability assessment API version `2026-04-01-preview` for Azure SQL Database, Azure SQL Managed Instance, Azure Synapse Analytics workspaces, and SQL on machines.
- [SQL vulnerability assessment settings API reference](/en-us/rest/api/defenderforcloud-composite/sql-vulnerability-assessment-settings)
- [SQL vulnerability assessment baseline rules API reference](/en-us/rest/api/defenderforcloud-composite/sql-vulnerability-assessment-baseline-rules)
@@ -157,11 +157,11 @@ Use the Azure SQL Database-only API version `2022-05-01-preview` for Azure SQL D
Use the [ARM template for Azure SQL logical server with express configuration](https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.sql/sql-logical-server/azuredeploy.json) to create a new Azure SQL logical server with express configuration for SQL vulnerability assessment.
-To configure vulnerability assessment baselines by using Azure Resource Manager templates, use the `Microsoft.Sql/servers/databases/sqlVulnerabilityAssessments/baselines` type. Make sure that `vulnerabilityAssessments` is enabled before you add baselines.
+To configure vulnerability assessment baselines by using Resource Manager templates, use the `Microsoft.Sql/servers/databases/sqlVulnerabilityAssessments/baselines` type. Ensure that `vulnerabilityAssessments` is enabled before you add baselines.
-The following examples show how to set up baselines using ARM templates:
+The following examples show how to set up baselines by using ARM templates:
-- Setup batch baseline based on latest scan results:
+- Set up a batch baseline based on the latest scan results.
```json
{
@@ -173,7 +173,7 @@ The following examples show how to set up baselines using ARM templates: }
}
```
-- Set up batch baseline based on specific results:
+- Set up batch baseline based on specific results.
```json
{
@@ -204,7 +204,7 @@ The following examples show how to set up baselines using ARM templates: }
}
```
-- Set up baseline for a specific rule:
+- Set up baseline for a specific rule.
```json
{
@@ -219,7 +219,7 @@ The following examples show how to set up baselines using ARM templates: }
}
```
-- Set up batch baselines on the master database based on latest scan results:
+- Set up batch baselines on the master database based on the latest scan results.
```json
{
@@ -236,10 +236,10 @@ The following examples show how to set up baselines using ARM templates:
#### Manage vulnerability assessments with PowerShell
-Express configuration isn't supported in PowerShell cmdlets, but you can use PowerShell to invoke the latest vulnerability assessment capabilities by using the REST API. For example, you can:
+PowerShell cmdlets don't support express configuration, but you can use PowerShell to call the REST API and access the latest vulnerability assessment features. For example, you can:
- [Enable express configuration](powershell-sample-vulnerability-assessment-azure-sql) on an Azure SQL Server.
-- [Set up baselines](powershell-sample-vulnerability-assessment-baselines) based on latest scan results for all databases in an Azure SQL Server.
+- [Set up baselines](powershell-sample-vulnerability-assessment-baselines) based on the latest scan results for all databases in an Azure SQL Server.
- Review the [Express configuration PowerShell commands reference](express-configuration-powershell-commands).
#### Manage vulnerability assessments with Azure CLI
