Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Microsoft Azure Cost Optimization and improve efficiency

101 views

Published on

Cloud solutions could not be best solution if it is not chosen. One factor businesses deviates from cloud solutions is unawareness of getting best out of cloud solutions with increasing efficiency.

This presentation addresses gaps between discussion had at the global azure bootcamp New Jersey.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Microsoft Azure Cost Optimization and improve efficiency

  1. 1. Kushan Perera about.kushanperera.com
  2. 2. Kushan Lahiru Perera Principle Consultant at Independent Consultant – Cloud and Office 365 Passionate about: Enterprise Collaboration - O365/ SharePoint Cloud Services - Microsoft Azure & GCP Client Side Frameworks Microsoft MVP (Most Valuable Professional)
  3. 3. Agenda 1. Motivations to cloud? 2. Introduction to optimization 3. Techniques cloud cost optimization Demos: • Tagging • Azure Runbooks • Azure cost calculator
  4. 4. What is CLOUD (revisit)? Pay-as-You-Go Zero capital ($) to start Outsourced services – No unpredictable costs
  5. 5. Why Optimize? Utility Compute and Storage are a utility so ‘turning off’ should be natural Efficiency Efficiency allows more to be done within a given budget Architecture Cost awareness drives todays architectural decisions
  6. 6. What you will get (benefits)? Reduced Risk Cost/ Time Efficiency Availability
  7. 7. Scenario: Usage of server within a business day.
  8. 8. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad
  9. 9. Capacity of 1 Server 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad
  10. 10. Traditional capacity required Capacity of 1 Server 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad
  11. 11. Traditional capacity required Capacity of 1 Server 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad 1 Server for 8 hours
  12. 12. Traditional capacity required 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad 1 Server for 8 hours Capacity of 1 Server 1 Server for 8 hours 1 Server for 8 hours
  13. 13. Traditional capacity required 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad 1 Server for 8 hours Capacity of 1 Server 1 Server for 8 hours 1 Server for 8 hours 1 Server for 8 hours
  14. 14. Capacity of 1 Server Traditional capacity required 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Hour of day ServerLoad 1/3rd Saving
  15. 15. Azure RIs (Reserved VM Instances) Reservation of VMs in advance and get discounts • Predictive budgets • One or three year terms • Prioritized compute • Flexible cancel or exchange • Easy purchase
  16. 16. Naming and Tagging Make accountable and transparent • Resource naming convention <company> <department> <productline> <environment> Eg. softhonic services business prod • Tagging • Name value pairs assigned to resources or resource groups • Each resource could have up to 15 tags
  17. 17. Scale Right Buy only what you need Workload Workload Workload
  18. 18. Scale Right… cont Buy only what you need • Auto scale • Know your capacity • Audit • Continuous monitor
  19. 19. Decommission & Automate Pay only when you need • Auto shutdown • Logic apps • Web Jobs • Automation – Runbooks • Azure Dev Test Labs • Windows Scheduler Tasks • Etc. • Deallocate unused resources • Audit with PowerShell for unattached disks and resources • $  0
  20. 20. Azure Automation - Runblocks https://github.com/ratchetnclank/Invoke- Autoshutdown/blob/master/Invoke-Autoshutdown.ps1
  21. 21. Choose right Pay only when you need • Price deviates from resource location https://azure.microsoft.com/en-us/global-infrastructure/locations • Find best service for your requirement Go server-less when its POSSIBLE No maintenance No License Less knowledge curve
  22. 22. aka.ms/azurecalculator
  23. 23. Bring Your Own Licenses (BYOL) Use what you have • Research licenses from 3rd party • Purchase directly • If you have Visual Studio enterprise – you have licenses
  24. 24. Educate end-users Use what you have • If you scheduled to shutdown VMs at 6.00 PM • User on half day and leaves around 2.00 PM • If user shutdown at 2.00 PM, you save 4 hour compute
  25. 25. Pay as you go but keep eye on distance you go.
  26. 26. Inboxme@kushanperera.com about.kushanperera.com

×