Stop the spill, get in control of your Azure bill!

Transcript

1. Stop the spill, get in control of your Azure bill! Kees Schollaart | Microsoft
2. Stop the spill, get in control of your Azure bill! Kees Schollaart | Microsoft
4. Kees, don’t you have a target?
5. Show of hands… Who has an Azure subscription attached to their private CC?
6. Pay as you Go
7. Pay as you Go
8. Pay as you Go
10. Our agenda, 5x5 1. 5 Anti patterns 2. 5 Tools to get better insights 3. 5 Cultural things 4. 5 Discounts 5. 5 Actions for tomorrow
11. Chapter 1 5 Tips: how to Sponsor Microsoft? 5 Tips: How to cause Azure cost spill?
12. How to cause Azure cost spill? Tip 1 of 5: Lift & Shift your VM’s and run away!
13. How to cause Azure cost spill? Tip 2 of 5: A full-blown Acceptance Environment… Used 30 minutes every month
14. How to cause Azure cost spill? Tip 3 of 5: Use Azure Database for *everything*
15. How to cause Azure cost spill? Tip 4 of 5: Create a mess of your Azure Environment
16. How to cause Azure cost spill? Tip 5 of 5: Test AKS, then forget to kill your cluster… …and discover it after 4 weeks
17. Chapter 2 5 Tools to get better insights
18. 1: For our CSP friends.. • You are not talking ‘money’ with Microsoft… • Azure Cost Insights won’t work • azure-costs.com • And other 3th party solutions (provided by your CSP provider)
19. 2: Azure Cost Insights - Per subscription - Cost Alerts - Budgets - Advisor recommendations
27. 3: EA Portal - Departments - Over subscriptions
30. 4: Power BI (for EA) - Built-in connector - Ready to use dashboards
32. Insights 2.0 • Make them scoped to Team, Product or … • Scoped insights… • Are less boring to look at • Affect behavior • Cause responsibility • Interesting to all roles
33. 5: Cost Insights for Azure DevOps - Insights over subscriptions - All roles involved - Daily push of insights
34. Insights, recap - Garbage in is garbage out - Use tags - Name your resources properly - More Resource Groups & Subscriptions is more data* - Push insights don’t expect people to pull this type of data - Frequently confront teams with their spendings
35. Chapter 3 5 Cultural things
36. Agree upon a scale unit and measure it. For example: ‘Number of Users’ or ‘Number of Orders Processed’
37. Don’t fall asleep in your datacenter keep up with the pace of innovation and move forward from old VM SKU’s, Azure Cloud Services etc.
38. What is the business case? Developers are not cheap!
39. A 1-time ‘cost savings’-project or a consultant to the rescue? Be careful!
40. Cost cannot be an afterthought That is like adding unit-tests afterwards
41. Chapter 4 5 Discounts you should know
42. Don’t ignore the discount, must know 1 of 5: Dev/Test VM’s
43. Don’t ignore the discount, must know 2 of 5: B-Series VM’s
44. Don’t ignore the discount, must know 3 of 5: Low priority VM’s
45. Don’t ignore the discount, must know 4 of 5: BYOL
46. Don’t ignore the discount, must know 5 of 5: Reserved Instances
47. Free is less than cheap! ☺
48. Chapter 5 5 Actions for tomorrow 10
49. Get on top of your Azure infrastructure ‘database’ Naming conventions, tags and policies to the rescue!
50. Leverage the AppService Plan features Sharing plans, High Density hosting and Consumption Plan
51. Scale- and shutdown your pre-production resources automatically
52. CaaS vs PaaS There is VM overhead in a cloud agnostic (container) architecture
53. Become in infrastructure And create disposable load/integration-test environments in your CI/CD pipelines
54. 5 Leftover FAQ’s: should I…? 1. Use the Azure Pricing calculator? 2. Send a monthly mail to everyone@costoso.com? 3. Go to AWS? 4. Use the API’s myself? 5. RTFM?
55. Takeaway 1 of 3: Costs are like technical debt, staying ahead of misery requires constant effort
56. Takeaway 2 of 3: Frequently confront the team with cost insights, tailored to their product(s)
57. Takeaway 3 of 3: Treat you Azure infrastructure as a database, garbage in == garbage out
58. Slides aka.ms/StopTheSpill My LinkedIn aka.ms/kees Thank you!  You’ll be fine!