Microsoft Defender for Cloud
Cloud and workloadsSql Azure Vulnerability Assessment Overview
In brief
The documentation now states that APIs for classic vulnerability assessment configuration and classic Defender for SQL Advanced Threat Protection will be retired on August 16, 2027, with migration guidance provided.
What Defender admins need to know
Administrators using these APIs should follow the migration guidance before the retirement date to avoid disruption.
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.
@@ -23,6 +23,9 @@ Vulnerability assessment is part of [Microsoft Defender for Azure SQL](defender- > [!NOTE] > Vulnerability assessment is supported for Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics. Databases in Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics are collectively referred to as databases in this article. The server refers to the [server](/azure/azure-sql/database/logical-servers) that hosts databases for Azure SQL Database and Azure Synapse. +> [!IMPORTANT]+> The APIs used for classic vulnerability assessment configuration will be retired on **August 16, 2027**, together with the classic Defender for SQL Advanced Threat Protection APIs. For migration guidance, see [Prepare for the retirement of classic Defender for SQL APIs](migrate-classic-defender-for-sql-apis.md).+ > [!IMPORTANT] > Express Configuration is generally available for Azure SQL Managed Instance and Azure Synapse Analytics Workspaces. This extends the generally available Microsoft-managed experience for Azure SQL Database, at no additional cost. >