Defender for Cloud secure score shows N/A for all subscriptions – secureScores API returns 0/0 although MCSB is assigned

Sundar kannan 0 Reputation points
2026-11-18T02:04:44.6933333+00:00

Hi,

The classic secure score in Microsoft Defender for Cloud (Azure portal) has started showing N/A for all subscriptions in our tenant. It was showing a score until last week; we have not changed the Defender plans or the security policy.

What we see:

  • Defender for Cloud > Overview > Security posture: the total secure score shows 46%, but every subscription in the list shows Secure score = N/A (production, management and connectivity subscriptions).
  • Recommendations are still being assessed – for example, the production subscription shows 3 of 47 unhealthy resources, and recommendation status updates normally.

What we have checked:

  1. The Microsoft cloud security benchmark is assigned to the subscription: assignment "SecurityCenterBuiltIn" (ASC Default), enforcement mode Default, and it shows On under Environment settings > Security policies.
  2. Secure Scores API: GET /subscriptions/{subscriptionId}/providers/Microsoft.Security/secureScores?api-version=2020-01-01 returns ascScore with current = 0, max = 0, percentage = 0.
  3. Secure Score Controls API: GET /subscriptions/{subscriptionId}/providers/Microsoft.Security/secureScoreControls?api-version=2020-01-01&$expand=definition returns all 13 controls (Apply system updates, Enable encryption at rest, Remediate security configurations, etc.) but each one has score 0 / max 0 with 0 healthy and 0 unhealthy resources – even though many recommendations in those controls are Healthy.
  4. One call to the Microsoft.Security provider returned: Bad Gateway – {"error":{"code":"InvalidGatewayCertificate","message":"The gateway certificate is invalid for 'Microsoft.Security'."}}
  5. There is no active incident for Defender for Cloud in Service Health.

Questions:

  1. Is this a known issue with the secure score calculation, or a side effect of the new Cloud Secure Score (risk-based) in the Microsoft Defender portal?
  2. Is there anything we can do on our side to trigger a recalculation of the classic secure score?
  3. If this is a backend issue, can a Microsoft moderator escalate it? We only have a Basic support plan, so we are unable to raise a technical support ticket.

This is time-sensitive for us because we need the secure score as evidence for a review next week.

Thanks in advance.secure score.png

Azure Policy
Azure Policy

An Azure service that is used to implement corporate governance and standards at scale for Azure resources.

0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-18T02:06:16.78+00:00

    The classic score recalculates automatically every eight hours and has no documented customer-triggered refresh, so a week-long tenant-wide 0/0 result should be preserved as evidence and escalated as a probable service-side data issue rather than addressed by reassigning MCSB.

    What the results indicate

    • The 46% aggregate score and per-subscription N/A values can coexist because the aggregate is a weighted calculation, not an average of the subscription percentages.
    • A control is excluded when it has no healthy or unhealthy assessments. If every control reports zero healthy, zero unhealthy, and zero maximum points, there is no denominator from which Defender for Cloud can calculate the subscription score. This explains N/A, but not why the assessment-to-score data disappeared.
    • Recommendations can update before their corresponding controls. Microsoft documents that controls are calculated every eight hours, while recommendations update more frequently. A temporary discrepancy is therefore expected, but persistence since last week is outside the normal calculation interval.^1^

    The InvalidGatewayCertificate response is additional evidence of a Microsoft.Security request-path failure. One occurrence does not establish the root cause, but include its timestamp, correlation/request ID, region, and full response headers in any escalation.

    Relationship to risk-based Cloud Secure Score

    The new risk-based Cloud Secure Score is not a replacement calculation feeding the classic score:

    • Classic Secure Score remains in the Azure portal.
    • Risk-based Cloud Secure Score is in the Microsoft Defender portal.
    • They are separate models with different calculations and values.^1^

    The transition from grouped to individual recommendations can produce inconsistencies in classic controls, such as an unhealthy control whose underlying grouped recommendation is no longer visible. Microsoft recommends using Risk view to investigate those findings.^2^

    However, that documented transition behavior does not specifically account for every subscription and all 13 controls simultaneously returning 0/0. Microsoft’s release notes also state that individual recommendations were intended to keep the classic score functionally stable rather than cause a material loss of scoring data.^3^

    There is public evidence of similar N/A/no-data reports, but no official November 2026 advisory in the available release notes that identifies this exact tenant-wide ascScore = 0/0 condition.^4^

    Actions to take now

    1. Do not remove and reassign SecurityCenterBuiltIn.
      MCSB is already enabled and assessments are still updating, so that would not target the failed score aggregation path.
    2. Capture one reproducible sample from each affected subscription:
      • UTC request time.
      • Subscription display name; redact subscription IDs in public posts.
      • secureScores response showing current, max, and percentage.
      • secureScoreControls response showing the zero resource counts.
      • Response headers containing request/correlation IDs.
      • Screenshot of Defender for Cloud → Security posture.
      • Screenshot or export showing that current MCSB recommendations contain healthy/unhealthy resources.
      • The InvalidGatewayCertificate response and its request ID.
    3. Check Service Health history, not only active incidents.
      In Azure portal, open Service Health → Health history and filter for Microsoft Defender for Cloud/Microsoft.Security and the affected subscriptions. Resolved service issues remain visible for 90 days.^5^
    4. Record both score models separately for the review:
      • Azure portal: label it Classic Secure Score, record the aggregate 46%, timestamp, scope, and per-subscription N/A condition.
      • Microsoft Defender portal: label it Risk-based Cloud Secure Score and record it separately.
      • Export the recommendation status and MCSB assignment as supporting posture evidence. Do not present the risk-based score as a replacement value for the classic model.

    Escalation with Basic support

    Azure Basic does not include technical break/fix support; technical cases require an eligible support plan.^6^

    A Q&A moderator can flag a report or seek product-team attention, but a Q&A post is not a support ticket and cannot guarantee tenant-specific backend investigation. Update the Q&A case with the sanitized evidence above and request confirmation of whether an active Microsoft.Security score-pipeline issue exists.

    Also check whether your organization has an Enterprise Agreement, Unified/Premier agreement, Visual Studio support benefit, Cloud Solution Provider, or partner-managed subscription. If so, ask its support administrator or provider to open the technical case. If support entitlement is expected but unavailable, the documented path is to have the tenant administrator or support-agreement owner verify access and entitlement.^7^


    References

    1. Cloud Secure Score in Microsoft Defender for Cloud - Microsoft Defender for Cloud | Microsoft Learn
    2. Transition from grouped to individual recommendations in Defender for Cloud
    3. What's new in Defender for Cloud features
    4. Classic Recommendations view shows no data (Secure score N/A, 0 recommendations) in Microsoft Defender for Cloud. - Microsoft Q&A
    5. Service issues
    6. Create an Azure support request
    7. Microsoft Cloud Portals: Self-Help When a Support Request Cannot Be Opened
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.