Error trying to find out how "The way SQL vulnerability assessment findings are consumed in Defender for Cloud is changing"

The aka.ms link is intended to describe the change where SQL Vulnerability Assessment findings in Microsoft Defender for Cloud are moving from a server-level aggregated model to database-level recommendations. The short link itself is currently not resolving; this cannot be fixed from the Defender for Cloud side and must be corrected by Microsoft.

The relevant information is already documented in the Defender for Cloud release notes:

• SQL Vulnerability Assessment rules now generate separate assessments per affected database.
• These assessments appear and are managed as recommendations in the Defender for Cloud Recommendations page.
• Previously, findings were aggregated at the server/instance level under recommendations such as:
  • SQL databases should have vulnerability findings resolved
  • SQL servers on machines should have vulnerability findings resolved
• The new database-level experience keeps the same scanning logic, rules, queries, schedules, APIs, and pricing; only the way findings are consumed and managed changes.
• During preview, the new database-level assessments do not affect Secure Score in the Azure portal but do contribute to Secure Score in the Defender portal.
• The SQL vulnerability assessment rules reference has been updated with the new database-level recommendation names and assessment identifiers.
• The existing server-level (aggregated) experience remains available during preview.

To understand and prepare for the change without using the broken aka.ms link:

1. Review the Defender for Cloud release notes section describing the February 2026 change to SQL Vulnerability Assessment consumption.
2. Review the SQL vulnerability assessment rules reference to see the updated database-level recommendation names and IDs.
3. In Defender for Cloud, open Recommendations and locate the SQL VA-related recommendations (both the existing server-level ones and any new database-level ones) to see how they appear in the environment.

The broken aka.ms link itself cannot be repaired locally; the workaround is to rely on the documented behavior in the release notes and rules reference as above.

References:

• What's new in Defender for Cloud features
• Data security recommendations