A cloud-native solution that protects workloads across hybrid and multi-cloud environments with threat detection and security recommendations
Hello @MarcoBlasco-8017
Hello Marco,
Thank you for providing such a detailed investigation, including the Azure Resource Graph queries, assessment IDs, and Secure Score impact across all three subscriptions.
Based on the evidence you've shared, this appears more consistent with stale assessment data or an incomplete recommendation migration in Microsoft Defender for Cloud than with an AKS configuration issue.
The fact that all three clusters are healthy, running newer Kubernetes versions, and generating current vulnerability assessment findings through other Defender for Containers components makes a general scanning configuration problem less likely.
- Was assessment 5409cb02 retired or superseded?
According to the official Microsoft Defender for Cloud release notes, Microsoft introduced the recommendation "Upgrade Azure Kubernetes Service Version" on June 1, 2026, specifically to replace the previous non-actionable recommendation covering vulnerabilities in AKS managed system pods.
The replacement became generally available on July 1, 2026.
This supports your conclusion that the older recommendation was superseded. However, the release notes do not explicitly identify assessment 5409cb02 as the retired assessment or document its backend cleanup process.
Consequently, only the Defender for Cloud product team can confirm whether its remaining assessment records should have been removed automatically.
- Why is the Secure Score still affected?
Microsoft documentation explicitly states that preview recommendations should not contribute to Secure Score calculations.
In your environment, the legacy assessment appears in the Remediate vulnerabilities control while the newer recommendation does not.
If the older assessment is indeed classified as Preview and is still responsible for the reported 0/6 score, this warrants investigation as a possible recommendation lifecycle or Secure Score calculation issue.
The important distinction is that membership in the control's assessmentDefinitions alone does not conclusively prove that the preview findings are being included in the score calculation.
I recommend asking Microsoft to validate the assessment's effective maturity classification, the control's underlying resource calculations, and the relationship between the legacy and replacement recommendations.
- Does the November 2025 statusChangeDate confirm that scanning stopped?
Not necessarily.
The statusChangeDate property indicates when an assessment's health status last changed, not when the resource was last evaluated.
However, the presence of outdated kube-proxy image versions and findings associated with namespaces deleted in August 2026 provides stronger evidence that the legacy assessment is not reflecting the current environment.
I recommend including the associated subassessment records and their timestamps in the existing support case to help Microsoft determine whether the issue originates from the scanning pipeline, assessment lifecycle, or stale backend data.
- Is deleting the assessment through the REST API supported?
Microsoft provides an Assessments DELETE REST API. However, the existence of this endpoint does not establish that deleting Microsoft managed built in assessment results is a supported method of clearing stale recommendations.
I would strongly recommend against manually deleting assessment 5409cb02.
Even if the request succeeds, the documentation does not guarantee that the underlying assessment data will be permanently removed or that the Secure Score will be recalculated correctly.
The safest approach is to have Microsoft investigate and correct the assessment state through the supported service lifecycle.
- Recommended next steps
Since you already have support case fb1b37f8-f6e5f434-74be60bb-91b3-4f84-84a0-f81a758c3b32, I recommend requesting escalation to the Microsoft Defender for Cloud product engineering team.
Specifically, ask them to:
- Confirm whether assessment 5409cb02 has been officially deprecated and replaced by 2dfd0218.
- Investigate why legacy assessment records remain associated with AKS resources that have been upgraded or removed.
- Validate whether these stale findings are incorrectly contributing to the Remediate vulnerabilities Secure Score control.
- Confirm whether the legacy assessment records can be safely cleaned up through a supported backend process.
- Verify whether the Secure Score control definition requires updating to reflect the replacement recommendation.
As a temporary workaround, you could discuss a documented recommendation exemption with Microsoft support. However, this should only be considered after verifying its impact, since exemptions change how findings contribute to Secure Score and do not resolve the underlying stale data.
Assessments REST API:
In summary, your investigation provides substantial evidence of stale vulnerability assessment records, but confirming the legacy assessment's retirement status and correcting its Secure Score impact requires Microsoft product engineering involvement.
Given that the issue affects three subscriptions and has persisted despite active vulnerability scanning, I would recommend continuing with your existing support case rather than changing the AKS or Defender for Containers configuration.
I hope this helps! If my answer is helpful and addresses your question, please consider marking it as "Accepted Answer" so other community members facing similar issues can benefit from it.