Integrating VMware vSphere directly via PowerShell requires you to know upfront exactly what Datastores, Hosts, VMs, and Properties you want to interact with before you can start configuring your vSphere calls.
The Integration Module for VMware vSphere provides a set of ready built activities for integrating with vSphere from within Azure Automation and the Kelverion Runbook Studio. These are forms driven activities which allow you to define interactions with vSphere without having to write any PowerShell code.
When the Integration Module is used from within the Runbook Studio you also get the benefit of the Smart Discovery. You create a Smart Connection to a vSphere instance and the IM will query the Instance to find out all the Datastores, Clusters and Hosts in that Instance and presents you a list of the available Items. You then select a VM and the IM will automatically configure its self to show all the Fields for the VM as a Parameter for the command and the preconfigured value for the Fields where appropriate.
This means you don’t need to be an expert on the vSphere configuration before you can interact with it because the IM will tell you how the system is configured and then you just configure the activity to achieve the interaction you require.
The Integration Module delivers activities to automate IT Functions such as:
Automated Provisioning Automate the creation of resources in vSphere directly from Service Requests or automated resource scaling.
Delete VM Retire Virtual Machines to free up resources and reclaim licenses for re-use.
The Key capabilities added to your Runbook Studio solution include: Automatically builds and executes the necessary VMware vSphere interactions without the user having to write or understand PowerShell
Simplifies Runbook design by automatically mapping vSphere properties to input properties, filters, and published data items
Smart Connections establish a reusable link between the Runbook Studio and a specific vSphere instance. You can create as many Smart Connections as you require, specifying links to multiple vSphere instances.