I love social media and all the channels I follow. So also this topic came into my view out of a LinkedIn post of David das Neves. I had a look into it … and thought I should share it here. Microsoft Learning on GitHub Did you know that there is a number of repositories…
We arrived at the last part of the series about Azure Reservations. After we had looked into changes and cancellations in our last article it is time for a conlsuion
- Part 1 – ARS 1/6 – Azure Reservations Series – Intro
- Part 2 – ARS 2/6 – Azure Reservations Basics
- Part 3 – ARS 3/6 – Azure Reservations Purchasing
- Part 4 – ARS 4/6 – Azure Reservations Settlement
- Part 5 – ARS 5/6 – Azure Reservations Changes
Reserved instances are a great way to save costs in Azure and run long term resources at low cost. The flexible crediting based on the use of resources also allows you to use added value if individual resources are not operated around the clock, as other resources simply benefit from the reservation.
However, some planning is needed. On the one hand the correct reservation must be found. A calculation of the savings is particularly time-consuming at Cosmos DB and SUSE due to the different ratios.
The cancellation fee and the maximum refund of $50,000 must be observed.
All around…with some planning and knowledge of the possibilities and conditions…a great possibility to increase the added value of Cloud even further.
Dieser Post ist auch verfügbar auf: German