Reason 1: Native Reservations Already Covering Storage Spend
The customer already has native reservations covering this storage or backup spend. Check their commitment inventory first before moving to the next reason.
Reason 2: Insufficient Storage Spend
The customer's storage or backup spend is not enough for the recommender to surface commitments. The minimum capacity to procure a reservation for storage or backup is 100TB.
You can find the customer's storage spend in Infrastructure Inventory and calculate the GB/hr metric over a 30-day timeframe to arrive at their rough monthly usage.
The 100TB minimum is applicable to a particular tier (Hot, Cool). You cannot aggregate 60TB of Hot and 40TB of Cool in order to procure a 100TB Azure backup reservation.
The 100TB minimum is applicable to a particular redundancy type.
Last updated
Was this helpful?
Was this helpful?
