Assuming that you have no networking issues here, agent must be able to connect to:
- global.handler.control.monitor.azure.com
-
<virtual-machine-region-name>
.handler.control.monitor.azure.com (example: westus.handler.control.azure.com) -
<log-analytics-workspace-id>
.ods.opinsights.azure.com (example: 12345a01-b1cd-1234-e1f2-1234567g8h99.ods.opinsights.azure.com)
Nope, installation of an Azure Monitoring agent on an endpoint doesn't do anything by default. Microsoft loves this extra config crap. IMO ideally, you would just install, have a GUI to lead you through config on where to point the tenant and set ups these pieces for you but you'll need to:
- Create a monitored object (MO) in Azure
- Then associate the data collection rules (DCR) to the object
Then there's all sorts of exceptions....
- No standalone boxes
- No laptops (or not ideal)