Skip to content
ENExplore Calculators

Azure Secure Score Calculator

Model Microsoft Defender for Cloud secure score: achieved points over maximum points, with partial credit from healthy resource ratios.

About Azure Secure Score Calculator

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

Worked example

With the default values below, Azure Secure Score Calculator returns Secure Score of 64.1%. Change any input above and every figure here is recalculated in your browser.

Inputs used

Maximum secure score points availableaccepts 1–2,000 points
64 points
Points currently achievedaccepts 0–2,000 points
41 points
Security recommendations in scopeaccepts 1–5,000 recommendations
58 recommendations
Recommendations fully completedaccepts 0–5,000 recommendations
29 recommendations
Healthy assessed resourcesaccepts 0–5,000,000 resources
1,240 resources
Total assessed resourcesaccepts 1–5,000,000 resources
1,820 resources
Points on the largest open recommendationaccepts 0–200 points
10 points
Healthy resources on that recommendationaccepts 0–100 %
45 %
Target secure scoreaccepts 0–100 %
80 %

Results

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%
Points Needed to Hit Target
10.2 points
Verdict
One recommendation is worth five or more score points; finish it before starting anything else

Step by step

  1. 1Values used
  2. 2Azure Secure Score
  3. 3Marginal uplift
  4. 4Secure Score= 64.1
  5. 5Grade= C — Fair
  6. 6Points Still Available= 23.0 points
  7. 7Assessed Resource Health= 68.1
  8. 8Recommendations Completed= 50.0
  9. 9Score Uplift From the Top Recommendation= 8.59

Assumptions and limits

  • The result is derived only from the 9 inputs listed above. Anything not among them is not part of the calculation.
  • In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
  • Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

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.

Related Calculators

Azure Secure Score Calculator | Calcrivo