Book Image

The Road to Azure Cost Governance

By : Paola E. Annis, Giuliano Caglio
Book Image

The Road to Azure Cost Governance

By: Paola E. Annis, Giuliano Caglio

Overview of this book

Cloud teams and ICT cost controllers working with Azure will be able to put their knowledge to work with this practical guide, introducing a process model for structured cost governance. The Road to Azure Cost Governance is a must-read if you find yourself facing the harsh reality of monthly cloud costs gradually getting out of control. Starting with how resources are created and managed, everything you need to know in order to track, display, optimize, rightsize, and clean up cloud resources will be tackled with a workflow approach that will leave the choice of operation to you (be it the Azure CLI, automation, logic apps, or even custom code). Using real-world datasets, you'll learn everything from basic cost management to modeling your cloud spend across your technical resources in a sustainable way. The book will also show you how to create a recursive optimization process that will give you full control of spending and savings, while helping you reserve budget for future cloud projects and innovation. By the end of this Azure book, you'll have a clear understanding and control of your cloud spend along with knowledge of a number of cost-saving techniques used by companies around the world, application optimization patterns, and the carbon impact of your cloud infrastructure.
Table of Contents (14 chapters)
Section 1: Cloud Cost Management
Section 2: Cloud Cost Savings
Section 3: Cost- and Carbon-Aware Cloud Architectures

Defining cost constraints

We now need to apply what we have learned to our company's organization, for costs to be clear and split across all departments and for technical constraints to be correctly implemented and configured for our cost governance model.

Depending on your cloud usage and how your organization works, you must create a conceptual map on how a chargeback (albeit theoretical) should work for each cloud service. If your organization is made up of many separate departments, each holding its own authority over cloud costs, these suggestions will still work, although you might have to duplicate all your efforts.

For example, in a company where a central information technology (IT) department is providing services to other departments, these could be the criteria:

  • Application usage:
    • Each application has a unique and dedicated set of cloud services that can be charged back to users (one-to-one relationship app/department/cost), as illustrated in the following...