Microsoft Azure DevOps Initial Setup

AC
Service Delivery Manager at a comms service provider with 1,001-5,000 employees

There are three ways to deploy Microsoft Azure DevOps. To set up all three deployments is very similar but different. The on-premise deployment is where the customer owns the code. What Microsoft Azure DevOps does lets you develop your code, and when you have finished your code, you have to put it in the cloud for the hybrid. Then you can test it in an environment that is similar to production. I was in charge of making sure that everything was set up correctly.

I was involved from the beginning of the implementation. I'm a project manager myself too. I don't have certification, but I've been doing project management all my life. One important element when doing the implementation is the voice of the customer. No matter what you're configuring or setting up, if the voice of the customer is not there, but the voice of the business and the employees is, that is only two-thirds of what you have to do.

For example, I want my customers to run this application even if they are in the jungle. If they have access to WiFi, cellular signal, or hotspots, they can have access to anything that Microsoft Azure DevOps can give to them. Except they need a client, and that's the other part. You need to understand what clients the customers are going to need. The clients depend on three things. You need to know the infrastructure of the customers, their immediate needs, and the needs of their customers. We're developing something for the customer who has customers. Unfortunately is not only DevOps, it's everything. DevOps is only one part.

DevOps has one issue. There are components that are produced and supported by other teams somewhere else. Service maps are very important to develop with DevOps teams. When we develop the service map, they know what to do. However, some DevOps do not like to have service maps, because they say that they know what to do. That's what the problem is, they need to understand that they're not alone.

View full review »
Jayashree Acharyya - PeerSpot reviewer
Director at PepsiCo

It took a few weeks for us to do the solution's initial setup.

View full review »
Ali Raza Pirwani - PeerSpot reviewer
Assistant Vice President at Bank Alfalah Limited

The initial setup is a little bit complex.

View full review »
Buyer's Guide
Microsoft Azure DevOps
March 2024
Learn what your peers think about Microsoft Azure DevOps. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
CR
Assurance Manager at a energy/utilities company with 5,001-10,000 employees

It is pretty straightforward on the administrative side, but I've been working with this technology for a long time. It really falls in line with the majority of Microsoft products. If you're familiar with the Microsoft stack, it follows their pretty standard setup. You go through a similar process. It is just about knowing the nuances that Microsoft has when you're doing a farm configuration or a farm setup and the recommended prerequisites before you get started.

If we're talking about new end-users who are going from an older version of TFS to Azure DevOps Server or Azure DevOps Services, there is going to be a bit of a delta because the technology is different. There is a slight learning curve. Of course, it has got fancier bells and whistles and a jazzier user interface. It has softer edges and things have moved from left to right. Things that you found on the left side have again moved back over to the right side for administrative or usability functions. Your security elements and the things that you used to see on the left side have again switched back to the right side. These are the kinds of nuances about which you would need to educate your end-users. You need to get them used to the boards and how to use those. If your company is transitioning from a CMI model to an Agile model, it is going to be very important for the folks who are administrating your projects and your project managers to know how to configure the projects themselves, how to use Teams, and how to use permissions. Security becomes even more important because a lot of that really influences how you see the information within your project, and how you manage your boards, your sprints, and the work items that you allocate to your scrums or sprint users.

As you're going through different stages of your project, you have your pipelines and repos where your more development-centric users are going to be. I try to allocate out two different kinds of users that we're going to have and target them when I'm educating my folks. You have a kind of power user, and you have your regular contributor user. It is important to make this distinction because there are folks who are going to be doing basic or just regular contributor work. They will just contribute to the work items that are on a board or within a sprint. You're also going to have users who need to be slightly elevated, which is going to be that basic plus test plan. You need to understand how those affect your subscription and billing towards that subscription and how to manage that when they're not actively using it. You need to monitor this and enroll them back to a stakeholder so that you're not constantly incurring costs against your pay-as-you-go subscription costs. Everything is pay-as-you-go once you get into the cloud.

View full review »
Usman ur Rehman Ahmed - PeerSpot reviewer
Cloud App Dev & Services Pre-Sales Lead for MEA & APAC at Systems Limited

The initial setup was quite intuitive. I would rate it eight out of ten.

View full review »
MM
Software Engineer at Mercedes-Benz AG

The initial setup is easy. Once the code is committed and the developers sign off, we just go to Azure DevOps, click on "Pipelines," and run the pipeline. That's all, pretty straightforward.

View full review »
Jeremy Chen - PeerSpot reviewer
Installation Engineer at CTCI

The initial setup was fairly complex and time-consuming. I would rate it four out of ten. During the initial setup, we encountered the most difficulty with Microsoft's documentation. It proved to be quite lengthy and lacked clear guidance, which made the setup process challenging. Consequently, we had to explore various additional resources to ensure a smoother setup of Azure DevOps.

View full review »
Mitch Tolson - PeerSpot reviewer
Director of Robotics at Fresh Consulting

I've been a developer on the backend. In terms of setting up the product, my answer would be highly complex. If I were just doing it for a core user, set of users, then I would say the setup was relatively frictionless. I would say the one point of ambiguity is for some newcomers if they don't understand the difference between CMMI templates versus Agile, versus Scrum, they'll find it complex. I've seen a lot of new users create dummy projects to then go in and see how each of those is configured from a template standpoint. Work could be done there to just reduce that level of friction.

In terms of deployment times, I've been on multiple different sides of levels of deployment. From the simple side, I've seen deployments take as little as a couple of minutes. If it's teams of five, for example, they go into the web app, they start up a new project, and boom they're in. They get all the requirements and user stories and all that stuff done. 

I've also been on the other side where it's been nine months with 22 people working full-time to configure and deploy this system across thousands and thousands of users. It just depends on the size.

View full review »
HarunRashid - PeerSpot reviewer
Principle BI Architect at Allshore Staffing

The initial setup process for Azure DevOps was somewhat complex, requiring documentation and technical support. Migration from previous tools and configuring project guidelines were involved. The deployment strategy involved creating directories, and repositories, setting up environments, and assigning access rights, following a predefined plan. Initially, deployment took about three to four hours, but now, for regular deployments, it typically takes 30 minutes to an hour, depending on project stability. 

For the initial deployment of Azure DevOps, gathering information from various resources is essential, but typically, only one person is needed to handle deployment through the web interface. Maintenance involves regular tasks like backups and occasional updates, requiring minimal effort.

View full review »
Alba Jamile Diaz - PeerSpot reviewer
Founder at Premium Consulting SAS

The initial setup can be straightforward if the consultant is knowledgeable.

View full review »
BC
Director at a computer software company with 10,001+ employees

I was not involved in the installation. My team completed it.

View full review »
Krishnakumar Subramanian - PeerSpot reviewer
Technical Director at Alstom Ferroviaria S.p.A.

My team set up the solution. It took one and a half years to stabilize.

View full review »
CW
Software Engineering Manager at a healthcare company with 1,001-5,000 employees

The initial setup is very intuitive. What I think they could work on is the whole permissions model where you have projects and other things which require permissions and which is not very intuitive. You can do almost everything but I want a more granular permissions model that's also easy to maintain. I don't quite like the way it's set up so there's some work to be done there. I think I'd rather do it in text because it's hard to see everything clearly otherwise. If you have a complex permissions system, it's complex to set up and it's not super intuitive. Compared to AWS, which is a very different system, that aspect of Azure is not very intuitive.

I work in an engineering department so we didn't feel the need to get any help with deployment. If you read the manual, create the sandbox, and test it out you're able to roll it out. It's not that hard. 

View full review »
GP
Project Manager at a government with 10,001+ employees

The initial setup is fairly straightforward. It's one of its advantages over JIRA. It is easier to set up because it is a simple product, whereas JIRA is more complex, more mature and complete, and more difficult to set up.

We have two or three technicians who deploy and maintain this solution.

View full review »
OB
Director | Information Technology / Quality Engineering at a performing arts with 1,001-5,000 employees

With manuals, the implementation is much easier. It is quite straightforward.

We are not doing any kind of maintenance on the solution. We don't need to because it's so fast. We are not paying for everything in terms of infrastructure development. 

View full review »
Syed Fahad Anwar - PeerSpot reviewer
Principal System Developer at HHRC

The initial setup varies depending on the complexity of the workload. Some cases are intricate and require significant time to develop the end product or work item. Conversely, there are simpler, smaller cases that can be completed quickly.

View full review »
AS
Software & Cyber Section Manager at a aerospace/defense firm with 5,001-10,000 employees

I can't speak to the implementation process, as our IT handled it. I was not a part of the initial setup. I can't speak to if it was complex or straightforward, or how long it took to set up.

View full review »
AS
President & CEO at Modern Requirements

It is reasonably straightforward, but it is only as straightforward as the problems that you are trying to solve.

If you are trying to set up the whole chain, then the problem is complex, and the solution has to be as equally complex.

View full review »
MR
Product Owner at Day Insurance

It is effortless to set up DevOps. All Microsoft products are user-friendly and easy to install. If you run into any obstacles, you can use Microsoft library or MSDN for any further help that you need. Microsoft provides a lot of wizards that you can use to solve your problem.

View full review »
VM
Associate Software Development Engineer at Publicis Sapient

The installation is straightforward since it's cloud-based. You can do it yourself. For deployment, we were a team of about 20 people. 

View full review »
CM
CT DDS ENC at SGRE

I am not familiar with the initial setup.

View full review »
Akhilendra Singh - PeerSpot reviewer
Engagement Manager at Capgemini

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

View full review »
EC
IT Project Manager at a energy/utilities company with 10,001+ employees

I wasn't involved in that, but I do know that, just like many tools, there is a learning curve that was associated with that. I have used Jira before, so I had more or less an understanding because it is very similar to Jira, but I know that for other people I work with, it was a completely new concept to use something like this.

For its maintenance, we have a small team. We have about three individuals who do the backend support. So, it is minimal. Obviously, if they have any escalations, then they do go to Microsoft, but we haven't had that happen. It was very minimal. There are plugins that are available to enhance kind of some capabilities of the tool. When we ask for that type of functionality, these three individuals have been able to implement plugins for us.

View full review »
Jeremy Chen - PeerSpot reviewer
Installation Engineer at CTCI

It is a cloud solution, so there is no installation. Its initial configuration takes some time and is not very easy. 

View full review »
TC
Senior .NET Engineer at Advance Storage Products

The basic setup works very quickly, but there are so many things and options.

View full review »
AG
Technical Engineer (Retail Group) at a retailer with 10,001+ employees

Being a SaaS solution, there is no setup.

View full review »
SA
Data Scientist at a computer software company with 1,001-5,000 employees

The installation of Azure DevOps is straightforward because it is a web-based platform. You don't need to create solutions or go through complex setup procedures, making it a user-friendly option. Maintenance for Azure DevOps is minimal, especially if you have automated processes in place. If your solution uses Docker and you have set up automated updates on Docker Hub, the environment can essentially upgrade itself without much proactive maintenance. However, if issues arise, you can make adjustments to the configurations as needed, allowing for a more reactive approach to maintenance.

View full review »
Carlos Arturo Quiroga Quiroga - PeerSpot reviewer
Digital Architecture Corporate Leader at Banco Pichincha

We have good people with a lot of experience in DevOps, so it's not complex for us. The most significant difficulty in adopting the tool was changing our past processes to move to the standardization model we defined with Microsoft DevOps.

View full review »
WJ
Test Advisory, Management & Implementation at a energy/utilities company with 51-200 employees

I didn't see any complexity in the setup because everything is from Microsoft. The development tools and operation tools are coming from one shop, Microsoft, so it's easy to connect, plug in, and establish all those things. For Google Cloud or AWS, it's different because they use different tools in order to achieve what Microsoft is trying to achieve. For example, the CI/CD Pipeline.

Even in ALM or in the DevOps tool, it's initially a one-time setup.

View full review »
TM
CTO at Southernsoft Technologies

The initial setup is pretty straightforward.

View full review »
PS
Application Architect at a manufacturing company with 10,001+ employees

The initial setup is very straightforward. 

View full review »
MM
DevOps engineer at a financial services firm with 1,001-5,000 employees

For any Microsoft product, Active Directory is a prerequisite, and ensuring its availability on the Azure Standard and Database is essential. This configuration is necessary for setting up the application effectively.

View full review »
BJ
Program Test Manager at B and H Designs

I wasn't around when they initially set it up, but the way it is set up, it is too complex. It is probably good for developers, but it is not good for the testing side. 

View full review »
WD
Group Product Manager – Billing and Payments at MultiChoice Group

It was super simple. We just needed a username and a password. The board was pre-setup by our administrator. In fact, we didn't even have to go through any real training, even though the training was available. It is really intuitive to use.

View full review »
Rodrigo Bassani - PeerSpot reviewer
Head Of Technology at Elogroup

We had some initial difficulties, because the solution is not commonly used here. Jira and Microsoft are the most common solutions but it's not usual to use everything inside the platform. It was a cultural change that we implemented here in our team and to convince them was more difficult than to use the platform itself. We used an integrator for deployment but we don't do that in every case. In some of our deployments, hosting the most popular software development languages, like Java or .NET makes it easy to create the deployment mode. But when you have different platforms on development, it's more difficult to configure. We're on an SaaS platform, so deployment was very easy.

View full review »
Eli Harush - PeerSpot reviewer
Customer Solution Manager at DXC

Installing Azure DevOps is pretty straightforward at the installation or admin stage. Deployment time depends on the service on my side, so it's mostly very fast.

View full review »
RC
Vice President at a energy/utilities company with 10,001+ employees

While the installation did seem to be pretty straightforward, I believe it took awhile, even though I am not aware of the specifics involved. We struggled with this initially.

View full review »
SP
Principal Project Manager at Systems Limited

Setting up DevOps is easy. 

View full review »
Abhay Rawat - PeerSpot reviewer
Cloud Engineer at Hanu Software

The product's initial setup phase was not complex, especially since the work items are mostly descriptive, making it an area that everywhere can use easily. The CI/CD part is a bit technical. One can get a hold of the CI/CD part over a period of time, so I don't think it is a difficult task.

Our company's team handled the product's rollout phase. The rollout phase was divided into parts. A single person did not carry out the rollout phase. I only took care of some of its parts. I cannot tell the exact time taken by our company to deal with the product's rollout phase.

View full review »
Mohammad Alyounis - PeerSpot reviewer
DevOps engineer at Q-pros

The initial setup is easy. Deployment typically takes around ten minutes at most. We have set up an automated process that recreates everything, so even if there is damage to the VM or target machine, we can quickly retrieve and redeploy everything ourselves.

We require about two DevOps engineers to maintain Azure DevOps for our company, which has around 400 users in total.

View full review »
Derek Smith - PeerSpot reviewer
Development and Release Compliance Officer at a computer software company with 1,001-5,000 employees

For us, the initial setup was extremely complex due to the multiple organizations we had on the go. We actually had to abandon our initial rollout and rethink the whole process though. 

I'm in compliance, and therefore cannot speak to what the maintenance process is like for the solution. 

View full review »
Krishnakumar Subramanian - PeerSpot reviewer
Technical Director at Alstom Ferroviaria S.p.A.

The initial setup was quite straightforward.

View full review »
HS
Senior Soft Engineer at SECP

The initial setup is not overly complex. It's fairly straightforward. Other than the Java environment variables which lack documentation, it's not complex and easy to follow.

View full review »
MS
Project Manager at Shell Exploration & Production Co.

The initial setup was very straightforward.

The time it takes to deploy is dependent on the type of deployment. Deployment of software, or deployment of the project into the software? 

It took me a week to deploy the project into the software. It's approximately 800 PBIs.

View full review »
Himanshu  Rana - PeerSpot reviewer
Delivery Service Engineer at Hanu Software

It is very straightforward. It was easy for me to deploy. 

The deployment depends on the workloads we have. For example, deployment for setting up Azure DevOps or the application itself isn't the same.

It takes a lot of time to get the setup ready. 

Regarding setup, connecting it to Visual Studio was smooth on both Mac and Windows. Integrations are quite good. 

Deployments depend on the workload. We create virtual machines using Terraform, so it's usually fast, especially when downloading repos from Azure Repos.

View full review »
YN
Owner and Senior Consultant at a tech services company with 1-10 employees

The initial setup is straightforward. It is simple to install.

Other than the initial setup, it does not require any maintenance.

View full review »
DA
DevOps Engineer at Simprints

Setup is not so much of an issue as the product is on the cloud. The services are essentially on demand for the product. What you do with the services is what may take more time and consideration.  

View full review »
MF
C# Developer at a financial services firm with 51-200 employees

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

View full review »
EA
CIO at i cloud seven

The solution is easy to install and it took us three months to implement. This includes the support for our teams and for them to come up with their strategy to manage our projects.

View full review »
BB
Director of Strategy at a financial services firm with 1,001-5,000 employees

I wasn't part of the conversion from Jira to DevOps but it was a painful process. We lost data, things didn't map. My Scrum Master who used it was not happy with the process.

View full review »
LB
Software Architect at a mining and metals company with 10,001+ employees

The initial setup is easy.

View full review »
HN
Software Architect at EML

We did not find the initial setup to be complex. The implementation is straight forward. 

Deployment is quick and typically only takes a few days or so.

We have ten people that handle maintenance. They are in different parts of the world. We have two in Australia, for example, and two in the USA.

View full review »
IG
Senior Director at Cloud Technovation

The initial setup was straightforward.

View full review »
it_user1101249 - PeerSpot reviewer
Senior Project Manager at a financial services firm with 5,001-10,000 employees

The initial setup for this solution is quite easy.

View full review »
LO
Manager of Information Technology Services at a government with 501-1,000 employees

Installing Microsoft Azure DevOps is straightforward. You can have everything set up in three or four hours. It's pretty simple.

View full review »
Johan Bester - PeerSpot reviewer
Director at Rand Merchant Bank

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.

View full review »
KA
Chief Operating Officer Executive at a cloud provider with 11-50 employees

It's average, because we need to research what we are trying to achieve, and the platform has rich functionality. This is a good thing, but it can also mean setup is very complicated. However, we usually find that after testing more, we find our way around what we are trying to achieve.

View full review »
Ismail Kiswani - PeerSpot reviewer
Manager at Al-kiswani

The initial setup is straightforward, it's a cloud service, so it's plug and play.

View full review »
SG
Senior Project Manager at a marketing services firm with 10,001+ employees

The initial setup was straightforward. While we were migrating, we had training from Microsoft, which was helpful.

View full review »
SC
Works at a energy/utilities company with 10,001+ employees

The initial setup is straightforward. We've been using Microsoft products for a while. 

View full review »
FC
Cloud Solution Architect at a tech services company with 201-500 employees

The initial setup is very simple and straightforward. It is not difficult or complex. 

We use the online version. We don't have to deploy the tool. We don't have to put in a lot of effort as we already have the pipelines in the TFS. We just move it to Azure DevOps. 

View full review »
KA
Chief Operating Officer Executive at a cloud provider with 11-50 employees

Setting up Microsoft Azure DevOps was easy.

View full review »
JS
Practice Director, Global Infrastructure Services at a computer software company with 10,001+ employees

It is a cloud solution, and there is no installation. You just start using it.

We have one or two admins per project for deployment and maintenance.

View full review »
BG
Chief Digital Officer (CDO) at a financial services firm with 201-500 employees

The initial setup wasn't complex. It was pretty straightforward. We didn't run into any issues that complicated the process of implementation.

View full review »
OH
Enterprise Agile Coach at Knowit Require

The initial setup for this solution is much easier than for that of JIRA.

View full review »
Zeeshan Arshad - PeerSpot reviewer
DevOps Engineer at a tech services company with 51-200 employees

It is straightforward. It is not that complex.

In terms of maintenance, we only do maintenance when we have new upgrades. Other than that, we don't need to maintain it much. We have optimized the TFS and Azure DevOps database, and we have done indexing and optimized it. It is pretty good.

View full review »
MN
Trainer at a training & coaching company with 51-200 employees

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.

View full review »
AS
Technical Sales Manager at Skhomo Technologies

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.

View full review »
RM
Release Engineer at a computer software company with 11-50 employees

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

View full review »
JM
IT System Manager at a financial services firm with 1,001-5,000 employees

The initial setup is straightforward. We just implement it from the cloud. We took it and configured it with our local website infrastructure, so there was nothing much to do.

View full review »
RC
Senior Support Analyst at ONS
CH
Product and Systems Director at SPCM

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.

View full review »
SK
CTO at Cantier Inc

Its initial setup was a little complex for us. We had been using TFS for quite some time, and migration was a bit difficult for us. We didn't get great support and response from Microsoft. We had limited resources in terms of support, and that's why it took us longer to figure out how to migrate from TFS.

View full review »
DB
Vice President at a tech services company with 51-200 employees

Setting up Azure DevOps was straightforward. It's easy to use the default templates. Everything is under our control, so it's simple to implement new requirements. We did it ourselves in three days. Since we used the default templates,  we didn't have to change the standard Azure DevOps services. Two people are responsible for deployment and maintenance: DevOps engineer and Release Train Engineer

View full review »
PN
Devops Engineer at a manufacturing company with 10,001+ employees

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

View full review »
KI
Consultant at a computer software company with 11-50 employees

The initial setup is quite easy.

View full review »
SA
Delivery Lead - Agile Coach at a tech services company with 201-500 employees

The installation is straightforward.

View full review »
IR
Lead solution architect at a recreational facilities/services company with 10,001+ employees

The installation of Microsoft Azure DevOps is straightforward. The steps are already in place and one only need follow them. We were able to handle this by ourselves.

The product is deployed to the cloud and we have five developers responsible for this. 

View full review »
CH
Product and Systems Director at SPCM

The initials tup is not complex. It's a very easy, very straightforward process. A company shouldn't have any trouble with implementation. It only takes a couple of hours. It's pretty quick to deploy for DevOps purposes.

View full review »
AS
Senior Business Analyst │ Microsoft Power BI & Power BI App Development at a energy/utilities company with 1,001-5,000 employees

The initial setup is simple.

It was easy to deploy and within a day, I was able to learn it and work on it.

View full review »
IT
Software Architect Consultant at a tech consulting company with self employed

The initial setup for the latest version was very straightforward. The upgrade was quick and lightweight.

View full review »
CC
Head of .NET Department at Evozon

The initial setup is straightforward. The configuration of Microsoft Azure DevOps could be better. The documentation needs to be improved.

View full review »
AK
Project Manager at a computer software company with 11-50 employees

The initial setup was not overly complex. It was pretty straightforward. A company should have too much trouble with it.

View full review »
SK
Tech Lead DevOps (Manager) at a tech services company with 11-50 employees

The initial setup is complex. It really depends on those who are using it in the company and exactly what they're utilizing with respect to tools. It also depends on whether they want to integrate it.

View full review »
HP
Computer engineering student at a educational organization with 501-1,000 employees

It's straightforward. With the cloud solution, there is no installation.

I could create the main console for the project very quickly, with just a name and description and the rest is the default.

View full review »
SK
SDET at a consultancy with 1,001-5,000 employees

I would rate this solution 6 out of 10.

I did have some issues due to our organization, but it would be different for everyone. My advice is to reach out to support if you have any problems.

View full review »
TA
Process Manager at a marketing services firm with 501-1,000 employees

The installation was easy.

We have an IT team of four to manage and deploy this solution.

View full review »
CK
Senior Software Engineer at Xylem

The product is very straightforward to set up. 

The deployment is fast as well. It only took us about 10 to 15 minutes to have everything up and running. 

View full review »
SP
Senior Consultant at CMEx

The initial setup is pretty straightforward. We needed to set up a Microsoft account, and that gives access to the projects. Basically, the IT department or IT administrators take care of the access.

As a member of the team, once access is provided, I can just start using it. It is plug-and-play, as far as I'm concerned.

View full review »
CM
Lead Technical Consultant (Information Technology) at a construction company with 1,001-5,000 employees

The initial setup is straightforward and easy. It takes very little time to deploy.

View full review »
WG
DevOps Manager at a tech services company with 51-200 employees

The initial setup was really easy. I didn't even manage this before, but I'm the one who is running this now, and it's pretty easy. Something that made me a little bit confused was all the permissions you have to give to teams and people. Sometimes it's kind of tricky, but it's understandable.

Lately, the deployment's taking a little bit longer than before. I don't know what happened. I'll say that before our deployments took us maybe a couple of minutes. I didn't even measure that, but now it sometimes takes up to 40 minutes or an average of 30 minutes for each deployment.

View full review »
MG
Partner at a tech services company with 1-10 employees

The installation time of this solution depends on the environment it is being implemented in. We had a couple of projects that took around two weeks of implementation. This included the whole integration of the DevOps and everything together.

View full review »
NE
API | SOA | Integration | Application | Internet of Things Solution Architect at a computer software company with 10,001+ employees

The initial setup is easy. We had a team of three engineers dealing with implementation. 

View full review »
EA
Head of Tourism Development at a tech services company with 51-200 employees

Another team handles the implementation, so I wasn't involved. I'm on the business team. Two engineers are responsible for deploying and managing DevOps. 

View full review »
SM
Managing Director at a tech services company with 201-500 employees

As the solution is cloud-based, installation was not required.

View full review »
MN
Especialista Devops at a tech services company with 201-500 employees

It is very simple to install. Its deployment takes a very short time.

View full review »
MS
System Engineer at a tech services company with 51-200 employees

The initial setup is very simple.

View full review »
Buyer's Guide
Microsoft Azure DevOps
March 2024
Learn what your peers think about Microsoft Azure DevOps. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.