Skip to main content

๐Ÿ›ก๏ธ Azure Savings Plan expired in the last 30 days๐ŸŸข

  • Contextual name: ๐Ÿ›ก๏ธ Savings Plan expired in the last 30 days๐ŸŸข
  • ID: /ce/ca/azure/savings-plan/expired-in-last-30-days
  • Tags:
  • Policy Type: COMPLIANCE_POLICY
  • Policy Categories: COST

Statsโ€‹

not available

Logicโ€‹

Descriptionโ€‹

Open File

Descriptionโ€‹

Review Azure Savings Plans that expired during the previous 30 days to confirm that the expiration was intentional and that the covered compute usage has an appropriate pricing commitment.

Rationaleโ€‹

Azure Savings Plans provide discounted pricing in exchange for a commitment to an hourly spend on eligible compute services. When a plan expires, eligible usage reverts to pay-as-you-go pricing unless another commitment applies. Reviewing recent expirations helps FinOps and workload owners identify missed renewals and decide whether replacement coverage remains cost effective.

Impactโ€‹

An unintended expiration can increase compute costs and reduce forecast accuracy. Purchasing a replacement without reviewing current usage, scope, and term can instead create unused commitment. This policy does not recommend an automatic purchase; each result requires an owner review.

Auditโ€‹

The policy marks an Azure Savings Plan as INCOMPLIANT when its Provisioning State is Succeeded, its Expiry Date Time is before the current UTC day, and that date falls within the preceding 30 days.

... see more

Remediationโ€‹

Open File

Remediationโ€‹

  1. Confirm with the workload owner and FinOps team that the Savings Plan expiration was intentional.
  2. In the Azure portal, open Cost Management + Billing and select Savings plans to review the expired plan, eligible usage, and cost impact.
  3. Compare current eligible compute demand, the intended scope, term, and hourly commitment with the available pricing options.
  4. If replacement coverage is justified, purchase a new Savings Plan with the approved scope and commitment. Azure Savings Plans are not renewed in place.
  5. Configure advance-expiry monitoring and assign an owner so the commitment can be reviewed before its next expiry date.

policy.yamlโ€‹

Open File

Linked Framework Sectionsโ€‹

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
๐Ÿ’ผ Cloudaware Framework โ†’ ๐Ÿ’ผ Resource Optimization37no data