Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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:


Service Endpoint PatternAPI EndpointService Management Endpoint
Azurehttps://login.microsoftonline.com/*https://management.azure.com/https://management.core.windows.net/
Azure Govcloudhttps://login-us.microsoftonline.com/*https://management.usgovcloudapi.net/https://management.core.usgovcloudapi.net/

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

Configuring DNS Resolver

To perform vDiscovery for all resources in your Microsoft VNets, you must enable DNS resolvers in NIOS. To configure DNS resolver for the Grid, complete the following in the NIOS GUI, Grid Manager:

  1. From the Grid tab -> Grid Manager tab -> Members tab, expand the Toolbar, and then click Grid Properties.
  2. In the Grid Properties editor, do the following:
    • Click the DNS Resolver tab and select the Enable DNS Resolver check box if it is not already selected.
    • In the Name Servers list, click Add to add the IP address of the upstream DNS server to the list.
    • Enter the IP address and press Enter.
  3. Save the configuration. The changes may take a brief period of time to become active.
  • No labels