- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 11:58 PM
In pattern based discovery, you discover all the subscriptions, Datacenters etc..
but in SG-connector for Azure, I dont see any info related to discovering of the subscriptions, resources across all the Datacenters.
The docs just mention about configuring below details
- Application (client) ID
- Client Secret
- Directory (tenant) ID
With this, will Azure SG connector discover all subscriptions & resources hosted in different datacenters?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2025 06:58 AM
Hi @Suggy,
The SG-Azure-Subscriptions Scheduled Import Job will create a Cloud Service Account CI for each of the Subscriptions associated with a particular Azure Tenant.
All the Resources associated with each of your Subscriptions, regardless of the Azure Data Center (Location) that they exist in, will have a corresponding Target CI created in the ServiceNow CMDB. For example, if you have Azure Virtual Machines created in both the US East and West Europe Azure Locations, Target Virtual Machine CI's will be created for these Azure Virtual Machines in the ServiceNow CMDB. So yes you are correct in your understanding of how the SG-Azure Service Graph Connector pulls resources for your Subscriptions from all the Azure Data Center's that contain Resources.
An yes, if you want to connect to a 2nd Tenant you will need to create a new Connection. The white paper explains how to do this in the Creating Multiple Hardware connections and Creating Multiple Software connections subsections of the C. Installing & Configuring Azure Service Graph Connector on your ServiceNow Instance section of the Whitepaper.
Hoping this helps,
Thanks,
Anne-Marie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2025 12:52 PM
Hi Anne,
Hope you are doing good today. So to clarify upon this point - if an environment has a unique workspace for each subscription (e.g., 50 workspaces, 50 subscriptions), the SGC requires setup of 50 HW & 50 SW connections?
Additionally, may I ask if you have seen successful integration with an envrionment that has a workspace configured to aggregrate data from VMs across subscriptions - similar to AWS Config Aggregrator?
This context would be tremendously helpful! Appreciate it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-30-2024 10:16 PM
Anyone?
