Microsoft Desired State Configuration review
A portable, open-source DSC CLI for defining and comparing machine state.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Microsoft Desired State Configuration (DSC) is an open-source, self-hosted configuration management platform for developers and administrators who need portable declarative configuration. Its current DSC 3.x implementation is a standalone command-line tool that runs on Linux, macOS, and Windows without a local configuration manager service. Teams describe the desired state of machines and application components in JSON or YAML, then use resource operations to get, test, set, delete, or export configuration state.
The standout capability is its declarative, idempotent model combined with drift comparison. JSON schemas define resources and configuration documents, while custom resources can be authored in multiple programming languages. DSC also supports adapter resources for compatibility with PowerShell DSC resources, giving existing PowerShell-based configurations a path into the newer implementation. Integrations with Azure Machine Configuration, Azure Automanaged VM, and WinGet extend its fit within Microsoft-oriented environments. Developers who value portable documents, extensibility, and command-line execution should find this focus compelling.
DSC is open source and follows a self-hosted deployment model, so teams retain responsibility for operating the configuration workflow around the CLI. The published capabilities focus on desired-state definition, resource actions, schemas, drift comparison, and cross-platform execution rather than patch management or compliance reporting. Organizations seeking those functions as part of the same configuration product should consider an alternative with explicit coverage for them. DSC is a strong choice for teams that want an agentless, policy-as-code approach across Linux, macOS, and Windows, especially when Azure integrations or PowerShell DSC compatibility matter.
Microsoft Desired State Configuration pros and cons
- Where it wins
- Runs agentless across Linux, macOS, and Windows
- Supports JSON and YAML configuration documents
- Compares configuration drift against desired state
- Where it doesn't
- Does not cover patch management
- Does not provide compliance reporting
- Self-hosted deployment requires operational ownership
Microsoft Desired State Configuration 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