🛡️ Azure Savings Plan utilization is below 80%🟢

• Contextual name: 🛡️ Savings Plan utilization is below 80%🟢
• ID: /ce/ca/azure/savings-plan/utilization-below-threshold
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: COMPLIANCE_POLICY
• Policy Categories: COST

Stats

not available

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 Azure Savings Plan
  • 🔌 Azure Savings Plan - object.extracts.yaml
  • 🔌 Azure Savings Plan Utilization - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

This policy identifies successfully provisioned Azure Savings Plans with at least one complete utilization record below 80% in the last 40 days.

Rationale

Low utilization means part of the hourly commitment was not consumed by eligible compute usage during a recent reporting period. Persistent underutilization can indicate an oversized future commitment or a mismatch between the commitment and eligible demand.

Impact

Savings Plan commitments cannot be changed after purchase. A single historical period is evidence for review, not proof that current or future demand is too low.

Audit

The policy marks an Azure Savings Plan as INCOMPLIANT when its Provisioning State is Succeeded and at least one related Azure Savings Plan Utilization record has a Usage Date within the last 40 days and Utilization Percentage, Avg below 80%.

A plan with a missing provisioning state is UNDETERMINED. A successfully provisioned plan is also UNDETERMINED when a related utilization record has no Usage Date, a record within the last 40 days has no

... see more

Remediation

Open File

Remediation

1. In the Azure portal, open Cost Management + Billing, select Savings plans, and open the affected plan.
2. Review Utilization for each period below 80% and compare several periods to determine whether the shortfall is persistent.
3. Confirm that the plan's benefit scope contains sufficient eligible compute usage. Account for seasonal demand, outages, migrations, and overlapping Reservations or Savings Plans.
4. Where permitted by current Azure rules, align the benefit scope with accounts, subscriptions, or resource groups that have suitable eligible usage.
5. Because an active Savings Plan's hourly commitment cannot be reduced, use the observed demand to set a lower hourly commitment or a better scope for future purchases.

Validate proposed changes with the workload owner and FinOps team. Do not change future coverage based on a single low-utilization period.

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Resource Optimization			37		no data