ARS 5/6 – Azure Reservations Changes
4. March 2019
In the last part we have looked at how Azure Reservations are offset against actual usage.
Reservations – Everything goes according to plan?!
But now it should happen from time to time that one is wrong. The planned project does not need so many servers. The solution is used much more and the database needs more performance.
Anyway…it can happen that reservations have to be adjusted or even have to be cancelled completely.
There are a few things to keep in mind:
Changes to reservations
There are ways to change existing reservations. For example, the region, scope and also the size of the reservation can be changed. If a larger reservation is required, only the difference to the new reservation must be paid. The reservation period starts again with the exchange. Only reservations with the same or higher level can be exchanged. A “downgrade” is not possible.
The change of a SUSE Linux reservation is not possible!
Cancellation of reservations
Basically it is also possible to “return” a reservation and cancel it. However, there are two important things to keep in mind.
On the one hand, Microsoft retains a 12% “Cancellation Fee”. So a penalty for early termination of the reservation.
In addition, a maximum of $50,000 refund is possible per year. So it is not advisable to make more than $50,000 reservations that are not safely used.
The refund always refers to the residual value of the reservation.
The return of SUSE Linux reservations is not possible!
In the next part, we’ll look at how it behaves with changes to reservations.
Next Part (tomorrow): ARS 6/6 – Azure Reservations Conclusion
This article is based on my current knowledge as of February 2019. All information is subject to change without notice…especially as the rules of the game may change at any time and there is a possibility that I have misunderstood or overlooked something … If this is the case, I would be happy if you add it to the comments.
Dieser Post ist auch verfügbar auf:
Leave a comment