Hi,

• You can go with push installations after meeting prerequisites here Requirements for Push Installing Commvault Cloud Software Onto a Server That You Want to Back Up (metallic.io)

• or Install agent manually on the VM via guide Configuring Backups for File Server in Microsoft Azure (metallic.io)
• Then you can simply use installer file obtained here to install without guide, just by triggering .exe installer on the VM. The only thing you need provide during installation is auth code available in Webconsole under Manage > Company. 
• to Keep VM and File System agent entries as a one backup “client” please remember to backup entity as a VM first, a then deploy the agent (if it’s already protected on the daily basis additional VM level backup are not required, it’s valid for new resources only).

In the Security IQ dashboard, there’s an option to sign up for anomaly related alerts too by clicking on the “bell” icon in the top right corner. It needs to be done by user directly. 

Hi @Steve B , 

I see the unusual file activity is supported for File systems and Endpoints only.  So for VMs you need to install the File system agent  and try the same by taking at least 1 backup using the Agent. 

“The Unusual file activity panel also displays anomalies in the file types of backed up files on Windows clients computers. The anomaly is displayed when there is a mismatch in the file type of the file and the file extension.”
Refer: https://docs.metallic.io/metallic/unusual_file_activity_report.html

Second, The Seeding package should allow you to set restore only agents. However as the backup is required using Agent for File activity, it might not help you.