Azure DevOps Organization
Does ZopNight manage Azure DevOps Organization?
Azure DevOps organizations bill per paid user seat and per parallel pipeline job, not per compute hour, so the waste hides in seats nobody uses and in self-hosted CI agent VMs that idle between builds. ZopNight discovers each organization via Resource Graph and ties its charges back to the owning Azure subscription.
Rules that fire on Azure DevOps Organization
No active rule family targets Azure DevOps Organization today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery and cost visibility only. |
Azure DevOps provides repos, pipelines, boards, and artifacts, billed per user and per parallel pipeline job. Unused paid user seats and idle self-hosted agent VMs are its typical cost leaks.
Seats and parallel jobs, not compute hours
Azure DevOps billing follows people and concurrency rather than infrastructure: paid user seats accrue per user, and pipeline capacity is bought as parallel jobs, Microsoft-hosted or self-hosted. None of it responds to how much anyone actually commits, builds, or deploys in a given month. A seat assigned to a contractor who rolled off in the spring bills like a seat used daily, and an extra parallel job bought for one crunch keeps billing long after the crunch ended.
How DevOps spend joins the subscription picture
Discovered via Azure Resource Graph for inventory and billing linkage, connecting DevOps spend to the owning subscription. That linkage matters because DevOps charges reach the Azure bill only through the organization’s billing configuration, and without the connection the spend floats free of any accountable owner. The organization itself is not schedulable (there is nothing to stop), so ZopNight’s role here is inventory and cost attribution.
Where DevOps organizations leak
The first leak is seats: Basic access granted broadly during onboarding and never reclaimed as people change teams or leave. The second is parallel jobs sized for a past peak in build traffic. The third sits just outside the organization boundary: self-hosted agent pools backed by VMs that idle around the clock waiting for builds that only arrive during roughly 45 working hours a week. Those agent VMs are ordinary schedulable compute, and pairing the organization with its agent fleet is where the real recoverable money usually lives.
Reviewing the organization from the portal
Azure portal → Azure DevOps organizations shows the organizations linked to the subscription. Seat counts, access levels, and parallel-job purchases live at dev.azure.com under Organization settings, in the Billing and Users sections.