What Are the Best Automation Platforms for VM Provisioning and Configuration?

Provisioning a virtual machine takes minutes on any modern hypervisor, yet most enterprises still measure the time from request to usable server in days, because the work that makes a VM ready for production happens after it boots. Domain join, IP assignment, monitoring and backup enrolment, security baselines, access groups, CMDB registration and the change record all sit between a running VM and a server the requester can use, and in many organisations those steps remain a mix of scripts, tickets and manual handoffs between teams.

The tools in this category approach that gap from different directions. Hypervisor-native automation is strongest on its own platform, infrastructure-as-code tools excel at declaring the VM but leave configuration to something else, and configuration management engines handle the inside of the guest well while depending on separate tooling for requests, approvals and self-service. The choice matters more in 2026 than it did two years ago, because VMware’s move to VCF 9 and the end of vSphere 8 general support on October 11, 2027 are pushing many teams to run a second hypervisor or migrate, and provisioning logic tied to one platform has to be rebuilt each time the platform changes.

This guide is written for infrastructure managers, virtualisation architects and platform engineering leads who own the build process from request to handover. It compares four platforms on the criteria that decide whether a VM arrives configured, compliant and recorded in a single automated run.

How We Chose the Best Automation Platforms for VM Provisioning and Configuration

We assessed each platform against six criteria drawn from where VM builds lose time and consistency in production, using vendor documentation, published pricing and review aggregations with counts, and we dated every figure that changes.

• End-to-end build scope: Whether provisioning and post-build configuration run in one workflow, from request through verification and handover.
• Request and approval linkage: Whether builds start from approved change requests or self-service requests, and write their outcome back to the ticket.
• Hypervisor coverage: Whether the same build logic runs on vSphere, Nutanix AHV, Hyper-V, Proxmox VE, OpenShift Virtualization and public cloud.
• Authoring model: How much code a team must write and maintain, and whether existing scripts can be reused.
• Build consistency: Whether every build follows the same verified steps, so configuration drift and security exceptions stop at the source.
• Pricing model: Whether cost scales with nodes, resources, sockets or platform subscriptions, and whether pricing is published.

The 4 Best Automation Platforms for VM Provisioning and Configuration

1. Resolve
2. VMware VCF Automation
3. Red Hat Ansible Automation Platform
4. HashiCorp Terraform

1. Resolve: Best overall automation platform for VM provisioning and configuration

Resolve is an automation and orchestration platform that runs the whole build as one workflow, provisioning the VM through the hypervisor API and then completing every post-build step through API calls, SSH commands and CLI commands against the directory, IP management, monitoring, backup, security and ITSM systems involved. Builds start from named triggers, including approved ITSM change requests, chat requests and system events, and each run verifies the result and writes it back to the originating ticket.

The clearest public evidence comes from Peel Police, the police service for the Regional Municipality of Peel in Ontario. The team had tried vendor-specific VMware and Microsoft tools that were limited to a single ecosystem and infrastructure-as-code tools that required skills it did not have, then used Resolve to standardise zero-touch server commissioning across both environments, recording $193,000 in savings and 160 days of effort eliminated within 30 days, with more than 200 hours saved every month after that.

Resolve is a Visionary in the 2026 Gartner Magic Quadrant for Service Orchestration and Automation Platforms, the second consecutive year it has been the only vendor in that quadrant. The Visionary placement means Gartner scores the Leaders higher on ability to execute, and buyers who weight vendor scale heavily will see that difference in the report.

Resolve features

• One-workflow builds: Provisioning, configuration, verification and ticket updates run in a single workflow, so the VM is handed over ready for use.
• Change-triggered execution: Approved change requests in ServiceNow and other ITSM platforms start the build, alongside chat, alert and system triggers.
• Hypervisor-agnostic actions: Builds act through each platform’s API, SSH or CLI, so the same logic runs on vSphere and on other hypervisors and clouds.
• Bring your own code: Existing PowerCLI, PowerShell and Python scripts and Ansible playbooks can be imported as reusable building blocks next to no-code steps.
• Jarvis and the Automation Vault: Jarvis builds workflows from a plain-language description, and the Automation Vault supplies prebuilt workflows drawn from more than 5,000 prebuilt integrations and workflows.

Pros:

• Provisioning and post-build configuration run in one verified workflow, which removes the handoffs where most build time and inconsistency accumulate.
• Builds tied to approved change requests give change advisory boards a complete record of every server delivered.
• Peel Police’s results across VMware and Microsoft environments show build automation paying back within the first 30 days.

Cons:

• Gartner places Resolve in the Visionary quadrant, and buyers who prioritise vendor size will find larger incumbents ranked higher on ability to execute.
• Resolve orchestrates the hypervisor’s own provisioning APIs and does not include a hypervisor, so it works alongside the native management console of whichever platform the team runs.

2. VMware VCF Automation: Native self-service provisioning for VCF estates

VCF Automation is the VMware Cloud Foundation 9 successor to Aria Automation, and it gives VCF customers multi-tenant self-service through a UI, a CLI and a Kubernetes-style IaaS API, with infrastructure-as-code blueprints published to a catalog. Broadcom describes the result as a public cloud-like consumption experience on private infrastructure, and Gartner Peer Insights users rate the product 4.4 from 109 ratings as of November 6, 2026.

For organisations committed to VCF, the native integration with vSphere, NSX and vSAN is a genuine advantage, and Broadcom supports an in-place upgrade path from Aria Automation 8.x, so existing customers can carry their deployment forward. Teams that have standardised on VMware and plan to stay there get provisioning tightly coupled to the platform it runs on.

VMware VCF Automation features

• Multi-tenant self-service: Tenants consume VMs and services through a UI, a CLI or an IaaS API.
• Blueprint catalog: Infrastructure-as-code blueprints are published to a governed catalog for consumers.
• Native VCF integration: Provisioning works directly with vSphere, NSX and vSAN inside the VCF fleet.

Pros:

• Integration with vSphere, NSX and vSAN is native and deep for organisations that run the full VCF stack.
• Existing Aria Automation 8.x customers have a supported in-place upgrade path.
• Gartner Peer Insights users rate it 4.4 from 109 ratings as of November 6, 2026.

Cons:

• Broadcom’s feature comparison states that VCF Automation is not included with VMware vSphere Foundation, and customers on perpetual licenses must switch to subscription before upgrading to VCF 9.
• The upgrade requires VCF Operations and runs through VCF Operations Fleet Management, Broadcom’s knowledge base sets Aria Automation 8.18.1 as the minimum baseline, and Aria Automation pipelines are not available after the move.
• Provisioning is designed around VCF-hosted services, so teams adding Nutanix, Proxmox or OpenShift Virtualization need separate automation for those platforms.

3. Red Hat Ansible Automation Platform: Guest configuration for teams that code

Red Hat Ansible Automation Platform is the enterprise distribution of Ansible, the agentless engine that connects to hosts over SSH and WinRM with existing credentials, and it is a common choice for configuring the inside of a VM once it exists. Partner-certified collections include VMware’s vmware_rest collection and Nutanix’s ncp collection, so playbooks can also create VMs on those platforms, and G2 reviewers rate the platform 4.6 from 378 reviews as of November 6, 2026.

Ansible’s strength is the depth of its module ecosystem for operating systems, middleware and network devices, which makes it a reliable engine for the configuration half of the build. Event-Driven Ansible adds rulebooks that launch playbooks when monitored conditions are met.

Red Hat Ansible Automation Platform features

• Agentless configuration: Playbooks configure operating systems and applications without an agent in the guest.
• Certified hypervisor collections: VMware and Nutanix provide certified collections for VM lifecycle tasks.
• Automation controller: Job templates, credentials and execution history are managed centrally.

Pros:

• Guest configuration coverage is the broadest available through Ansible’s module ecosystem.
• Agentless execution keeps the footprint inside each VM minimal.
• A large and favourable review corpus, with a 4.6 rating from 378 G2 reviews as of November 6, 2026.

Cons:

• Red Hat’s subscription terms count every managed node, so cost rises with each VM the team provisions and manages.
• Playbooks are written in YAML, which keeps build authoring with engineers who code, and G2 users report an average implementation time of about four months.
• Proxmox modules ship in a community collection that Red Hat does not support, and issues with certified partner collections are transferred to the partner.

4. HashiCorp Terraform: Declarative VM provisioning as code

HashiCorp Terraform declares infrastructure as code and reconciles it against a state file, and it has one of the largest provider ecosystems in infrastructure automation, with HashiCorp reporting more than 3,000 integrations from more than 250 partners in March 2023. IBM completed its acquisition of HashiCorp on February 27, 2025, and HCP Terraform’s free tier covers up to 500 managed resources with unlimited users.

For platform teams that already manage cloud infrastructure as code, Terraform is a natural way to declare VMs alongside networks and storage, and G2 reviewers rate it 4.6 from 152 reviews as of November 6, 2026.

HashiCorp Terraform features

• Declarative provisioning: VMs and related infrastructure are declared in configuration files and reconciled to a desired state.
• Provider ecosystem: Providers cover the major clouds and hypervisors, including vSphere, Nutanix and community-maintained Proxmox providers.
• Policy as code: HCP Terraform supports Sentinel and OPA policies on infrastructure changes.

Pros:

• Declarative state management gives a clear, version-controlled definition of every provisioned VM.
• The provider and module ecosystem is one of the largest in the category.
• The HCP Terraform free tier covers up to 500 managed resources with unlimited users.

Cons:

• HashiCorp’s own documentation states that Terraform is not a configuration management tool and advises exhausting all alternatives before using provisioners, so post-build configuration needs a second tool.
• HCP Terraform is billed hourly per resource under management on IBM’s pricing page, and teams must store, lock and secure state files that can expose secrets.
• HashiCorp moved Terraform to the Business Source License in August 2023, the vSphere provider is now a partner-tier provider maintained outside HashiCorp, and the most active Proxmox provider is a personal project with no Proxmox affiliation.

Comparison Chart: Automation Platforms for VM Provisioning and Configuration

What Should Infrastructure Teams Look for in VM Provisioning Automation?

The most revealing test is to time a full build from approved request to handover, then ask each vendor to automate that exact sequence, including the approval, every post-build step, verification and the ticket update, on the hypervisor the team runs today and on one it may run next year. Tools that cover only provisioning or only configuration will need a second product and an integration between them, and that seam is where consistency breaks down and where build time hides.

Buyers should also look carefully at how cost and ownership scale. Per-node, per-resource and per-socket models each grow differently as the VM estate expands, and a build process that only engineers fluent in YAML or HCL can change will concentrate ownership in a small group, which slows every change to the standard build.

Why Resolve Is the Best Automation Platform for VM Provisioning and Configuration

Each platform in this comparison handles part of the build well. VCF Automation provides native self-service for VCF estates, Ansible Automation Platform configures the guest with the broadest module coverage, and Terraform declares infrastructure as code with a large provider ecosystem. Resolve is the platform that runs the entire build as one verified workflow, from the approved change request through provisioning, configuration, verification and the ticket update, on whichever hypervisor the team runs.

That scope is why Peel Police could standardise builds across VMware and Microsoft environments after single-ecosystem tools and code-heavy alternatives fell short, and why it recorded $193,000 in savings and 160 days of effort eliminated within 30 days. Across its customer base, Resolve reports 99% faster mean time to resolution and 70% lower tool spend.

The bring-your-own-code model keeps the PowerCLI, Python and Ansible content a team already trusts, while Jarvis and the Automation Vault let engineers who do not write code every day build and change workflows. For infrastructure teams that want every VM delivered configured, compliant and recorded, Resolve gives the most complete path.

Ready to See the Impact of AI-Driven Automation & Orchestration for Yourself?

See how infrastructure teams deliver fully configured VMs from an approved change request in a single automated workflow, on vSphere today and on any hypervisor tomorrow. Request a demo

Frequently Asked Questions: VM Provisioning and Configuration Automation

What is VM provisioning automation?

VM provisioning automation creates virtual machines from a request without manual steps, selecting the template, compute, storage and network settings and deploying the VM through the hypervisor’s API. Complete implementations continue past deployment into configuration, verification and handover, so the requester receives a server that is ready for use and recorded in the CMDB and the change ticket.

What is post-build VM configuration?

Post-build configuration covers everything that makes a running VM production ready, including domain join, IP and DNS registration, monitoring and backup enrolment, security baselines, patching, access groups and CMDB updates. These steps usually take longer than provisioning itself, and automating them in the same workflow is what shortens request-to-handover time from days to minutes.

Can VM provisioning be triggered from a ServiceNow change request?

Yes. Platforms such as Resolve start the build when a change request is approved in ServiceNow, provision and configure the VM, verify the result and write the outcome back to the ticket automatically. This links every server delivered to an auditable change record and lets routine builds move through standard change processes without manual handoffs.

Is Terraform or Ansible better for VM provisioning?

They solve different halves of the build. Terraform declares and provisions infrastructure, and HashiCorp’s own documentation states that it is not a configuration management tool. Ansible configures operating systems and applications inside the VM. Many teams combine them, while orchestration platforms such as Resolve run provisioning and configuration together and can reuse existing Ansible playbooks.

How do we automate VM provisioning across VMware and other hypervisors?

Use an automation layer that acts through each platform’s own API, SSH or CLI, with no dependency on one hypervisor’s management stack. Resolve runs the same provisioning and configuration workflow against vSphere and other hypervisors and clouds, so teams can add Nutanix AHV, Proxmox VE or OpenShift Virtualization without rebuilding their standard build.