Microsoft Azure DevOps Reviews

We are using Azure DevOps for continuous integration and continuous deployment.

Microsoft Azure DevOps has helped the developers a lot and we are deploying process changes very frequently and simultaneously. A lot of my team members that are developers are updating the code in parallel using Git. Additionally, Microsoft Azure DevOps is providing a very good approval mechanism. Overall it is benefiting by creating efficiency in production deployment and applications, our new releases are running well. The security of secured is good.

We are facing a lot of issues in the development of containerized solutions. We are facing a lot of challenges in this area. They could make the process simpler.

I have been using Microsoft Azure DevOps for approximately four years.

The technical support from Microsoft Azure DevOps is good. Whenever we have raised a ticket with priority, we had a very good response from the technical team. My experience with Microsoft support is very good.

The integrations of Microsoft Azure DevOps are good and the implementation is not difficult. The testing of the solution went well.

I have seen a return on investment from using Microsoft Azure DevOps.

We have spread the knowledge about Microsoft Azure DevOps to a lot of our customers. We have organized a lot of training sessions because we are Microsoft's gold partner. That is why we promote all the tools and technologies which are part of Microsoft and we're also using them.

I rate Microsoft Azure DevOps a nine out of ten.

There are two versions of Azure DevOps: the cloud version and the on-premises version. We use the cloud version in very few situations, but most of our software is based on Azure DevOps on-premises.

We are a software house, and we develop software. We use it to store our source code; that is, it is the repository for our source code.

We have different teams working on different products, and each one uses a different methodology and a different process. Azure DevOps helps with that. For instance, one group may be using Scrum as a methodology to develop their software. The other group could also be using Scrum but with CDCI (continuous development, continuous integration), which helps a lot when you have to develop, test, and deploy the solution.

I think the most usable thing is that you can follow the whole progress of the development process. This makes it very useful for us.

As for improvement, the first one is pricing. For us, luckily because we are partners, it's free. Microsoft gold partners do not have to pay, but if you're not a partner, the product is very expensive.

The second would be that the tool should integrate with some of the competitors. It doesn't matter if it's a big market; it's difficult when you have to integrate with other competitor's tools, like JIRA, for instance.

If you look at the competitor's tools, they integrate easily with Microsoft, but on Microsoft's side, it's not as easy. They have been changing, but still, there are a number of gaps there.

I've got teams that want to use Microsoft Project, not only to control the whole process of the development but also to control the whole project and software. I think Project should be integrated with DevOps.

We have been using this solution for 10 years.

It is very stable. I think the system is down only a couple of hours per year, so it's very stable.

It's very scalable. We started using this solution 10 years ago, and it has evolved, We also have grown our software production, and so far, we have scope with all these situations.

We haven't had any problems with the product, but every time we had some questions, technical support staff answered pretty fast, in less than 24 hours.

The initial setup is pretty easy.

For the deployment, I think we had two people: one person from infrastructure and one who was a specialist in Azure DevOps. For maintenance, because we have about 80 people using this software, we only have one and a half people taking care of the software. That is, the infrastructure person does this part-time. He doesn't spend the whole day taking care of DevOps.

The ROI is very positive for us, but it's difficult to say how it would be if we had to pay for the solution. It's a very worthwhile product, but again, we don't have any comparisons because we don't pay anything for it.

Microsoft Azure DevOps is an expensive solution.

Get to know the product because it is complex and has many different possibilities.

It is worth having it, but you have to have an in-depth understanding and know what it is capable of doing. Otherwise, you're going to install it, and then it will be like having a very nice car in your garage that you don't know how to drive.

On a scale from one to ten, I would rate Microsoft Azure DevOps at eight.

We are an application development company, so DevOps helps us manage the work our developers and software engineers do on-site. It's convenient for customers because everybody works from home due to COVID.

DevOps is used within our organization and we also encourage some of our clients who are interested in a development platform to use Azure DevOps, but we have other clients that actually prefer Red Hat or other platforms. We like Azure DevOps, but our cloud environment is AWS. We've done three implementations on AWS without any problem.

Our technical sales staff and business development people need to know how far the developers are on any product that we're developing. DevOps makes it easier for you to see how far along they are with the work because they have a repository where they store everything. There is a portal where you can see what has been done, what has been tested, what is working, and what isn't. I have a huge dashboard with an overview of what the development team is doing from an executive point of view.

I know exactly what they're working on. If the team is falling behind on a project, there's a project management module where I can see exactly what was supposed to be delivered and what hasn't been. 

I can't think of any specific things at the moment, but I've run into things that I didn't like. I came across something that I wanted to be changed in DevOps, but I can't remember what it was. It was a particular feature I was looking for that I couldn't find.

I'm happy with DevOps' stability. I've had problems with the Red Hat environment, but I think it also boils down still to implementation skills. We're a big Microsoft implementer, so we find Azure DevOps to be highly stable.

DevOps is highly scalable. Before one of our clients decided to move to the cloud version of DevOps, they decided to try it in a small environment to see if they liked it. Previously, they had Team Foundation Server running on-premises, and we encouraged them to switch to DevOps. We set up a minimal environment and used it as a typical development environment. It wasn't for testing or anything. It was just a mini development environment that replicated their internal chassis.

Before we started using DevOps, we were using Microsoft Team Foundation Server, which allowed the whole team to share work and collaborate. DevOps does that and a little more.

Most of the time we just leave it on the cloud instead of deploying it on-prem, unless a client requests on-prem. In that case, we just replicate the cloud environment in the on-prem environment. There's no real difference, and we've had some clients who change and say they now prefer to have it on the cloud. 

After the subscription, which took about a day, we had our B environment up and running, and everything was transferred from on-prem to the cloud. In the older days, it would take you about a month. But now, to move, it actually took us, I think, almost a week, because the biggest challenge was moving the data more than the environment. Moving the environment, it took about, I think, a day or two. But the data was a bit of a problem.

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. 

I rate Azure DevOps seven out of 10. I would give it a higher rating, but there are a couple of things that tick me off.

I have been working with it for different projects and purposes. I'm basically the main architect for such solutions.

It is stable. I like Azure a lot. All our guys are Microsoft certified. 

It is fairly new, so there are a lot of changes, and because it keeps on changing, you need to adapt to those changes.

Its setup is quite complex.

It is stable.

We never used Microsoft's technical support. We always get it right.

Its initial setup is quite complex. There are a lot of caveats. Even if I can call a setup out of the box, it is not really out of the box.

We managed everything on our own. It involved fitting other products with the existing product. If you don't encounter problems, you're not going to learn.

We are 100% satisfied with it. I would rate it a nine out of 10.

We use Microsoft Azure DevOps for applications that analyze data and the data scientist creates the test data for the manual and automatic application tests. Here in Europe, we need anonymous synchronization of all data for testing.

We create special applications for creating data for direct tests.

Microsoft Azure DevOps has been very good for creating pipelines, and all the solutions for creating task management for developers and for the business. 

All of the tests of the applications are done on the mobile or web interface and it could be improved.

The connection to Power BI could improve. Power BI is a very good platform for reporting and presenting processes, but a good engine does not exist to present the process development in time in Power BI. It's a typical business reporting tool.

I have been using Microsoft Azure DevOps for approximately one year.

Microsoft Azure DevOps is highly stable.

There are two options to build. The first option is to build in the cloud, which is very stable but not quickly. The second is to build the systems in the local networks. 

We have 5 to 10 people using this solution in my organization. We have three DevOps and the others are the QA cluster.

We do not use support from Microsoft, we have not had any problems.

The initial setup of this solution was complex. Every part of the implementation was difficult.

For us to implement our production it took approximately 10 to 20 sprints. One sprint is two weeks.

We require a three-person team for the maintenance and support of the solution.

The price of the solution is expensive.

All people who work on projects must have good staff in development in .net, and need to have certificates. The minimal certificate is the AZ-204 Azure developer, it is obligatory.

I rate Microsoft Azure DevOps a nine out of ten.

We use it for planning, pipeline management and testing, as well as using it as a CI/CD tool.

I like the agile management of projects, running stand-ups and the like. The pipeline management feature is great.  

We'd like to see an improvement in reporting across multiple projects. The same applies to improving program visibility so that project managers can get that pane of glass to assist with their work. It would be a big win for a lot of users as well as a good addition to the tool. 

We've been using this solution for close to four years. 

The solution is stable. There are still the occasional issues but on average it's very stable. 

The solution is easily scalable because it runs on the cloud and everything is managed by Microsoft. We don't do anything in terms of increasing capacity so when more users are added the increased capacity is automatically managed. 

We haven't made a lot of calls to technical support but when we have their response has been good and quick. 

We have a DevOps engineer who carried out the implementation for us and I believe it was relatively easy. 

I rate this solution eight out of 10.

We use Microsoft Azure DevOps for our source control, change request management, and a small amount of Wiki.

Microsoft Azure DevOps has helped our organization from having completely automated builds. The developers can send their own code to QA without needing a release manager or lead or IT person moving the code over.

The dashboards need bigger with better extensions and layouts. There isn't a workflow related to the statuses on the dashboard. It only lists the statuses. You can have one started, and once done, but everything in between is only in progress and could be in any order you want, it lacks flow.

I have used Microsoft Azure DevOps for approximately one year.

Last week the builds did stop working for some unknown reason, and then started again. Most of the time the stability is fine, but there are occasions when there's a problem on Microsoft's side, where it creates problems for us.

The solution is scalable but you have to pay for it.

We have approximately 40 people using this solution consisting of developers, QAs, and product owners. We are extensively using this solution in our organization.

I wish the dashboards and the release process were integrated better. The use of Kanban dashboards could be a lot better. They don't have a Kanban dashboard. They have a dashboard with one sprint but it's not exactly the same as a Kanban dashboard. You are not able to do much with them. 

We have not needed to contact the support.

The installation is straightforward. We can create a whole new organization in less than a day.

We did the implementation ourselves. I do most of the maintenance but it is mostly maintenance-free.

There are additional costs for some functionality, such as increased scalability.

My advice to others is for them to do their research before implementing this solution.

I rate Microsoft Azure DevOps a seven out of ten.

The plugins are the biggest thing. I like how Visual Studio is designed as a shell application, and then the plugins make it do what you want it to do.

Microsoft could improve Visual Studio by making it easier to find the plugins you need to get your job done. Maybe they could implement an AI search instead of a simple tech search. Sometimes, people come up with a catchy name for something, and you don't know how it's spelled. For example, a developer might come up with a packet wizard and spell weird, like P-A-K-I-T.

I've been working with Microsoft Visual Studio since it first came out in 1997, so about 24 years.

Visual Studio is very stable.

I don't think scale applies to Visual Studio because it's a developer tool. And I haven't had a lot of experience with massive projects where multiple teams are working on the same source code. I've only worked on a team of a few people.

I think support is probably pretty decent, but I've never had to use it. I just look at Visual Studio's source code to troubleshoot it. 

The setup is pretty straightforward. Visual Studio runs pretty fast.

I'd say Visual Studio is a nine out of 10. If you're thinking about adopting Visual Studio, research the kind of functionality you need. The nice thing about Visual Studio Code is that it's a modular design. So if you're working on a strange language that has a different syntax, you can just get a plugin that'll format your code for you based on the language it's in.