As we saw in a previous post, for local servers, you need to download and install the Microsoft Monitoring Agent in order to feed data from that server to OMS. For Azure VMs its even easier. Check this out.
Select the OMS workspace you’ve been working with. In my case, its the mickeygmms workspace.
In the menu for the workspace blade, select Virtual Machines
This will provide you a list of the virtual machines in Azure you have access to. Select the machines you want to onboard into OMS.
Then click the Connect button at the top of the blade.
This will automatically start the process of installing the agent and configuring it for the OMS workspace.
And here is what you will see once it is finished.
You have to admit that is a quick and easy way to install the agent on a large number of Azure VMs!
At this point, I’ve created my workspace, and I’ve added both local servers and Azure servers to my OMS environment. But the only information being returned is “heartbeat” pings, indicating whether the servers can communicate with OMS or not. To really start seeing the power of OMS, I need to start retrieving log and/or event data, so I can start seeing what is happening on my machines. The next few posts will show you how that works.