Azure Service Operator review
An open-source operator for managing Azure infrastructure through Kubernetes workflows.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Azure Service Operator is an open-source Kubernetes operator for teams that want to provision and manage Microsoft Azure resources alongside Kubernetes applications. It uses Kubernetes custom resources and kubectl, allowing infrastructure configuration in YAML or JSON and lifecycle ownership through Kubernetes references. The active v2 project supports more than 150 Azure resource types, including Redis Cache and PostgreSQL, making it a fit for Azure-focused platform teams standardizing infrastructure workflows around Kubernetes.
Its central capability is reconciliation: Azure Service Operator compares declared resource configurations with actual Azure state and works to keep them aligned. Teams can import existing Azure resources with asoctl, export Azure-generated values to Kubernetes Secrets or ConfigMaps, and choose among Azure Workload Identity, service principals, and managed identities. Kubernetes, kubectl, Helm, FluxCD, and Argo CD integrations also support GitOps-oriented operating models, particularly where infrastructure and application delivery already share a Kubernetes control plane.
The project is open source, and its execution and state management are self-hosted. That model gives teams a Kubernetes-native way to manage Azure resources, but it also makes a Kubernetes cluster a prerequisite rather than an optional interface. Azure Service Operator is therefore suited to organizations already operating self-hosted Kubernetes and committed to Microsoft Azure. Teams seeking multi-cloud infrastructure coverage or a service that runs without self-hosted Kubernetes should choose a different infrastructure-as-code tool. The current entry describes ASO v2; Azure Service Operator v1 is deprecated and unmaintained.
Azure Service Operator pros and cons
- Where it wins
- Manages more than 150 Azure resource types
- Reconciles declared and actual Azure resource state
- Supports FluxCD, Argo CD, imports, and identity options
- Where it doesn't
- Supports Microsoft Azure only
- Requires a self-hosted Kubernetes cluster
- State management and execution remain self-hosted
Azure Service Operator fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update