How to connect multiple VMs of multiple regions to an OMS workspace.

[Prashant Sharma]

I have multiple virtual machines in multiple regions or different resource groups. so how to connect all the VMS into the OMS workgroup. it is possible to connect all VMS using a PowerShell script?

[#2]

@Prashant SharmaA computer in any region, subscription, on-premises or other cloud provider can send data to a workspace.  For an Azure VM, go into the workspace you want them to connect to and Virtual Machines under Workspace Data Sources.  Select the VM and connect.  

I did a series of videos on Log Analytics.  I cover the information above as well as how to setup Azure and Non-Azure servers.  https://www.youtube.com/playlist?list=PLnWpsLZNgHzVXXyN9a0jm9xNNDrikHf8I

[#3 · Accepted solution]

@Travis Roberts  thank you for this Travis. but I can not connect the single-single VM to the workspace.

I need a script (PowerShell script). so i can fill the VM name and resource group into the excel sheet and run that Excel sheet through the PowerShell script.

[#4]

@Prashant Sharma Below is a link to the command line setup.  Possibly use this with Invoke-Command?  Another Azure option would be to used a custom script extension to push the settings.  DSC would also be an option.  Best bet would be to push it out with SCCM or some other application deployment solution.

FWIW, OMS settings can be deployed as part of an ARM template.

https://docs.microsoft.com/en-us/azure/azure-monitor/platform/agent-windows#install-the-agent-using-...

[#5]

@Travis Roberts Can you have a machine connect to multiple workspace? I dont think this is possible.

Also, we have a customer with some machines connected to the wrong log analytics workspace so I will change it but I will need to re-install the agent right? I noticed the agent has no option to update the workspace ID (unfortunately)

Any help appreciated.

P.S. I follow you on Udemy. Keep up the good work :)

[#6]

@matrixman  The host pool maps to one workspace.  You can't connect to multiple.

For Azure VM's it's best to remove the agent and re-add it for the correct log analytics workspace.  I suspect there is a way to do that programmatically with PowerShell if here are a lot of them.  

Thanks