EMAIL: Action recommended: Migrate from classic Defender for SQL APIs by 16 August 2027

Hi Patrick Riehmers,
We understand that the link provided in the Microsoft Azure notification is returning a 404 error. Please check the affected Azure SQL resource in the Azure portal under Security → Microsoft Defender for Cloud → Configure and confirm the current SQL Vulnerability Assessment configuration.

If the resource is using Classic Configuration, we recommend migrating to Express Configuration. Once migrated, please verify that the vulnerability assessment scan and findings are working as expected.

Also, please check whether any existing scripts or automation are using the Classic SQL Vulnerability Assessment APIs and update them if required.

To help us verify the issue further, please share the affected subscription/resource details and a screenshot of the current Vulnerability Assessment configuration.

Hi,

Thanks for your reply.

Only the "Master" Database from our Test Database will be shown there:

How could i delete/remove this ?

Where do i see, if we have the Classic or Express Configuration?

Thanks for your help.

Hi Patrick Riehmers,

Thanks for sharing the screenshot.
Regarding the Master Database: master is an Azure SQL system database that is automatically maintained by Azure. It is not a customer-created database.
The master database cannot be deleted or removed.
Therefore, seeing master in the Vulnerability Assessment scope/results is expected behavior.
Regarding Classic vs. Express Configuration:
Go to:
Azure Portal → SQL Database → Security → Microsoft Defender for Cloud → Enablement Status → Configure Storage Account is configured → Classic Configuration
No customer-managed Storage Account is configured → Express Configuration Express Configuration is the recommended option because it uses Microsoft-managed storage and does not require the customer to maintain a Storage Account.
Therefore, there is no need to delete the master database. If the concern is that only master is displayed in Vulnerability Assessment, this is related to the Vulnerability Assessment scope/configuration, not an issue with the master database itself.

Hi Patrick Riehmers,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered. 

Hi @SIVASANKAR YEDDULA

Thanks for your reply. Your Hint with the path "Azure Portal → SQL Database → Security → Microsoft Defender for Cloud → Enablement Status → Configure Storage Account is configured → Classic Configuration"

was really helpfull!

Thanks for your help!