---
title: "Performing vDiscovery on Virtual Networks"
canonical: "https://docs.infoblox.com/space/vniosazure/37486690/Performing%20vDiscovery%20on%20Virtual%20Networks"
format: markdown
---
> ⚠️ **Note**
> ⚠️ 
> ⚠️ <span style="color: #000000">vDiscovery can be performed only on virtual networks in Azure public cloud and Azure Government cloud. Other Azure environments (see below) may not be supported.</span>

<span style="color: #000000">A vDiscovery job retrieves information about virtual entities in cloud environments that are managed through a cloud management platform (CMP) such as Azure. The current vDiscovery feature supports tenants, networks, and compute VMs only. It does not support data that is retrieved from load balancer networks, load balancer VMs, Kubernetes platform VMs, application gateways, service VMs, SQL VMs, or any other VMs that are created by cloud services such as Kubernetes service or analytics service, where the IPAM is handled by the respective orchestration engines of the cloud provider.</span>  
<span style="color: #000000">Note that if the vDiscovery job retrieves unsupported data from Azure, then it impacts the performance of the vDiscovery process.</span>

<span style="color: #000000">Infoblox vDiscovery supports the resource manager model in the Azure Portal. However, you must first register the new vDiscovery application with Microsoft Entra ID (formerly, Azure Active Directory) through the Azure classic portal.</span>

> ⚠️ **Note**
> ⚠️ 
> ⚠️ - <span style="color: #000000">Discovered virtual networks in Microsoft Cloud are mapped to network containers in NIOS.</span>
> ⚠️ - Updates done by Microsoft to the root CAs of Azure services can cause vDiscovery to fail. If vDiscovery fails with ERROR: PycURL error: (60, 'SSL certificate problem: unable to get local issuer certificate'):
> ⚠️   - Download the **DigiCert Global Root G2 **Certificate from *[DigiCert Root Certificates](https://www.digicert.com/kb/digicert-root-certificates.htm)*.
> ⚠️   - Upload the certificate to NIOS as described in the *Uploading CA Certificates* section in the *[Infoblox NIOS Documentation](https://docs.infoblox.com/)*.

<span style="color: #000000">To perform a vDiscovery job on a Azure virtual network, complete the following tasks:</span>

1. <span style="color: #000000">Configure DNS resolver in NIOS, as described in the </span><span style="color: #000000">*Configuring DNS Resolver*</span><span style="color: #000000"> section.</span>
2. <span style="color: #000000">Register an application with the Microsoft Entra ID through the Azure classic portal, as described in </span><span style="color: #000000">*[Integrating vDiscovery with Microsoft Entra ID](https://infoblox-docs.atlassian.net/wiki/spaces/vniosazure/pages/37814282)*</span><span style="color: #000000">.</span>
3. <span style="color: #000000">Perform vDiscovery for service instances and subnets in selected virtual networks. For detailed information, refer to </span><span style="color: #000000">*Configuring vDiscovery Jobs*</span><span style="color: #000000"> in the </span><span style="color: #000000">*[Infoblox NIOS Documentation](https://docs.infoblox.com/)*</span><span style="color: #000000">*.*</span>
  <span style="color: #000000">When configuring the endpoint for the vDiscovery job, ensure that you perform the following:</span>
  - <span style="color: #000000">**Server Type**</span><span style="color: #000000">: Select </span><span style="color: #000000">**Azure**</span><span style="color: #000000">.</span>
  - <span style="color: #000000">**Client ID**</span><span style="color: #000000">: Use the </span><span style="color: #000000">**CLIENT ID**</span><span style="color: #000000"> you obtained for the application you created in Azure.</span>
  - <span style="color: #000000">**Client Secret**</span><span style="color: #000000">: Enter the key value of the application to authenticate the user account.</span>
  - <span style="color: #000000">**Service Endpoint**</span><span style="color: #000000">: Use the token endpoint URL you selected for the new application.</span>
4. <span style="color: #000000">After performing a vDiscovery job on your virtual networks, you can view and manage discovered data in NIOS. For detailed information, refer to the </span><span style="color: #000000">*[Infoblox NIOS Documentation](https://docs.infoblox.com/)*</span><span style="color: #000000">. You can also create DNS records for discovered IP addresses. For information, see </span><span style="color: #000000">*[Creating DNS Records for Discovered IP Addresses](https://infoblox-docs.atlassian.net/wiki/spaces/vniosazure/pages/37486803)*</span><span style="color: #000000">[.](/wiki/pages/resumedraft.action?draftId=22806684#PerformingvDiscoveryonVirtualNetworks-bookmark32)</span>

<span style="color: #000000">The vDiscovery job of Azure Government cloud uses different service endpoints than that of Azure public cloud. The following table illustrates the use case of different endpoints that Infoblox supports. </span>Allow network traffic to these endpoints and access to the download page [https://www.microsoft.com/en-us/download/details.aspx?id=56519](https://www.microsoft.com/en-us/download/details.aspx?id=56519).

| **Cloud** | **Service Endpoint Pattern** | **API Endpoint** | **Service Management Endpoint** |
| --- | --- | --- | --- |
| **Azure public cloud** | *https://login.microsoftonline.com/** | *https://management.azure.com/* | *https://management.core.windows.net/* |
| **Azure Government** | *https://login.microsoftonline.us/** | *https://management.usgovcloudapi.net/* | *https://management.core.usgovcloudapi.net/* |

<span style="color: #000000">The following service endpoints are currently not supported by Infoblox:</span>

| **Cloud** | **Service Endpoint Pattern** |
| --- | --- |
| **Azure AD Germany** | *https://login.microsoftonline.de* |
| **Azure AD China operated by 21Vianet** | *https://login.chinacloudapi.cn* |

## <span style="color: #555555">Configuring DNS Resolver</span>

<span style="color: #000000">To perform vDiscovery for all resources in your Microsoft virtual networks, you must enable DNS resolvers in NIOS. To configure DNS resolver for the Grid, complete the following steps in the NIOS GUI, Grid Manager:</span>

1. <span style="color: #000000">On the </span><span style="color: #000000">**Grid**</span><span style="color: #000000"> tab -> </span><span style="color: #000000">**Grid**</span><span style="color: #000000"> </span><span style="color: #000000">**Manager**</span><span style="color: #000000"> tab -> </span><span style="color: #000000">**Members**</span><span style="color: #000000"> tab, expand the Toolbar, and then click </span><span style="color: #000000">**Grid**</span><span style="color: #000000"> </span><span style="color: #000000">**Properties**</span><span style="color: #000000">.</span>
2. <span style="color: #000000">In the </span><span style="color: #000000">*Grid*</span><span style="color: #000000"> </span><span style="color: #000000">*Properties*</span><span style="color: #000000"> editor, complete the following:</span>
  - <span style="color: #000000">On the </span><span style="color: #000000">**DNS**</span><span style="color: #000000"> </span><span style="color: #000000">**Resolver**</span><span style="color: #000000"> tab, select the </span><span style="color: #000000">**Enable**</span><span style="color: #000000"> </span><span style="color: #000000">**DNS**</span><span style="color: #000000"> </span><span style="color: #000000">**Resolver**</span><span style="color: #000000"> checkbox if it is not already selected.</span>
  - <span style="color: #000000">In the </span><span style="color: #000000">**Name**</span><span style="color: #000000"> </span><span style="color: #000000">**Servers**</span><span style="color: #000000"> list, click </span><span style="color: #000000">**Add**</span><span style="color: #000000"> to add the IP address of the upstream DNS server to the list.</span>
  - <span style="color: #000000">Enter the IP address and press </span><span style="color: #000000">**Enter**</span><span style="color: #000000">.</span>
3. <span style="color: #000000">Save the configuration. The changes may take a brief period of time to become active.</span>