🛡️ Azure Reservation expired in the last 30 days🟢

• Contextual name: 🛡️ Reservation expired in the last 30 days🟢
• ID: /ce/ca/azure/reservations/reservation-expired-in-last-30-days
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: BEST_PRACTICE
• Policy Categories: COST

Logic

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

Description

Open File

Description

This policy identifies Azure Reservations that have expired within the last 30 days. It acts as a safeguard to verify that expirations were intentional and to alert teams to potential unplanned increases in cloud spending.

Rationale

Although proactively monitoring upcoming expirations is the recommended best practice, this policy provides a reactive safety net. By identifying recently expired reservations, FinOps and cloud management teams can confirm whether the expiration was intentional or the result of an oversight. This enables timely evaluation of the financial impact of resources reverting to pay-as-you-go pricing and supports corrective action if necessary.

Audit

This policy flags an Azure Reservation as INCOMPLIANT if its Expiry Date falls within the last 30 days.

The Reservation is marked as INAPPLICABLE if its Provisioning State is not equal to Expired or the Expiry Date is empty.

Remediation

Open File

Remediation

Verify whether the reservation's expiration was intentional. If not, take immediate corrective action to mitigate increased costs by purchasing a new reservation.

Using the Azure Portal

1. Acknowledge and verify intent.

   Confirm with the resource owner or finance team whether the expiration of the identified reservation was deliberate.

2. Assess cost impact.

   Use the Cost analysis tools to review spending for the resource group or subscription previously covered by the reservation.

3. Repurchase a reservation, if required.

4. Implement proactive monitoring.

   • Prevent future oversights by enabling policies that provide advance notification of reservations nearing expiration (e.g., 30, 60, or 90 days in advance).
   • Configure email alerts for reservation expirations to ensure timely action.

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Waste Reduction			28		no data