Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
FinOps Handbook for Microsoft Azure

You're reading from   FinOps Handbook for Microsoft Azure Empowering teams to optimize their Azure cloud spend with FinOps best practices

Arrow left icon
Product type Paperback
Published in May 2023
Publisher Packt
ISBN-13 9781801810166
Length 256 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Maulik Soni Maulik Soni
Author Profile Icon Maulik Soni
Maulik Soni
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Part 1: Inform
2. Chapter 1: Bringing Visibility and Allocating Cost FREE CHAPTER 3. Chapter 2: Benchmarking Current Spend and Establishing Budgets 4. Chapter 3: Forecasting the Future Spend 5. Chapter 4: Case Study – Beginning the Azure FinOps Journey 6. Part 2: Optimize
7. Chapter 5: Hitting the Goals for Usage Optimization 8. Chapter 6: Rate Optimization with Discounts and Reservations 9. Chapter 7: Leveraging Optimization Strategies 10. Chapter 8: Case Study - Realize Savings and Apply Optimizations 11. Part 3: Operate
12. Chapter 9: Building a FinOps Culture 13. Chapter 10: Allocating Costs for Containers 14. Chapter 11: Metric-Driven Cost Optimization 15. Chapter 12: Developing Metrics for Unit Economics 16. Chapter 13: Case Study – Implementing Metric-Driven Cost Optimization and Unit Economics 17. Index 18. Other Books You May Enjoy

The on-demand and elastic nature of Azure

Azure is designed to scale. Workloads on Azure can easily scale up or down and scale out or in depending on demand. When coming from a data center mindset, where compute, storage, and networking capacity are preallocated and rarely changed, the cloud is a totally different ball game. Azure is all about pay-as-you-consume. If you don’t consume, you don’t have to pay. And this principle can be used to our advantage.

When you think of deploying a workload to Azure, start small. There is no need to pre-provision peak capacity when you can simply auto-scale based on metrics such as CPU, memory, or queue length. Also, consider shutting down development and test environment resources on weekends or holidays based on usage patterns. In this way, you can entirely avoid the cost associated with those resources.

All of this is possible only when you develop sensible KPIs and business metrics. Let’s look at how we can achieve...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image