Cyber Security Specialist at a consultancy with self employed
Real User
Top 20
2024-06-14T16:34:00Z
Jun 14, 2024
I find Azure Stack to be very costly. The people who manage the budgets are satisfied with the solution’s medium pricing, which is neither very expensive nor very cheap. I think the solution has a reasonably good value for what it provides.
@reviewer2500395Â Aquila Clouds Multicloud BillOps & Finops solutions can work with Azure Stack and have helped many enterprises in Charge back , Show back and optimization of Azure Stack environment's. With more and more solutions like these having custom dashboards the use of Azure Stack becomes simple and cost effective.
I would rate the pricing a seven out of ten, with ten being expensive. It's one of the more affordable solutions on the market, but Azure pricing has a lot of factors. Azure Stack isn't a single product. The cost depends on the specific solution you build. So, it has been cost-effective for us.
The pricing model is consumption-based. We pay as we go. Our overall cost is lower. Some things in the pricing model are a bit confusing. The vendor has two pricing systems. One is for Azure Stack, which is on the cloud. We also install and use it on-premises. The difference in price for the two is not very clear most of the time in the documentation. The tool is affordable.
The licensing costs are expensive. I pay on a monthly basis. We pay through our managed partner. So, it's bundled with other services provided by our partner.
Azure itself is not very pricey since the most expensive parts are hardware and hardware support. We use a consumption-based model and it does not have a fixed time, we just pay for how long we use it. The cost of it depends on the workload. The starting price is $6 per vCPU for a Linux VM monthly, or $34 per vCPU per month for Windows machines.
In some cases, it's difficult to calculate the licensing costs. All the cost is the big picture there because this concerns the capacity of Azure Stack and Azure Service as well. it's a pay-as-you-go model. So, it has some concerns to define the cost.
Azure Stack has an annual licensing fee, which is very expensive. We pay service costs to the integrator or the partner to support and maintain Azure Stack.
Head of Architecture and DevOps at a financial services firm with 10,001+ employees
Real User
2022-09-27T17:25:00Z
Sep 27, 2022
The licensing is pay-as-you-go, and Azure also provides a bring-your-own-license. I believe that is a good option if anyone is looking at it and they already have a license. They can get the infrastructure and the provision in a very short time and it will save the existing licenses. Different applications will have different licensing needs. It depends on which tool you use. You will then need to secure that license.
In terms of pricing, my customers believe AWS is slightly more reasonably priced than Azure. They believe it is significantly less expensive than what Azure offers. It is simply a matter of pricing.
Azure has a subscription version. It has a pay-as-you-go subscription with a subscription ID. So, you have your particular subscription with an enterprise agreement. There is a dev-type subscription for development and testing. The pricing seems pretty reasonable. The pricing could be per resource. For example, you have Databricks, Data Factory, Scaled DB, and Cosmos. You have everything in Azure. They have an Azure pricing calculator that you can use to check the price of every resource. It gives you a proper cost estimation. You can compare the cost and then go for the best resource for your project.
Solutions Specialist at a computer software company with 10,001+ employees
Real User
2021-09-02T16:02:15Z
Sep 2, 2021
The licensing is one of the solution's most attractive features. Subscription model customers need not make large expenditures on upfront purchasing. A customer must purchase the software needed for Microsoft support, if he wishes to have this. This would incur a monthly fee. But, the upcoming Azure Stack HCl, which is hybrid cloud, does not involve an upfront purchase, only a subscription-based fee.
It is in the medium range cost-wise. For each component, I sort of buy licensing. Each component has its licensing fee by the number of users or by size.
Pre-Sales Engineering Manager - Cloud Computing at a tech services company with 11-50 employees
Real User
2019-12-31T09:39:00Z
Dec 31, 2019
If we are trying to deploy the Microsoft suite, first of all, we need to buy the data center licenses. Datacenter licenses are only used for verification solutions. Using that as a solution, we can declare an unlimited number of four VMs on the hardware. I spent a contribution to the hardware, the code, and the processes, and that all depends on the hardware architecture.
Azure Stack is the #1 ranked solution in top Hybrid Cloud Computing Platforms and #2 ranked solution in top Software Defined Data Center vendors. PeerSpot users give Azure Stack an average rating of 8.0 out of 10.
Azure Stack is a very expensive solution. The costs are very opaque and coming out of control quite quickly.
I find Azure Stack to be very costly. The people who manage the budgets are satisfied with the solution’s medium pricing, which is neither very expensive nor very cheap. I think the solution has a reasonably good value for what it provides.
@reviewer2500395Â Aquila Clouds Multicloud BillOps & Finops solutions can work with Azure Stack and have helped many enterprises in Charge back , Show back and optimization of Azure Stack environment's. With more and more solutions like these having custom dashboards the use of Azure Stack becomes simple and cost effective.
I would rate the pricing a seven out of ten, with ten being expensive. It's one of the more affordable solutions on the market, but Azure pricing has a lot of factors. Azure Stack isn't a single product. The cost depends on the specific solution you build. So, it has been cost-effective for us.
The pricing model is consumption-based. We pay as we go. Our overall cost is lower. Some things in the pricing model are a bit confusing. The vendor has two pricing systems. One is for Azure Stack, which is on the cloud. We also install and use it on-premises. The difference in price for the two is not very clear most of the time in the documentation. The tool is affordable.
Azure stands out for its flexibility with pay-as-you-go options.
The licensing costs are expensive. I pay on a monthly basis. We pay through our managed partner. So, it's bundled with other services provided by our partner.
Azure itself is not very pricey since the most expensive parts are hardware and hardware support. We use a consumption-based model and it does not have a fixed time, we just pay for how long we use it. The cost of it depends on the workload. The starting price is $6 per vCPU for a Linux VM monthly, or $34 per vCPU per month for Windows machines.
In some cases, it's difficult to calculate the licensing costs. All the cost is the big picture there because this concerns the capacity of Azure Stack and Azure Service as well. it's a pay-as-you-go model. So, it has some concerns to define the cost.
Pricing depends on the solutions which we build on. IaaS’s pricing is high. Other services might be competitive.
The product is expensive, but it is fine for the value that the solution produces.
It is not a cost-friendly solution. I rate it a seven for pricing.
Azure Stack has an annual licensing fee, which is very expensive. We pay service costs to the integrator or the partner to support and maintain Azure Stack.
Pricing could be improved so I rate it an eight out of ten.
The solution saves us money but is more costly than other products such as AWS. We have been paying 10 crores for our Azure services.
The licensing is pay-as-you-go, and Azure also provides a bring-your-own-license. I believe that is a good option if anyone is looking at it and they already have a license. They can get the infrastructure and the provision in a very short time and it will save the existing licenses. Different applications will have different licensing needs. It depends on which tool you use. You will then need to secure that license.
The licensing model of Azure Stack is complicated. The solution is expensive.
I would rate the pricing 4 out of 5. It could be lower.
Azure is reasonably priced compared to Google Cloud, AWS, or some other cloud giants.
In terms of pricing, my customers believe AWS is slightly more reasonably priced than Azure. They believe it is significantly less expensive than what Azure offers. It is simply a matter of pricing.
Azure has a subscription version. It has a pay-as-you-go subscription with a subscription ID. So, you have your particular subscription with an enterprise agreement. There is a dev-type subscription for development and testing. The pricing seems pretty reasonable. The pricing could be per resource. For example, you have Databricks, Data Factory, Scaled DB, and Cosmos. You have everything in Azure. They have an Azure pricing calculator that you can use to check the price of every resource. It gives you a proper cost estimation. You can compare the cost and then go for the best resource for your project.
Azure is relatively expensive, but on the other hand, you get excellent support, stability, and security, so I think it's worth it.
The price of Azure Stack is higher relative to other solutions.
I believe our license is yearly.
The licensing is one of the solution's most attractive features. Subscription model customers need not make large expenditures on upfront purchasing. A customer must purchase the software needed for Microsoft support, if he wishes to have this. This would incur a monthly fee. But, the upcoming Azure Stack HCl, which is hybrid cloud, does not involve an upfront purchase, only a subscription-based fee.
Commercially, Azure Stack is cheaper than AWS.
Azure Stack is expensive.
In terms of costs, it is a standard price, and there is no negotiation.
The pricing is very expensive. If I were rating it on cost then it would be a five out of ten.
It is in the medium range cost-wise. For each component, I sort of buy licensing. Each component has its licensing fee by the number of users or by size.
We are satisfied with the pricing.
The price of using Azure Stack for OCR is more expensive than using OCR by Google.
The pricing of the solution is quite fair. It's not too expensive.
If we are trying to deploy the Microsoft suite, first of all, we need to buy the data center licenses. Datacenter licenses are only used for verification solutions. Using that as a solution, we can declare an unlimited number of four VMs on the hardware. I spent a contribution to the hardware, the code, and the processes, and that all depends on the hardware architecture.