The 3 Dimensions of Cost Management in Azure
By Mike Benkovich on August 25, 2021
As companies and organizations move to take advantage of the cloud, one of the first objectives should be understanding the costs and how to optimize them.
Microsoft Azure offers a number of tools that give you visibility into your Azure environment, so that you can understand what's being used, and ultimately control and optimize your spend. In this post, I'll share some of these tools available in the Azure Management Portal and how to set them up so you can prevent surprises and make the most of your investment.
The three dimensions I'll explore are Visibility, Control and Optimization.
Understanding costs begins with visibility into what's going on. The Azure Management Portal includes several tools that surface when you view your subscription in Azure. The default overview of a subscription includes charts and metrics that give you an idea of your current spend and projections of what the monthly costs will be, as well as details around the number and types of services provisioned in the subscription. Easy navigation allows you to drill deeper into questions, and makes it simple to find answers about costs.
Going from the Overview to the Cost Analysis view of the subscription opens a graph of the costs along with detailed charts on the specific services, locations and resource group charges, letting you break down and see how much each of those elements impacts your final bill. One of the nice features of the main chart is that you can change the scope of which subscriptions or resources you want to include in the analysis, as well as the dates. There also are a number of views you can switch to, with the default accumulated costs providing the forecast. Other views include cost by resource or by service, daily costs, and invoice details.
The ability to change the view, the timeframe and the scope of the query creates custom views that you can then save and share with the rest of your team. You can share the view with others, for those members of the team who are interested in seeing the costs, and also schedule downloads for distribution by going to the settings, selecting downloads and creating a scheduled export.
Control with Budgets
Setting up budgets is a way to be notified when your spend exceeds what you planned. Working with budgets in the portal is straightforward, where the portal provides suggested values for amounts, based on actual costs, and then allows you to designate who is notified when it reaches a set limit of either the projected or the actual costs.
Once a budget has been set up, you can add cost alerts for different parties. There is a filter option that includes the ability to use tags on services to provide chargeback capability if you're using tags in your governance model.
Optimizing Costs with Azure Advisor
Azure provides great feedback and recommendations for using your Azure resources. The Azure Advisor service analyzes usage and loads to understand how your workload runs and what is required to make it better. For example, the advisor will look for over-provisioned but under-used resources, as well as VM's that could be right-sized. The recommendations can be downloaded as a one-time report, or subscribed to on a periodic basis.
Optimizing for KnowledgeLake
Understanding workloads is key to managing costs. When running KnowledgeLake with the Azure storage configuration, the key is to set up and configure storage services so that you have enough capacity to support the expected load while minimizing additional costs. There are two services used by KnowledgeLake with Azure: Cosmos DB and Azure Blob Storage.
Cosmos DB is a globally distributed, multi-model database service that is used to manage metadata about documents that are ingested. It uses the Mongo-API and stores information per document to support the search and indexing capabilities of KnowledgeLake. Cosmos can be configured to use either the provisioned throughput, which guarantees a level of performance, or serverless, where you pay only for what you use. The drawback of serverless is that it currently doesn't support more than one region and has a storage limit of 50 GB. Depending on your requirements, this may likely work for you, but you need to be aware of that.
Azure Blob Storage is used to archive the actual documents and provides redundancy and availability by design. The configuration of Storage needs to be such that it is at least v2 Storage. It doesn't require global replication (GRS), but can work with local replication (LRS). What this means is that within the Azure datacenter, the data is stored at least three times across a redundant storage model.
Understanding workload requirements is key to optimizing how you can best configure resources and manage costs. Using the tools built into Azure makes it easier to understand and manage costs.
KnowledgeLake provides content management solutions that help busy organizations intelligently automate their most important document processes. Since 1999, we've created award-winning, Microsoft-centric solutions that have helped thousands of companies around the world focus on their mission rather than their mission-critical documents.
Latest from the KnowledgeLake Blog
Nine Reasons Your ECM System Belongs in the Cloud
5 Considerations to Drive Microsoft Azure Adoption Success
Stay in Touch
Receive the latest blogs from KnowledgeLake in your inbox!