Page Comparison

Infoblox provides vDiscovery for detecting and obtaining information about virtual entities and interfaces in the Microsoft Cloud. Infoblox vDiscovery supports the resource manager model in the Azure Portal. However, you must first register the new vDiscovery application with Azure Active Directory through the Azure classic portal.

...

Note: Discovered virtual networks in Microsoft Cloud is mapped to Network Containers in NIOS.

...

To perform a vDiscovery job for a VNet, complete the following tasks:

1. Configure DNS resolver in NIOS, as described in Configuring DNS Resolver.
2. Register an application with the Azure Active Directory through the Azure classic portal, as described in Integrating vDiscovery with Azure Active Directory.
3. Add the new application as a user through the Azure resource manager portal, as described in Adding vDiscovery Application as New User.
4. Perform vDiscovery for service instances and subnets in selected VNets. For detailed information, refer to ConfiguringvDiscoveryJobs in the InfobloxNIOSAdministratorGuide. When configuring the endpoint for the vDiscovery job, ensure that you select the following:
   • Server Type: Select Azure.
   • Client ID: Use the CLIENTID you obtained for the application you created in Azure.
   • Client Secret: Enter the key value of the application to authenticate the user account.
   • Service Endpoint: Use the token endpoint URL you selected for the new application.
5. After performing a vDiscovery job on your VNets, you can view and manage discovered data in NIOS. For detailed information, refer to the InfobloxNIOSAdministratorGuide. You can also create DNS records for discovered IP addresses. For information, see Creating DNS Records for Discovered IP Addresses.

Azure Government Cloud vDiscovery job uses different service endpoints than that of Azure. The following table illustrates the use case of different endpoints:

...

Note: Infoblox vNIOS configured in Azure does not currently support DHCP.

...