A permissions related error may be encountered when attempting to deploy a virtual machine from an existing template. The deployment operation fails, and the virtual machine is not provisioned successfully.
The following error message is displayed in the vCenter UI:
Error: Permission to perform this operation was denied. Message: NoPermission.message.format
In the vCenter Server Appliance, the /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log may contain entries similar to:
YYYY-MM-DD HH:MM [DEBUG] https-jsse-nio-9443-exec-9 70013216 100364 200029 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl
Will determine whether to retry managed method reconfigure for moref ManagedObjectReference: type = VirtualMachine, value = vm-###, serverGuid = #######-####-####-####-#########.
The failure was com.vmware.vim.binding.vim.fault.NoPermission: Permission to perform this operation was denied.
VMware vCenter Server 8.x
VMware ESXi 8.x
This error occurs when the user account performing the virtual machine deployment does not have the necessary privileges on one or more vCenter objects involved in the operation.
The following objects are typically part of the virtual machine deployment workflow:
Virtual machine template
Destination datastore
Target virtual machine folder
Host, cluster, or resource pool
Network configuration
Datacenter or vCenter Server root objects
If the account lacks adequate permissions on any of these objects, vCenter Server will deny the deployment operation and display the "NoPermission" error.
Perform the deployment operation using an account with administrative privileges. If the deployment succeeds, this confirms the issue is related to insufficient permissions for the original user account.
Log in to the vCenter UI.
Navigate to Administration → Roles → Global Permissions
Review the permissions assigned to the user or group performing the deployment.
Alternatively, check permissions on each object involved in the deployment process (template, folder, datastore, network, cluster, etc.).
Ensure that permissions are correctly applied at the required object level (e.g., datacenter, cluster, folder, datastore).
Confirm that the “Propagate to children” option is enabled where applicable.
| Object | Required Privilege Path |
|---|---|
| VM Template | Virtual machine → Inventory → Create from existing Virtual machine → Configuration → Read configuration |
| Destination Folder | Virtual machine → Inventory → Create new Virtual machine → Inventory → Register |
| Host / Cluster / Resource Pool | Resource → Assign virtual machine to resource pool |
| Datastore | Datastore → Allocate space |
| Network | Network → Assign network |