Azure SGC for On-Prem Azure ARC Servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
We've been tasked to look into a use-case to discover several on-prem ARC servers. None are currently virtual. Our enterprise is not currently using horizontal discovery in any way. This particular team is not allowed to use Agent Client Collector on their servers either.
In doing research, I'm having a tough time understanding if the connector for Azure will populate these bare-metal servers or not, or if a different tool would be needed. I've seen some documentation that leads me to think it will, some that seem to say it will as long as we use the mid-server as the medium. But I'd love to get some confirmation before we begin the testing.
When to use the Azure Service Graph Connector for Discovering your Azure Resources
You should use the Azure Service Graph Connector for Discovering your Azure Resources for the below Use Cases:
You don't want to have a MID Server as a requirement for your overall Solution Architecture
You don't want to (or can't) use ITOM Horizontal Discovery in your overall Solution Architecture.
You don't want to (or can't) use Agent Client Collector for Visibility in your overall Solution Architecture.
You want the below data to be populated in the Target CI's that get created:
- Installed Software running on Azure Virtual Machines
- Running Process & TCP Connections on Azure Virtual Machines
Cloud Discovery provides the ability to get High Level Azure Virtual Machine Metadata only. For cases where Horizontal Discovery and Agent Client Collector for Visibility are not options, but you need to get Installed Software, Running Process or TCP Connection data from your Azure Virtual Machines, then the Azure Service Graph Connector is recommended.
