Data Hub Service Network Resources - Azure
The following table provides a list of resources required for Data Hub Service (DHS) network configuration.
Field | Description |
---|---|
Name | Name for the network. |
Region | The region where your preconfigured network is located. Default: Central US . See Supported Regions - Azure
Important: Your client-side VNet and peered DHS network must be configured in the same region.
|
Select if you want to set up VNet peering | Select to set up VNet peering and create peered endpoints. |
Tenant ID | Your Active Directory's Tenant ID.
To find your Tenant ID in Azure, navigate to Microsoft Azure.
To add your Tenant ID to your Data Hub Service, return to the DHS Configure Network page. Important: You can add your MarkLogic Data Hub Service account to only one Azure Active Directory, meaning you cannot change the Tenant ID once verified.
Important: You cannot assign the Network Contributor role to MarkLogic without adding your Tenant ID to your DHS.
Example: |
Assign the Network Contributor Role | Assign the Network Contributor role to the mlDataHubService application, enabling MarkLogic to manage networks but not access them. To learn how to assign the Network Contributor role to the mlDataHubService application, see Assign the Network Contributor Role. For details about the role, see Network Contributor. |
VNet ID | Your client-side VNet's identifier.
To find your VNet ID in Microsoft Azure, navigate to Azure Virtual networks.
Example: |
VNet CIDR | The IPv4 Address Space used to set up your client-side VNet. Primary CIDR (Classless Inter-Domain Routing) block for your VNet. Example: 10.0.0.0/23
Important: The CIDR block
10.100.0.0/10 is used internally. If your VNet CIDR is within the 10.100.0.0/10 range of IP addresses, your CIDR block size must be between /20 and /28 subnet masks. The maximum amount of IP addresses in a CIDR block is 4,096, including all subnets. |