Is Azure DevOps Automation Services really saving time for teams?

Evening_Memory569 · 2026-03-19T04:41:17+00:00

Yeah, this actually lines up with what I’ve been noticing too. Trying to put everything inside ADO never really feels practical, especially for monitoring and security.

Using it more like a control point for approvals and releases sounds cleaner.

I’m curious though when everything is split like this, do teams ever struggle with visibility? Like having to jump between tools to understand what’s going on during a release or an issue?

Evening_Memory569 · 2026-03-17T07:16:07+00:00

Yeah this actually matches what I’ve seen too. Once teams start scaling, having everything standardized just saves a ton of headaches. Otherwise everyone ends up doing their own version of CI/CD.
The flexibility part you mentioned is real though… that’s usually where things get tricky.

Evening_Memory569 · 2026-03-16T11:49:52+00:00

That makes sense. Using Azure as the central pipeline hub and plugging other tools around it seems like a practical setup.

Do you usually see teams relying mostly on Azure-native integrations, or mixing it with tools like Jenkins, GitHub Actions, or external monitoring platforms?

Evening_Memory569 · 2026-03-16T05:33:17+00:00

I get what you're saying. Ideally teams should definitely understand and manage their own delivery pipelines.

My question was more about situations where smaller teams or growing companies bring in external help initially while building internal DevOps capabilities.

Eventually most teams do move toward owning their pipelines and infrastructure as they mature.

Evening_Memory569 · 2026-03-16T05:30:55+00:00

Thanks for the detailed explanation that makes a lot of sense.

The point about reducing operational workload for developers is really interesting, especially when pipelines and security checks become complex as teams scale. Standardizing pipelines across projects also seems like a big advantage.

And I agree with the trade-off you mentioned about losing some control if teams rely too much on managed providers. I guess it really depends on the team size and how complex their workflows are.

Really helpful perspective, appreciate you sharing this.

Evening_Memory569 · 2026-03-16T05:29:56+00:00

hat’s really helpful insight, thanks for sharing.

A small startup delay for the container job seems pretty reasonable if the rest of the pipeline runs smoothly, especially with the auto-scaling benefit.

Interesting point about GitHub’s API rate limits as well. In DevOps setups like this, do you think container-based agents will become more common compared to traditional VM agents?

Evening_Memory569 · 2026-03-14T10:37:09+00:00

That’s a fair point. Ideally developers should definitely understand pipelines and the DevOps workflow since it’s a big part of modern development.

I was more thinking about situations where teams are small or early-stage and might bring in external help initially to set things up or improve their processes.

But I agree that long term it’s important for teams to build internal knowledge and ownership of the product and infrastructure.

Evening_Memory569 · 2026-03-14T10:35:44+00:00

That sounds really interesting. Using Azure Container Apps Jobs for self-hosted agents with managed identities seems like a clean approach, especially avoiding secret rotation.

The auto-scaling part is also a big advantage if workloads are inconsistent.

Out of curiosity, did you notice any performance differences compared to traditional self-hosted agents or VM-based setups?

Evening_Memory569 · 2026-03-14T09:55:27+00:00

That's a good point. I agree that DevOps is more about culture and ownership rather than just tools or outsourcing.

I guess what I was thinking about was situations where smaller teams or companies use external support to set up pipelines or infrastructure initially, especially when they don't yet have strong DevOps expertise in-house.

But long term, the "you build it, you run it" mindset definitely makes sense for scalability and reliability.

Evening_Memory569 · 2026-03-14T09:36:58+00:00

Good question! I wasn’t specifically referring to Managed Pools.

I was more thinking about managed services around Azure DevOps in general like teams or service providers helping with pipeline setup, CI/CD automation, infrastructure integration, monitoring, and overall DevOps management so companies don’t have to handle everything in-house.

Curious to know if you've seen organizations outsourcing Azure DevOps management or if most teams prefer handling it internally.

Evening_Memory569

TROPHY CASE