↳ GitHub sourceConnector

CommvaultSecurityIQ

Description

This Azure Function enables Commvault users to ingest alerts/events into their Microsoft Sentinel instance. With Analytic Rules,Microsoft Sentinel can automatically create Microsoft Sentinel incidents from incoming events and logs.

Declared status: 1
Declared author / publisher: Commvault

Declared sources

Metadata from the source file. No dependencies inferred from KQL.

Data types

CommvaultAlerts_CL

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

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/).

Commvault Environment Endpoint URL

Make sure to follow the documentation and set the secret value in KeyVault

Commvault QSDK Token

Make sure to follow the documentation and set the secret value in KeyVault

Connector instructions

Content published in the repository. Refer to the original file for all parameters.

>**NOTE:** This connector uses Azure Functions to connect to a Commvault Instance to pull its logs 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.

>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 - Configuration steps for the Commvalut QSDK Token** [Follow these instructions](https://documentation.commvault.com/2024e/essential/creating_access_token.html) to create an API Token.

**STEP 2 - Deploy the connector and the associated Azure Function** >**IMPORTANT:** Before deploying the CommvaultSecurityIQ data connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the Commvault Endpoint URL and QSDK Token, readily available.

Workspace ID

Primary Key

**Azure Resource Manager (ARM) Template** Use this method for automated deployment of the Commvault Security IQ data connector. 1. Click the **Deploy to Azure** button below. [![Deploy To Azure](https://aka.ms/deploytoazurebutton)](https://aka.ms/sentinel-CommvaultSecurityIQ-azuredeploy) 2. Select the preferred **Subscription**, **Resource Group** and **Region**. 3. Enter the **Workspace ID**, **Workspace Key** 'and/or Other required fields' and click Next. 4. Click **Create** to deploy.

Source provenance

GitHub

Displayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.

File: Solutions/Commvault Security IQ/Data Connectors/CommvaultSecurityIQ_API_AzureFunctionApp.json ↗
Commit: 9800e51 ↗
Source identifier: CommvaultSecurityIQ_CL

Additional source files 2

Solutions/Commvault Security IQ/Data Connectors/CommvaultSecurityIQ_API_AzureFunctionApp.jsonsource ↗Solutions/Commvault Security IQ/Data/Solution_Commvault Security IQ.jsonsolution-membership ↗

GSTEP / CATALOG TRACKING

Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC

GSTEP sync dates, separate from the source content’s publication dates.