DevOps Engineer at ENTERPRISE SYSTEM SOLUTIONS LIMITED
Real User
Top 5
Nov 6, 2025
Cloud infrastructure consists of three systems: SaaS, PaaS, and IaaS (Infrastructure as a Service, Platform as a Service, and Software as a Service). As of my understanding, this is the best platform to get all your needs in one place. In terms of other cloud infrastructure, I have seen that some things are complicated to integrate, and there are a few more things which can cause some delays about operations. However, if implementing the whole infrastructure in Microsoft Azure, then it is very seamless. Regarding cost optimization, Azure charges only the parking cost, not for unnecessary or unwanted cost. One of my clients was using AWS, and I observed that for the last three months, the subscription charges were continuously increasing: 35,000, now it is 55,000. The 20,000 difference is within four months because they have provisioned some database replication system in another availability zone, which is the main problem they are facing for the cost optimization process. However, in terms of Microsoft Azure, if putting all the things in the same region and implementing all infrastructure in one place, then it will be more efficient and cost relevancy will also be there. I do not think Microsoft Azure is demanding much more than other infrastructures because it is providing enterprise-level services. If wanting to work with seamless integration, then the price does not matter, and this is good. As of my understanding, it is more secure than other infrastructure because Microsoft is investing 200 billion dollars plus more for its security concerns. Cost optimization can be done, and it depends on how you are engineering your cloud service. However, whatever Microsoft is charging, I do not think it is much more than other infrastructure because what it is charging is legit.
Regarding the costs involved, I am not heavily involved in the financial operations side. I do know that we spent a considerable amount of money. From my perspective, for a business case like this, I would not have opted to spend so much, but it was a decision made by management. It might be seen as expensive for small businesses.
Pricing is fairly average, however, with other Microsoft products, pricing has been a bit confusing. Unless you deploy a solution, you can't get to a pricing model properly. They don't even provide a POC where you can have a sandbox or stuff that you can go through and see how exactly it's costing. That has been one of the challenges with Microsoft until you deploy a solution.
Program Solution Architect at a tech services company with 11-50 employees
Real User
Top 10
Apr 17, 2024
The solution's pricing is pretty cheap. The best part of the Azure DevOps and SaaS model is that there's no upfront cost. The tool has a per-user license. It's free for five users, and there is a price above five users. The solution's deployment and licensing costs are very cheap compared to those of its competitors. The solution's pricing is not fixed. The solution's testing license is $50 per user. It's $15 for normal users who use backlog management. We have two people from the test team and seven from the other team. This is in maintenance. Since we had a big testing team, we had 15 people in testing and 30 people in backlog management during peak time. You can say it has a 70:30 ratio. Most of the cost is in testing, and the backlog management is really cheap. On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a three out of ten.
Microsoft's licensing and pricing for Azure DevOps are competitive within the market. While it may be expensive, it is almost the same as the pricing for comparable products in the industry. I would rate the pricing as a six out of ten in terms of costliness.
The licensing for this product is on a monthly basis. It is relatively inexpensive compared to other solutions that necessitate servers and physical hardware.
Service Delivery Manager at a comms service provider with 1,001-5,000 employees
Real User
Apr 1, 2022
The reason that customers are going to the cloud is that it provides the ability to reduce the license cost. For example, when purchasing Office 365 it is bundled with Word, Excel, PowerPoint, Access, and many other applications. In the past, purchasing a license was approximately $600. Today it's only $35 or $45 per customer, per client, or per user, plus the storage. It's less expensive for companies today, to use something, such as Microsoft Azure DevOps, and provide the software to all the employees needing a license. It's better to go with the cloud than just to buy the licenses by themselves. There are some additional costs. You pay for how much space you are using. If you don't use too much space, then the price will be very little. If you use a lot of space, you have to pay for it. Additionally, they offer readiness training. It is not included directly in what is called a statement of work when you are doing business with customers. This is when things can be a little more difficult because it can be expensive for customers if they want to change deployments from on-premises to cloud or hybrid.
Agile Coach at a pharma/biotech company with 10,001+ employees
Real User
Mar 15, 2022
It is very expensive in comparison to others. As the cost structure is per user, I would recommend paying the cost structure based on the amount of data you use rather than the number of users.
The cost of Azure DevOps is manageable. You have the option to purchase a license that is per user. You can choose based on the size of your team. For example, you can opt for a volume enterprise license or go for user-based licensing if you don't have a huge number of users. You can start with a smaller package and then scale up as needed. Let's say, for instance, you are a smaller company with about only 10 users of the environment. Then, two months later, you win the Powerball, and you get a billion dollars and bring in a thousand developers. You have the flexibility to move from a small-team subscription to a big subscription easily. So you don't necessarily have to take the volume. The licensing model covers all three tiers, whereby you can have a volume license, individual users, or groups. We are using groups, and we've found it affordable because you cancel their license if someone leaves. When we get a new person, we repurchase the license. We pay a monthly subscription, but the annual licenses are cheaper because of the commitment.
Test Advisory, Management & Implementation at a energy/utilities company with 51-200 employees
Real User
Nov 15, 2021
I don't know the pricing of DevOps. It would be much cheaper than ALM because ALM came out as a software product initially. Now they are moving into a cloud and subscription model. In that case, Microsoft is coming from Azure and the cloud and DevOps and software as a service, so it would be much cheaper, but the catch would be that they are trying to get money on all sides, like an operating system, Microsoft Office, or Microsoft Azure DevOps. The good part is that it's a complete package, but at the same time, once you've gone with them, you don't have much leverage to split out into some other activities because everything is interconnected and entwined by that time, and it would be like a monopoly. It won't be good if you try to split out at a later point in time because everything is connected—all our Microsoft products like operating systems, OfficeSuite, MS Teams, Azure DevOps, etc.
Software Engineering Manager at a healthcare company with 1,001-5,000 employees
Real User
Oct 7, 2021
We're not paying a lot for this product. As developers, we have a Visual Studio license which is basically free. That's how their licensing model works. Then we have a number of stakeholders who need to do edits in the system, but not work with code necessarily. I believe they're paying $5 a month per user. We also have users who only need to read things and don't need code so I set that up for everyone who needs it. We're probably paying a few hundred dollars per month altogether. That's a minor cost for us; we're not currently hosting anything on cloud, so it's a small cost compared to hosting a solution. We ran into a few things where we had to pay more because of the number of concurrent building agents. We had capped it low and the developer was unhappy so we paid a little more to get what we needed and that's been good. I don't like it when you get a big bill and you don't know about it.
Group Product Manager – Billing and Payments at MultiChoice Group
Real User
Aug 17, 2021
Its pricing is reasonable for the number of features that you get and the functionality that you can utilize for the agile delivery, which is what we are using it for. I found it extremely cost-effective.
It would be nice if the licensing was a bit cheaper. Our IT team looks after that aspect. I don't deal with tasks such as licensing and payments directly.
I don't know what we pay, but I do know what I've seen online. If we switched to JIRA, we will basically have to double our costs because we still have to pay for the DevOps licensing. We're probably spending $100 a month on it. It has only standard licensing fees.
The price is reasonable, but of course, you can find others that are cheaper such as Atlassian. But, if you look at the more serious products like Polarion, it's very competitive. If you have good Microsoft programs, it's nearly free.
Director at a computer software company with 10,001+ employees
Vendor
Jan 25, 2021
Price is an area that could be improved. There are products on the market with a fixed price of 50 or 100 people, you are a bucket price. With Azure, you have to pay for every user. It's good to have a bucket such as 50 to 100, or 100 to 200, and flexible pricing. The issue may be from having more than one license. When you procure one license or two licenses, it becomes difficult. It should be easier to procure a license, it should not be one by one. We don't know how many members I will have on my team three months from now.
We have 100 users and the cost is $11 per user. There's an additional cost if you want to use the integrated test plan. You have the option to just change your license and you can use the automated test integrator.
I am not comfortable sharing the details of cost because there may be different pricing schemes, but compared to AWS, Azure is less expensive. So in the pricing in this class of services, Azure is good. It can work well for small to medium enterprises. But this solution is may not be good for those who are not enterprise-level users. Small cloud computing providers have better pricing than the bigger cloud computing providers like AWS and Microsoft Azure and may be a better choice for non-enterprise use. Still, Azure is priced better than AWS. Price may not be the only thing to consider.
Microsoft Azure DevOps is a cloud service that enables developers to collaborate on code development projects and create and deploy applications quicker than ever before. The service helps unite developers, project managers, and software development experts through a collaborative experience while using the application. For the users' convenience, Azure DevOps offers the user cloud services through Azure DevOps Services or an on-premises service using Azure DevOps Server. In addition, it...
Cloud infrastructure consists of three systems: SaaS, PaaS, and IaaS (Infrastructure as a Service, Platform as a Service, and Software as a Service). As of my understanding, this is the best platform to get all your needs in one place. In terms of other cloud infrastructure, I have seen that some things are complicated to integrate, and there are a few more things which can cause some delays about operations. However, if implementing the whole infrastructure in Microsoft Azure, then it is very seamless. Regarding cost optimization, Azure charges only the parking cost, not for unnecessary or unwanted cost. One of my clients was using AWS, and I observed that for the last three months, the subscription charges were continuously increasing: 35,000, now it is 55,000. The 20,000 difference is within four months because they have provisioned some database replication system in another availability zone, which is the main problem they are facing for the cost optimization process. However, in terms of Microsoft Azure, if putting all the things in the same region and implementing all infrastructure in one place, then it will be more efficient and cost relevancy will also be there. I do not think Microsoft Azure is demanding much more than other infrastructures because it is providing enterprise-level services. If wanting to work with seamless integration, then the price does not matter, and this is good. As of my understanding, it is more secure than other infrastructure because Microsoft is investing 200 billion dollars plus more for its security concerns. Cost optimization can be done, and it depends on how you are engineering your cloud service. However, whatever Microsoft is charging, I do not think it is much more than other infrastructure because what it is charging is legit.
The price and licensing of Microsoft Azure DevOps were fair.
Regarding the costs involved, I am not heavily involved in the financial operations side. I do know that we spent a considerable amount of money. From my perspective, for a business case like this, I would not have opted to spend so much, but it was a decision made by management. It might be seen as expensive for small businesses.
Pricing is fairly average, however, with other Microsoft products, pricing has been a bit confusing. Unless you deploy a solution, you can't get to a pricing model properly. They don't even provide a POC where you can have a sandbox or stuff that you can go through and see how exactly it's costing. That has been one of the challenges with Microsoft until you deploy a solution.
I have no idea about the pricing of Microsoft Azure DevOps.
The solution's pricing is pretty cheap. The best part of the Azure DevOps and SaaS model is that there's no upfront cost. The tool has a per-user license. It's free for five users, and there is a price above five users. The solution's deployment and licensing costs are very cheap compared to those of its competitors. The solution's pricing is not fixed. The solution's testing license is $50 per user. It's $15 for normal users who use backlog management. We have two people from the test team and seven from the other team. This is in maintenance. Since we had a big testing team, we had 15 people in testing and 30 people in backlog management during peak time. You can say it has a 70:30 ratio. Most of the cost is in testing, and the backlog management is really cheap. On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a three out of ten.
Microsoft's licensing and pricing for Azure DevOps are competitive within the market. While it may be expensive, it is almost the same as the pricing for comparable products in the industry. I would rate the pricing as a six out of ten in terms of costliness.
We pay yearly licenses. The tool could be cheaper.
We have an MPN subscription for Microsoft Azure DevOps, and it's all included.
Compared to other tools, Microsoft Azure DevOps is a cheap solution.
I would rate the costliness of Azure DevOps at a seven out of ten.
The pricing for Azure DevOps may be higher compared to other tools, but overall, I find it reasonable.
The solution is expensive.
The licensing for this product is on a monthly basis. It is relatively inexpensive compared to other solutions that necessitate servers and physical hardware.
This is good software for a reasonable price.
The pricing is very competitive because of the whole development cycle by Azure DevOps. You don't have to buy and integrate several different tools.
The cost is reasonable. For the basic license, it is around five euros per month.
I don't deal with licensing. I can't speak to how much the solution costs.
The reason that customers are going to the cloud is that it provides the ability to reduce the license cost. For example, when purchasing Office 365 it is bundled with Word, Excel, PowerPoint, Access, and many other applications. In the past, purchasing a license was approximately $600. Today it's only $35 or $45 per customer, per client, or per user, plus the storage. It's less expensive for companies today, to use something, such as Microsoft Azure DevOps, and provide the software to all the employees needing a license. It's better to go with the cloud than just to buy the licenses by themselves. There are some additional costs. You pay for how much space you are using. If you don't use too much space, then the price will be very little. If you use a lot of space, you have to pay for it. Additionally, they offer readiness training. It is not included directly in what is called a statement of work when you are doing business with customers. This is when things can be a little more difficult because it can be expensive for customers if they want to change deployments from on-premises to cloud or hybrid.
It is very expensive in comparison to others. As the cost structure is per user, I would recommend paying the cost structure based on the amount of data you use rather than the number of users.
The cost of Azure DevOps is manageable. You have the option to purchase a license that is per user. You can choose based on the size of your team. For example, you can opt for a volume enterprise license or go for user-based licensing if you don't have a huge number of users. You can start with a smaller package and then scale up as needed. Let's say, for instance, you are a smaller company with about only 10 users of the environment. Then, two months later, you win the Powerball, and you get a billion dollars and bring in a thousand developers. You have the flexibility to move from a small-team subscription to a big subscription easily. So you don't necessarily have to take the volume. The licensing model covers all three tiers, whereby you can have a volume license, individual users, or groups. We are using groups, and we've found it affordable because you cancel their license if someone leaves. When we get a new person, we repurchase the license. We pay a monthly subscription, but the annual licenses are cheaper because of the commitment.
The price of the solution is expensive.
Licensing costs are very reasonable compared to other solutions. It's a good price.
I don't know the pricing of DevOps. It would be much cheaper than ALM because ALM came out as a software product initially. Now they are moving into a cloud and subscription model. In that case, Microsoft is coming from Azure and the cloud and DevOps and software as a service, so it would be much cheaper, but the catch would be that they are trying to get money on all sides, like an operating system, Microsoft Office, or Microsoft Azure DevOps. The good part is that it's a complete package, but at the same time, once you've gone with them, you don't have much leverage to split out into some other activities because everything is interconnected and entwined by that time, and it would be like a monopoly. It won't be good if you try to split out at a later point in time because everything is connected—all our Microsoft products like operating systems, OfficeSuite, MS Teams, Azure DevOps, etc.
I can’t speak to the exact pricing. It’s not an aspect of the product I deal with.
There are additional costs for some functionality, such as increased scalability.
We're not paying a lot for this product. As developers, we have a Visual Studio license which is basically free. That's how their licensing model works. Then we have a number of stakeholders who need to do edits in the system, but not work with code necessarily. I believe they're paying $5 a month per user. We also have users who only need to read things and don't need code so I set that up for everyone who needs it. We're probably paying a few hundred dollars per month altogether. That's a minor cost for us; we're not currently hosting anything on cloud, so it's a small cost compared to hosting a solution. We ran into a few things where we had to pay more because of the number of concurrent building agents. We had capped it low and the developer was unhappy so we paid a little more to get what we needed and that's been good. I don't like it when you get a big bill and you don't know about it.
Its pricing is reasonable for the number of features that you get and the functionality that you can utilize for the agile delivery, which is what we are using it for. I found it extremely cost-effective.
It would be nice if the licensing was a bit cheaper. Our IT team looks after that aspect. I don't deal with tasks such as licensing and payments directly.
We purchase the solution on an annual basis.
Licensing cost per user is approximately $11 to $15. We have about 400 users, but not all are active. We have around 200 to 300 active users.
There is a license for this solution.
I don't have a problem with the pricing.
I don't know what we pay, but I do know what I've seen online. If we switched to JIRA, we will basically have to double our costs because we still have to pay for the DevOps licensing. We're probably spending $100 a month on it. It has only standard licensing fees.
The main agile features are very expensive.
The price is reasonable, but of course, you can find others that are cheaper such as Atlassian. But, if you look at the more serious products like Polarion, it's very competitive. If you have good Microsoft programs, it's nearly free.
This area is very different for each and every organization and I would recommend that they research cost and pricing for their situation.
As a Microsoft Partner, you get a discount on the pricing. Licensing costs are around $80 a month for DevOps, but for Azure, it is about $200 a month.
Price is an area that could be improved. There are products on the market with a fixed price of 50 or 100 people, you are a bucket price. With Azure, you have to pay for every user. It's good to have a bucket such as 50 to 100, or 100 to 200, and flexible pricing. The issue may be from having more than one license. When you procure one license or two licenses, it becomes difficult. It should be easier to procure a license, it should not be one by one. We don't know how many members I will have on my team three months from now.
The price of this solution is fair.
It is a subscription model and I only pay for what I use.
We have 100 users and the cost is $11 per user. There's an additional cost if you want to use the integrated test plan. You have the option to just change your license and you can use the automated test integrator.
Microsoft Azure DevOps is free for up to five users and allows you to track a maximum of three projects.
I find that the pricing is good, and it is competitive with the other vendors in the market.
We don't have any complaints about the pricing.
The cost can get pretty high if you aren't paying attention to what you are doing.
I am not comfortable sharing the details of cost because there may be different pricing schemes, but compared to AWS, Azure is less expensive. So in the pricing in this class of services, Azure is good. It can work well for small to medium enterprises. But this solution is may not be good for those who are not enterprise-level users. Small cloud computing providers have better pricing than the bigger cloud computing providers like AWS and Microsoft Azure and may be a better choice for non-enterprise use. Still, Azure is priced better than AWS. Price may not be the only thing to consider.
The price is cheaper than Jira and some of the other competing tools.
I'm not sure about the pricing. It's not an aspect of the solution I currently deal with.
There is a licensing fee of $6/user per month. That's not too much money for us. There aren't really any additional costs beyond that.
Check out the pricing information from Azure Cost and analysis information.
It is easy to use if you are already familiar with Microsoft products.