Azure Cloud Discovery (Single/Multi-Tenant) + Dynamic VMware Follow-Up

AdhithyaR
Tera Contributor

4 weeks ago

I’m seeking guidance on defining Cloud Discovery for the following scenarios:

  1. I have two cases to consider — one involving multi-tenant IDs and the other a single-tenant ID.

  2. For example, in the single-tenant scenario, I have one Azure Tenant ID with 100 subscriptions. Each subscription contains its own resource groups, network gateways, hardware types, VMs, etc.

  3. I want to set up Cloud Discovery to cover all subscriptions, followed by VMware discovery.

  4. Let’s take one case: Cloud Discovery for Subscription1 is named "Azure ABC Subscription" with the discovery type Cloud Resource. This subscription has no VM resources, but I have also scheduled a VM Discovery named "Azure ABC Subscription VMware" with the discovery type Configuration Item.

  5. My goal is to configure discovery so that it dynamically checks for VMware resources within a subscription — if VMs are found, it should proceed with the second discovery; if not, it should skip the VMware discovery to avoid errors like "Discovery range is empty".

0 Helpfuls
  • 563 Views
2 REPLIES 2

Ram Devanathan1
ServiceNow Employee
ServiceNow Employee

3 weeks ago

For Azure you can setup azure management groups per tenant add the subscriptions into the mgmt groups, and add these azure mgmt group ID to the schedule (normally you would add subscription ID in the schedule). use cloud discovery workspace this has a wizard to lead you through.

 

set the property glide.discovery.cdu.auto_refresh_sub_accounts_and_ldcs property to true to get all subscriptions in mgmt group everytime scheduled discovery runs.

more details in this kb https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0961449

 

for vmware discovery you need to connect to the vcenter - even if it is vmware on azure. there's no direct connect via azure api into vmware setup.

 

HTH

Ram

0 Helpfuls

AJ-TechTrek
Giga Sage
Giga Sage

3 weeks ago

Hi @AdhithyaR ,

 

Yes, you can configure Cloud Discovery to cover all subscriptions automatically at tenant level. Then, use Discovery Orchestration Rules to dynamically check if VMs exist in a subscription → if yes, trigger VMware Discovery; if no, skip, so you don’t hit “empty range” errors.

 

Solution also cover in another post refer this - https://www.servicenow.com/community/itom-forum/guidance-on-tenant-level-azure-cloud-discovery/td-p/...

 

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025

0 Helpfuls