Azure Secure Score Calculator
Model Microsoft Defender for Cloud secure score: achieved points over maximum points, with partial credit from healthy resource ratios.
Inputs
Secure Score
64.1%
Grade
C — Fair
Points Still Available
23.0points
Assessed Resource Health
68.1%
Recommendations Completed
50.0%
Score Uplift From the Top Recommendation
8.59%
Points Needed to Hit Target
10.2points
Verdict
One recommendation is worth five or more score points; finish it before starting anything else
Step by step
Values used
Maximum secure score points available = 64 points; Points currently achieved = 41 points; Security recommendations in scope = 58 recommendations; Recommendations fully completed = 29 recommendations; Healthy assessed resources = 1,240 resources; Total assessed resources = 1,820 resources; Points on the largest open recommendation = 10 points; Healthy resources on that recommendation = 45 %; Target secure score = 80 %
Azure Secure Score
Secure score = achieved points ÷ maximum points × 100. Each recommendation awards its points in proportion to healthy resources, so partial completion earns partial credit.
Marginal uplift
Uplift from one recommendation = (its points − its points × healthy share) ÷ maximum points × 100 — the score you gain by finishing it.
Secure Score
= 64.1
Grade
= C — Fair
Points Still Available
= 23.0 points
Assessed Resource Health
= 68.1
Recommendations Completed
= 50.0
Score Uplift From the Top Recommendation
= 8.59
How it works
Microsoft awards each recommendation a maximum score, typically 1 to 10 points, and grants it pro rata to the share of in-scope resources that are healthy. That makes secure score a resource-weighted measure rather than a checklist, and it is why fixing one recommendation across four hundred VMs moves the number far more than fixing four recommendations on one VM. Secure score drives Azure security budgets and reporting, and prioritising by points per recommendation rather than by alert count is usually a two-to-three-fold difference in score movement for the same effort.
Formulas
Azure Secure Score
Secure score = achieved points ÷ maximum points × 100. Each recommendation awards its points in proportion to healthy resources, so partial completion earns partial credit.
- achievedPoints
- Sum of partial and full credit across recommendations
- maxPoints
- Total points offered by the recommendations in scope
- resourceHealth
- Healthy assessed resources ÷ all assessed resources × 100
Marginal uplift
Uplift from one recommendation = (its points − its points × healthy share) ÷ maximum points × 100 — the score you gain by finishing it.
- topEarned
- Points already earned on that recommendation through partial credit
- topRecommendationUplift
- Percentage points the score gains on completion
Frequently Asked Questions
How is Azure Secure Score calculated?
Secure score = achieved points ÷ maximum points × 100. Each recommendation awards its points in proportion to healthy resources, so partial completion earns partial credit. Microsoft awards each recommendation a maximum score, typically 1 to 10 points, and grants it pro rata to the share of in-scope resources that are healthy. That makes secure score a resource-weighted measure rather than a checklist, and it is why fixing one recommendation across four hundred VMs moves the number far more than fixing four recommendations on one VM.
Why does Azure Secure Score matter?
Secure score drives Azure security budgets and reporting, and prioritising by points per recommendation rather than by alert count is usually a two-to-three-fold difference in score movement for the same effort.
What values do I need to enter?
This calculator takes 9 inputs: Maximum secure score points available, Points currently achieved, Security recommendations in scope, Recommendations fully completed, Healthy assessed resources, Total assessed resources, Points on the largest open recommendation, Healthy resources on that recommendation, Target secure score. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Why did my score drop without me changing anything?
Almost always new resources or a new recommendation. Deploying twenty VMs without endpoint protection reduces the healthy share on an existing recommendation, and Microsoft periodically adds recommendations, which raises the maximum points. The score is a moving denominator, so track the trend rather than the absolute.
Should I chase the highest-point recommendations first?
Chase the highest available uplift, which is points multiplied by the unhealthy share. A 10-point recommendation already 90% healthy offers 1 point; a 4-point one at 10% healthy offers 3.6. This calculator computes exactly that figure for the recommendation you enter.
You might also need
- Cloud Security Health Score CalculatorCommonly used together
- Security Hub Score CalculatorCommonly used together
- GCP Security Command Center CalculatorCommonly used together
- Cloud IAM Risk CalculatorAlso in Cloud Security
- Cloud Compliance CalculatorAlso in Cloud Security
- Cloud Misconfiguration CalculatorAlso in Cloud Security