Azure Cost Management Reviews

In terms of Microsoft Azure products, it all depends on the project need. I evaluated Azure Synapse Analytics but found Azure Databricks more suitable. So in the current project, I'm using Azure Databricks and Azure Cost Management, Monitor, Kubernetes, Azure Kubernetes. They are part of the solution.

Azure Cost Management does not require any deployment. It is more a service to evaluate or understand the cost before we use any service—a monitor. So at the time of solutioning, we estimate or try to calculate the operational cost and the Capex cost. That means Azure Cost Management is more a service used to understand what the cost impact could be when implementing X or Y or Z solutions or Z services of Azure.

In Azure Cost Management, we utilize metrics to optimize resource allocation; we extract reports to understand which service is consuming the most cost and target the top five or top ten, then try to understand why they are consuming so much cost and see if some optimization can be done—we try to do that.

A strong point of Azure Cost Management is that budget setting is possible. We can set an upper limit, a budget range, on our services.

I do use Azure Cost Management's forecasting feature.

Assessing the effectiveness of cost alerts in preventing unexpected expenses, that feature is usable. The alerts are useful—they help us stay within the limits or budget set for that week or month or the day ranges.

There are areas in Azure Cost Management that could be improved; sometimes, as a start user or junior developer, if I try to understand which service consumed how much cost and look at different charts in the dashboards, it's difficult to understand which chart is representing what. Those interfaces could be made simpler.

I'm not much into analytics patterns, so Azure Cost Management's Cost Analytics feature hasn't particularly helped my organization understand spending patterns.

I have been working with Azure Cost Management for almost eight, nine years now.

The experience so far with Microsoft technical support has been excellent. I would rate it almost five out of five.

If I could rate Microsoft technical support out of 10, it would be 4.9, 4.95, 5 almost—around 9.8 or 9.9, somewhere close to 10.

Positive

Azure Cost Management has improved my cloud expense management.

Azure Cost Management did bring some benefit for my organization.

In terms of pricing, it may be a perception that Azure Cost Management is more expensive compared to other solutions, but it's been more than two years since I made a comparison. Generally, we receive requests from clients about which cloud they want to use, and that is usually already decided. Cost comparison is generally not part of the activities I do, but my perception is that Azure is the cheapest.

In terms of budgeting processes, a solution should be long lasting and work for another 10 years. That's how we capture the information from Azure Cost Management, do our analysis, and try to understand the impact, the volume of data, kinds of users, regions. Cost Management is a prime key input factor for proposing the right solution.

The stat regarding metrics, showing how much of my budget I can save using Azure Cost Management, is not available with me.

On a scale of 1-10, I rate Azure Cost Management a 9.5.

I use Azure Cost Management to monitor and keep track of the utilization of different resources in Azure.

Azure Cost Management has a positive impact since it provides insight into the utilization of different resources in Azure, helping us predict expenses in quarterly or yearly intervals.

Continuous monitoring helps me detect anomalies in the pipeline, preplan resource scalability, and assist with cost management by offering good visibility into resource utilization. It also offers predictive analytics and some existing features, including dashboards. The AI prediction feature helps forecast based on current utilization trends and suggests improvements like the GenAI feature for interactive inquiries.

Azure Cost Management is a little complicated, and the learning curve is somewhat steep. An enhancement recommendation I have would be to provide more real-time updates about costs.

I have been providing services for this solution for around three years, maybe more or less.

I find Azure Cost Management to be very stable with a rating of nine out of ten.

Scalability may not be directly relevant to Azure Cost Management because whenever another resource is created, it automatically gets tagged to the management system. However, having near real-time updates about costs would enhance scalability insights.

Support for Azure Cost Management is excellent with no issues or delays in response. I rate customer service at nine out of ten.

Positive

I previously worked with AWS Cost Management. My switch to Azure Cost Management was due to a shift in project requirements and the opportunity to develop new skills.

The initial setup is straightforward, especially if it's a simple implementation. However, for enterprise-level projects, Azure Cost Management is necessary.

The implementation is handled in-house with a minimum of five engineers involved.

Azure Cost Management has a positive impact on ROI. It provides a clear understanding of resource utilization and helps predict expenses in a structured manner.

The pricing is cost-effective, and I have not encountered any extra expenses attached after purchasing the service.

I wanted to compare solutions due to a client's interest in migrating from Matillion to ADF.

Azure Cost Management should be implemented, particularly for enterprise-level setups. 

Overall, I would rate the solution nine out of ten.

Positive

I use Azure Cost Management indirectly from Snowflake. Not all of the Azure stack is utilized, only some of it for the future.

Azure Cost Management has valuable native features.

It is already built-in, which allows me to track costs effectively through FinOps capabilities.

I have been using this solution for one year.

I have not experienced any stability issues.

I have experienced scalability issues.

Azure Cost Management can be priced high.

In my company, we are overall on your Azure, so we have our own Microsoft Azure. Our organization has a deployment into Azure itself, and we have the entire process set up on Azure. We are also using different products from Microsoft. I think, basically, it has been my company's cloud investment for a very long time.

The most beneficial features for me are the tool's visualization capabilities, the way the reports are presented, and the fact that we can also implement our governance policies. I think we can create the budget in the tool for our company and look into the different best practices across different places, which are all pretty good for us. I think for sure that the team would be utilizing it for different purposes, but for me, at a leadership level, the visualization part is really good and helpful.

In our company, we recently started using the tool, so I don't know what options it provides to actually scale up. I think it is too soon to basically provide feedback about the tool. So far, Azure Cost Management has been helping our company with the accountability we need for our hosting costs and other cost management.

The maintenance of the product by Azure's support team is an area with certain shortcomings where improvements are required.

I have been using Azure Cost Management for a year. My company has a partnership with Microsoft.

My company started using the tool's services recently. Stability-wise, I rate the solution an eight out of ten.

It is a pretty scalable solution, which is one of the reasons my company decided to go for Azure. Scalability-wise, I rate the solution an eight or nine out of ten.

Most of the people in my company are on Azure, and then we use it for our deployments, so our development team works on it. Around four to five people use Azure Cost Management.

Microsoft's technical team responded that the maintenance schedule was random and not planned. The aforementioned area consists of my company's biggest challenges with the tool. We tried escalating our company issues with the tool's support team many times, but it has nothing to do with Azure Cost Management. It has good documentation support, but it is not that good in terms of technical support.

I rate the support a five out of ten.

Neutral

My DevOps team was taking care of the tool's deployment. I heard no complaints about the tool, and it was pretty good at anomaly detection as well. I think my company was getting good returns on cloud costs and other stuff from one place.

The solution is deployed on the public cloud.

I have no idea about the time it took to deploy the tool because a team handling its deployment process was assigned all the deployment-related tasks. I understand the value the tool brought to our company, as it helped us save on costs.

Overall, in terms of hosting costs, my company reduced costs by 10 to 15 percent, as per the last quarter's report. The aforementioned results are from when my company first implemented the tool, so I am sure if I talked to my DevOps department, it would be around the same range as mentioned. We are not a big organization, so we, either way, are not spending that much. So, somewhere in terms of value savings or cost savings, we are able to cut down by 15 percent.

The product has helped save costs for the company. I rate the ROI as a nine or ten out of ten.

In terms of the benefits for our company's operations from the cost alerts provided by the tool, I would say that cloud optimization was just one of the initiatives that I took up as an engineering director. The tool might have different features, but I think one of its greatest things is its good documentation, which our company can implement very quickly.

I have not tried the tool's AI part so far because I think we are very specific with our AI policy in our company, so we haven't given any AI too much of a chance yet to actually contribute to the practices that we are doing, but I think it will happen in the future or next quarter.

Maintenance is mostly done automatically, but even if we require something, then there is a team that takes care of the regular maintenance and updates that we have to do.

I rate the tool as seven out of ten.

We use several services and use the product to understand the cost. 

We use Azure DevOps, and the product helps us understand the cost with the help of the Azure DevOps center. 

Azure Cost Management is expensive. 

I have been using the product for a couple of months. 

I rate the product's stability a ten out of ten. 

Azure Cost Management is scalable. My company has 100 users. 

The tool's technical support is excellent and depends on the severity. 

Azure Cost Management's deployment is easy and quick. 

We have in-house experts to do the deployment. 

The tool helps with price governance. 

The tool's licensing costs are monthly. 

I rate Azure Cost Management an eight out of ten. 

Cost Management is used to control your bills by setting limits. Sometimes, there are some offers from Microsoft for better pricing when we utilize the solution on log files, such as if we are making some reservation to reserve resources for a long time.

Cost management is the console's most valuable feature.

All the offers should be on the console. You shouldn't need to select from different tabs. You shouldn't need to go to each resource and check if it is there or not. You should be able to understand the reservation by doing it from one console. There should be a centralized console.

I have worked with the console for four or five years.

The solution is stable. Microsoft manages everything as a portal, so it is stable and flexible, and availability is always high.

Microsoft manages its infrastructure, so we don't need to handle scalability. It is scalable all the time. All my customers use it.

They provide support for this type of product.

The console is already configured by default. If you want to configure it, you can, but there's nothing else.

Azure has a high price. It is not designed for small, individual companies, only enterprise companies. You are charged based on how much you use the solution.

I rate the console a nine out of ten.

I mainly use it for insights. It's about managing the cost of our resources and how to optimize where we can downsize or right-size resources.

It's mostly about analytics, and this is the first use case. Technically, there are multiple projects, like data integration, data cleansing, and maintaining data quality. There are a few of the underlying use cases. But the topmost or very first use case is analytics.

We have a dedicated cost management team to optimize costs.

Management would be difficult because right now I'm having one of the projects. And for that project, we are consuming multiple other services. There are storage, pipelines, multiple data functions, and Azure functions. So, the solution is made above multiple Azure components. And there are multiple environments. Like the development environment, the staging, and the production environment. 

Even in production, we have beta and alpha. So it's too much of resources, and it's difficult to manually go through each and every resource every time and try to see where we are hitting the cost and where we can reduce the cost. So that's where the cost management comes in to achieve.

Azure Cost Management actually helps an organization primarily for cost forecasting. For example, I have a budget in mind for this year. Azure Cost Management includes a feature called resource forecasting. Based on current resource usage and projected demand (including any buffer you add for your projects), you can estimate your expected costs for next year. This information helps you build budgets for future periods. So, budgeting tools are very helpful in this regard.

Before we formally adopted Cost Management, based on current consumption, we estimated costs for development and user acceptance testing. These estimates were surprisingly accurate, around 90%. Without a tool like this, manual forecasting could lead to missed savings or even overspending.

There are many features in Azure Cost Management that are most effective in tracking and reducing cloud costs. The resource forecasting feature is invaluable. Secondly, the ability to drill down to the regional and resource level is incredibly helpful for pinpointing where my costs are accruing. 

Improved integration with other solutions could definitely be beneficial.

I have been using it for more than five years now. 

I would rate the stability a seven out of ten. 

There are around a thousand end users using this solution in my organization. 

I would rate the scalability a six out of ten. We have limited features. So, I have neutral views on scalability. 

So, my feedback for customer service and support isn't specific to Cost Management, but for other resources like Power BI and Azure App Services, support can be slow. In some cases, I expect a quick turnaround. 

We might need to repeat information when switching agents. So, this can be a continuous cycle. I spend extra time explaining things on each call. So, there's room for improvement.

Neutral

We use AWS and some Google Cloud servers.

The vendor handles maintenance and troubleshooting.

My team has twelve members who handle things like advertisement, deployment, and cloud resource management.

However, there are different teams and people as it varies from project to project. 

Compared to competitors, it's cost-effective. I would rate the pricing a seven out of ten, with ten being expensive. 

Overall, I would rate the solution an eight out of ten. I would recommend using this product to others. 

Once we deploy customer resources, we use Azure Cost Management to monitor their current and future cost budgets. We submit those estimates about the future and the current user metrics to the customer.

Azure Cost Management helps us understand the current and peak usage of all the resources so that we will know which resources are being consumed more. The solution helps us diagnose and understand why some resources cost more so that we can fine-tune and reduce the cost. We can forecast the usage for the next year, month, or quarter based on current and previous usage.

The solution could improve its APIs to access the customer application. This would help the user to integrate them into their current application itself.

The solution needs to improve its support management. The solution should exhibit ready-made templates and architectures for different problem statements, making it easy to understand the capabilities of the services. This would make it easy for the developers or architects to choose the right architecture.

I have been working with Azure Cost Management for more than seven years.

Azure Cost Management is a stable solution.

Azure Cost Management is a scalable solution.

The solution's technical support is okay, but it needs to reduce its response time for L2 and L3 support.

We do automated deployments using pipelines. We use IaC scripts either in Microsoft templates or any bias templates or script templates to deploy the resources. The solution's deployment does not take more than 30 minutes.

Customers see a return on investment with Azure Cost Management because it reduces the time for the physical maintenance of the infrastructure. The solution also provides hassle-free scaling of the infrastructure based on the demand. Users get up-to-date security patches managed by Microsoft because they use SaaS services.

We are using pay-as-you-go licenses mostly for our customers.

Azure Cost Management is mostly deployed on the cloud.

Overall, I rate Azure Cost Management a six out of ten.

We use Azure Cost Management to minimize cloud costs.

I like the fact that you can set alerts on the predicted cost in Azure Cost Management. Before the cost reaches a limit, you can send out a warning that costs are predicted to exceed a threshold.

The solution's technical support should be faster, more knowledgeable, and customer-friendly.

I have been using Azure Cost Management for five years.

I’ve never had any issues with the solution’s stability.

I rate Azure Cost Management ten out of ten for stability.

Azure Cost Management is a scalable solution. More than 30 customers are using the solution in our organization.

I have had pretty bad experiences with the solution's technical support.

The solution's initial setup was quite easy because it was enabled by default.

A small team of five people is needed to deploy and maintain the solution.

With Azure Cost Management, companies can detect and address unexpected cloud expenditures.

Azure Cost Management is a free cost management tool.

Before choosing Azure Cost Management, we evaluated CloudCheckr and CloudHealth. The main difference between them and Azure Cost Management is multi-cloud support.

Azure Cost Management is a cloud-based solution.

I would recommend Azure Cost Management to other users because it's a free cost management tool you can use rather than buy a third-party tool. Azure Cost Management is available out of the box and does what it's supposed to be doing. Some third-party tools have more capabilities, but you don't really need those.

Overall, I rate Azure Cost Management an eight out of ten.