Description
The Infoblox Data Connector allows you to easily connect your Infoblox TIDE data and Dossier data with Microsoft Sentinel. By connecting your data to Microsoft Sentinel, you can take advantage of search & correlation, alerting, and threat intelligence enrichment for each log.
- Declared status
- 1
- Declared author / publisher
- Infoblox
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
read and write permissions on the workspace are required.
Workspace
Workspace
read permissions to shared keys for the workspace are required. [See the documentation to learn more about workspace keys](https://docs.microsoft.com/azure/azure-monitor/platform/agent-windows#obtain-workspace-id-and-key).
Keys
Workspace
Azure Subscription
Azure Subscription with owner role is required to register an application in Microsoft Entra ID and assign role of contributor to app in resource group.
Microsoft.Web/sites permissions
Read and write permissions to Azure Functions to create a Function App is required. [See the documentation to learn more about Azure Functions](https://docs.microsoft.com/azure/azure-functions/).
REST API Credentials/permissions
**Infoblox API Key** is required. See the documentation to learn more about API on the [Rest API reference](https://csp.infoblox.com/apidoc?url=https://csp.infoblox.com/apidoc/docs/Infrastructure#/Services/ServicesRead)
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
>**NOTE:** This connector uses Azure Functions to connect to the Infoblox API to create Threat Indicators for TIDE and pull Dossier data into Microsoft Sentinel. This might result in additional data ingestion costs. Check the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/) for details.
>**(Optional Step)** Securely store workspace and API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. [Follow these instructions](https://docs.microsoft.com/azure/app-service/app-service-key-vault-references) to use Azure Key Vault with an Azure Function App.
**STEP 1 - App Registration steps for the Application in Microsoft Entra ID**
This integration requires an App registration in the Azure portal. Follow the steps in this section to create a new application in Microsoft Entra ID:
1. Sign in to the [Azure portal](https://portal.azure.com/).
2. Search for and select **Microsoft Entra ID**.
3. Under **Manage**, select **App registrations > New registration**.
4. Enter a display **Name** for your application.
5. Select **Register** to complete the initial app registration.
6. When registration finishes, the Azure portal displays the app registration's Overview pane. You see the **Application (client) ID** and **Tenant ID**. The client ID and Tenant ID are required as the **AzureClientId** and **AzureTenantId** configuration parameters, used by the connector's Function Apps to authenticate to the Log Ingestion API (for Dossier data) and to the Microsoft Sentinel Threat Intelligence Indicators API (for TIDE data).
> **Reference link:** [https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app](https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app)
**STEP 2 - Add a client secret for application in Microsoft Entra ID**
Sometimes called an application password, a client secret is a string value required by the connector to authenticate to the Log Ingestion API and the Microsoft Sentinel Threat Intelligence Indicators API. Follow the steps in this section to create a new Client Secret:
1. In the Azure portal, in **App registrations**, select your application.
2. Select **Certificates & secrets > Client secrets > New client secret**.
3. Add a description for your client secret.
4. Select an expiration for the secret or specify a custom lifetime. Limit is 24 months.
5. Select **Add**.
6. *Record the secret's value for use in your client application code. This secret value is never displayed again after you leave this page.* The secret value is required as the **AzureClientSecret** configuration parameter.
> **Reference link:** [https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app#add-a-client-secret](https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app#add-a-client-secret)
**STEP 3 - Assign role of Contributor to application in Microsoft Entra ID**
This role is required so the connector's Function Apps can create Threat Intelligence Indicators from TIDE data via the Microsoft Sentinel Threat Intelligence Indicators API. Follow the steps in this section to assign the role:
1. In the Azure portal, Go to **Resource Group** and select your resource group.
2. Go to **Access control (IAM)** from left panel.
3. Click on **Add**, and then select **Add role assignment**.
4. Select **Contributor** as role and click on next.
5. In **Assign access to**, select `User, group, or service principal`.
6. Click on **add members** and type **your app name** that you have created and select it.
7. Now click on **Review + assign** and then again click on **Review + assign**.
> **Reference link:** [https://learn.microsoft.com/azure/role-based-access-control/role-assignments-portal](https://learn.microsoft.com/azure/role-based-access-control/role-assignments-portal)
**STEP 4 - Find the Object ID of the app registration**
This connector ingests Dossier and TIDE data into Sentinel via the Log Ingestion API, which requires the app registration (the same one created in Step 1) to have the **Monitoring Metrics Publisher** role on every Data Collection Rule the connector creates. This role assignment is granted **automatically** by the ARM template at deployment time - you do not need to assign it by hand - but the template needs the app's **Object ID** (the Enterprise Application / Service Principal object ID, not the Application/Client ID) as a deployment parameter to do so.
1. In the Azure portal, search for and select **Microsoft Entra ID**.
2. Under **Manage**, select **Enterprise applications**.
3. Search for the app registration you created in Step 1 and select it.
4. Copy the **Object ID** shown on the Overview pane - this is the value to enter as **AzureEntraObjectID** during deployment.
> **Note:** If this value is missing or incorrect at deployment time, the role assignment silently fails to grant access and Dossier/TIDE data will not appear in the workspace, even though the Function Apps run without error.
**STEP 5 - Steps to generate the Infoblox API Credentials**
Follow these instructions to generate Infoblox API Key.
In the [Infoblox Cloud Services Portal](https://csp.infoblox.com/atlas/app/welcome), generate an API Key and copy it somewhere safe to use in the next step. You can find instructions on how to create API keys [**here**](https://docs.infoblox.com/space/BloxOneThreatDefense/230394187/How+Do+I+Create+an+API+Key%3F).
Azure Resource Manager (ARM) Template
Use this method for automated deployment of the Infoblox Data connector.
1. Click the **Deploy to Azure** button below.
[](https://aka.ms/sentinel-infoblox-azuredeploy)
2. Select the preferred **Subscription**, **Resource Group** and **Location**.
3. Enter the below information :
Workspace ID
Workspace (Log Analytics workspace resource name)
Data Collection Endpoint/Rule Location (Default: Resource Group location, must match the workspace region)
Azure Tenant Id
Azure Client Id
Azure Client Secret
Azure Entra Object ID (from Step 4)
Infoblox API Token
Infoblox Base URL
Historical Data Cutoff Date
Log Level (Default: Info)
Confidence (Default: 80)
Threat Level (Default: 80)
App Insights Workspace Resource ID
4. Mark the checkbox labeled **I agree to the terms and conditions stated above**.
5. Click **Purchase** to deploy.
> **Note:** The Data Collection Endpoint/Data Collection Rules and the Monitoring Metrics Publisher role assignment on them are created and wired up automatically by this template - no manual DCR or role-assignment steps are required after deployment.
Related content
Links established from declared identifiers and solution manifests.
Source provenance
GitHubDisplayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.
- Commit
9800e51↗- Source identifier
InfobloxDataConnector
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC