Will Azure SG connector discover all subscriptions &resources hosted in different datacenters?

[Suggy]

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?

[bigfissy]

What then is your question? 

[doug_schulze]

According to the docs and @Anne Marie Duff 's white paper it seems it does not

[Suggy]

Hi @doug_schulze Thanks for sharing the link to that white paper. As per my understanding, SG-Azure-Subscriptions Scheduled Import Job will populate all the subscriptions associated with that tenant and also all the resources across all the data centers will be populated. Only when you want to have a connection to 2nd tenant, one needs to create a new connection.

But you said " it seems it does not"

So I am confused now. @Anne Marie Duff if you could also please clarify here please.

[Anne Marie Duff · Accepted solution]

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

[Suggy]

Thanks a lot for clarifying @Anne Marie Duff  🙂