The best DevOps solution for Azure/Microsoft ecosystem
May 24, 2023

The best DevOps solution for Azure/Microsoft ecosystem

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Azure DevOps Services

I use Azure DevOps to schedule runs for automated test cases. It provides the feature to share results via Webhooks. So the team is able to know about the status of the test runs by alerts configured via Webhooks.It helps to track builds and perform dependency checks. It helps to create builds and deploy them.
  • Dependency check for builds
  • Deploy the builds in the respective environments
  • Run the tests in different stages within Azure DevOps
  • When I cancel a release, it asks for adding comments however, finding that comment later is difficult, the automated emails shared for each build do not contain the comments as well.
  • The UI/UX can be improved to be more intuitive
  • Automatic build creation
  • Automatically running tests against the specific environments
  • Identifying issues with the build
  • Deployment in the cloud environments
  • Automating the build creation, verification and deployment saves a lot of money
  • Ability to create the pipelines for specific needs to tailor the needs of the team helps to keep everything organized and in order
  • Scheduling helps to save productive time
As a cloud services user of Azure, using Azure DevOps made sense because it has the most support tailored for Azure ecosystem.

Do you think Azure DevOps Services delivers good value for the price?

Yes

Are you happy with Azure DevOps Services's feature set?

Yes

Did Azure DevOps Services live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Azure DevOps Services go as expected?

Yes

Would you buy Azure DevOps Services again?

Yes

Scenarios where it is suited:

1. Separating the builds into specific purposes into different pipelines
2. Automatically performing dependency checks, deploying the build and running tests on it
3. Tracking the status of different stages

Scenarios where it is less appropriate:

1. Companies which work on the waterfall model
2. Companies that don't utilize CI/CD

Azure DevOps Services Feature Ratings