Microsoft Sentinel
Cloud and workloads

Data Connectors Reference

In brief

The documentation marks the on-premises and online Exchange Security Insights collectors for migration to Azure Monitor and requires updating from the Azure Log Analytics HTTP Data Collector API to the Log Monitor API.

What Defender admins need to know

Administrators using these collectors must switch APIs and are advised to update the collector to version 8.0.0.0 or later.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

For a list of tables ingested into Microsoft Sentinel and the connectors that ingest them, see Microsoft Sentinel tables and associated connectors.

1Password

Supported by:1Password

  • Workspace ID: <variable value provided at install time>
  • Primary Key: <variable value provided at install time>

Armis Alerts Activities (using Azure Functions)

Supported by:Armis Corporation

The Armis Alerts Activities connector gives the capability to ingest Armis Alerts and Activities into Microsoft Sentinel through the Armis REST API. Refer to the API documentation: https://<YourArmisInstance>.armis.com/api/v1/docs for more information. The connector provides the ability to get alert and activity information from the Armis platform and to identify and prioritize threats in your environment. Armis uses your existing infrastructure to discover and identify devices without having to deploy any agents.

Log Analytics table(s):

TableDCR supportLake-only ingestion
Armis_Alerts_CLYesYes
Armis_Activities_CLYesYes

Data collection rule support:Workspace transform DCR

Prerequisites:

  • Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. For more information, see Azure Functions.
  • REST API Credentials/permissions: Armis Secret Key is required. See the documentation to learn more about API on the https://<YourArmisInstance>.armis.com/api/v1/doc

Setup Instructions:

NOTE: This connector uses Azure Functions to connect to the Armis API to pull its logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the Azure Functions pricing page 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 to use Azure Key Vault with an Azure Function App.

NOTE: This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias ArmisActivities/ArmisAlerts and load the function code. The function usually takes 10-15 minutes to activate after solution installation/update.

STEP 1 - Configuration steps for the Armis API

Follow these instructions to create an Armis API secret key.

  1. Log into your Armis instance
  2. Navigate to Settings -> API Management
  3. If the secret key has not already been created, press the Create button to create the secret key
  4. To access the secret key, press the Show button
  5. The secret key can now be copied and used during the Armis Alerts Activities connector configuration

STEP 2 - 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.
  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 is required as configuration parameters for the execution of Armis Alerts Activities Data Connector.

Reference link:/azure/active-directory/develop/quickstart-register-app

STEP 3 - Add a client secret for application in Microsoft Entra ID

Sometimes called an application password, a client secret is a string value required for the execution of Armis Alerts Activities Data Connector. 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 configuration parameter for the execution of Armis Alerts Activities Data Connector.

Reference link:/azure/active-directory/develop/quickstart-register-app#add-a-client-secret

STEP 4 - Get Object ID of your application in Microsoft Entra ID

After creating your app registration, follow the steps in this section to get Object ID:

  1. Go to Microsoft Entra ID.
  2. Select Enterprise applications from the left menu.
  3. Find your newly created application in the list (you can search by the name you provided).
  4. Click on the application.
  5. On the overview page, copy the Object ID. This is the AzureEntraObjectId needed for your ARM template role assignment.

STEP 5 - Assign role of Contributor to application in Microsoft Entra ID

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:/azure/role-based-access-control/role-assignments-portal

STEP 6 - Create a Keyvault

Follow these instructions to create a new Keyvault.

  1. In the Azure portal, Go to Key vaults. Click create.
  2. Select Subsciption, Resource Group and provide unique name of keyvault.

NOTE: Create a separate key vault for each API key within one workspace.

STEP 7 - Create Access Policy in Keyvault

Follow these instructions to create access policy in Keyvault.

  1. Go to keyvaults, select your keyvault, go to Access policies on left side panel. Click create.
  2. Select all keys & secrets permissions. Click next.
  3. In the principal section, search by application name which was generated in STEP - 2. Click next.

NOTE: Ensure the Permission model in the Access Configuration of Key Vault is set to 'Vault access policy'

STEP 8 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function

IMPORTANT: Before deploying the Armis Device data connector, have the Armis API Authorization Key(s) readily available..

Option 1 - Azure Resource Manager (ARM) Template

Use this method for automated deployment of the Armis connector.

  1. Click the Deploy to Azure button below.

    aka.msaka.ms

  2. Select the preferred Subscription, Resource Group and Location.

  3. Enter the below information : Function Name Workspace Name Armis Secret Key Armis URL (https://<armis-instance>.armis.com/api/v1/) Armis Alert Table Name Armis Activity Table Name Severity (Default: Low) Armis Schedule KeyVault Name Azure Client Id Azure Client Secret Azure Entra ObjectID Tenant Id

  4. Mark the checkbox labeled I agree to the terms and conditions stated above.

  5. Click Purchase to deploy.

Option 2 - Manual Deployment of Azure Functions

Use the following step-by-step instructions to deploy the Armis Alerts Activities data connector manually with Azure Functions (Deployment via Visual Studio Code).

  1. Deploy a Function App

NOTE: You will need to prepare VS code for Azure function development.

  1. Download the Azure Function App file. Extract archive to your local development computer.

  2. Start VS Code. Choose File in the main menu and select Open Folder.

  3. Select the top level folder from extracted files.

  4. Choose the Azure icon in the Activity bar, then in the Azure: Functions area, choose the Deploy to function app button. If you aren't already signed in, choose the Azure icon in the Activity bar, then in the Azure: Functions area, choose Sign in to Azure If you're already signed in, go to the next step.

  5. Provide the following information at the prompts:

    a. Select folder: Choose a folder from your workspace or browse to one that contains your function app.

    b. Select Subscription: Choose the subscription to use.

    c. Select Create new Function App in Azure (Don't choose the Advanced option)

    d. Enter a globally unique name for the function app: Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. (e.g. ARMISXXXXX).

    e. Select a runtime: Choose Python 3.12

    f. Select a location for new resources. For better performance and lower costs choose the same region where Microsoft Sentinel is located.

  6. Deployment will begin. A notification is displayed after your function app is created and the deployment package is applied.

  7. Go to Azure Portal for the Function App configuration.

  8. Configure the Function App

  9. In the Function App, select the Function App Name and select Configuration.

  10. In the Application settings tab, select + New application setting.

  11. Add each of the following application settings individually, with their respective values (case-sensitive): Workspace Name Armis Secret Key Armis URL (https://<armis-instance>.armis.com/api/v1/) Armis Alert Table Name Armis Activity Table Name Severity (Default: Low) Armis Schedule KeyVault Name Azure Client Id Azure Client Secret Azure Entra ObjectID Tenant Id logAnalyticsUri (optional)

  • Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: https://<CustomerId>.ods.opinsights.azure.us.
  1. Once all application settings have been entered, click Save.

Armis Devices (using Azure Functions)

Supported by:Armis Corporation

The Armis Device connector gives the capability to ingest Armis Devices into Microsoft Sentinel through the Armis REST API. Refer to the API documentation: https://<YourArmisInstance>.armis.com/api/v1/docs for more information. The connector provides the ability to get device information from the Armis platform. Armis uses your existing infrastructure to discover and identify devices without having to deploy any agents. Armis can also integrate with your existing IT & security management tools to identify and classify each and every device, managed or unmanaged in your environment.

Log Analytics table(s):

TableDCR supportLake-only ingestion
Armis_Devices_CLYesYes

Data collection rule support:Workspace transform DCR

Prerequisites:

  • Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. For more information, see Azure Functions.
  • REST API Credentials/permissions: Armis Secret Key is required. See the documentation to learn more about API on the https://<YourArmisInstance>.armis.com/api/v1/doc

Setup Instructions:

NOTE: This connector uses Azure Functions to connect to the Armis API to pull its logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the Azure Functions pricing page 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 to use Azure Key Vault with an Azure Function App.

NOTE: This data connector depends on a parser based on a Kusto Function to work as expected. Follow these steps to create the Kusto functions alias, ArmisDevice

STEP 1 - Configuration steps for the Armis API

Follow these instructions to create an Armis API secret key.

  1. Log into your Armis instance
  2. Navigate to Settings -> API Management
  3. If the secret key has not already been created, press the Create button to create the secret key
  4. To access the secret key, press the Show button
  5. The secret key can now be copied and used during the Armis Device connector configuration

STEP 2 - 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.
  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 is required as configuration parameters for the execution of Armis Device Data Connector.

Reference link:/azure/active-directory/develop/quickstart-register-app

STEP 3 - Add a client secret for application in Microsoft Entra ID

Sometimes called an application password, a client secret is a string value required for the execution of Armis Device Data Connector. 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 configuration parameter for the execution of Armis Device Data Connector.

Reference link:/azure/active-directory/develop/quickstart-register-app#add-a-client-secret

STEP 4 - Get Object ID of your application in Microsoft Entra ID

After creating your app registration, follow the steps in this section to get Object ID:

  1. Go to Microsoft Entra ID.
  2. Select Enterprise applications from the left menu.
  3. Find your newly created application in the list (you can search by the name you provided).
  4. Click on the application.
  5. On the overview page, copy the Object ID. This is the AzureEntraObjectId needed for your ARM template role assignment.

STEP 5 - Assign role of Contributor to application in Microsoft Entra ID

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:/azure/role-based-access-control/role-assignments-portal

STEP 6 - Create a Keyvault

Follow these instructions to create a new Keyvault.

  1. In the Azure portal, Go to Key vaults. Click create.
  2. Select Subsciption, Resource Group and provide unique name of keyvault.

NOTE: Create a separate key vault for each API key within one workspace.

STEP 7 - Create Access Policy in Keyvault

Follow these instructions to create access policy in Keyvault.

  1. Go to keyvaults, select your keyvault, go to Access policies on left side panel. Click create.
  2. Select all keys & secrets permissions. Click next.
  3. In the principal section, search by application name which was generated in STEP - 2. Click next.

NOTE: Ensure the Permission model in the Access Configuration of Key Vault is set to 'Vault access policy'

STEP 8 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function

IMPORTANT: Before deploying the Armis Device data connector, have the Armis API Authorization Key(s) readily available..

Option 1 - Azure Resource Manager (ARM) Template

Use this method for automated deployment of the Armis connector.

  1. Click the Deploy to Azure button below.

    aka.msaka.ms

  2. Select the preferred Subscription, Resource Group and Location.

  3. Enter the below information : Function Name Location Workspace Name Armis Secret Key Armis URL (https://<armis-instance>.armis.com/api/v1/) Armis Device Table Name Armis Schedule KeyVault Name Azure Client Id Azure Client Secret Azure Entra ObjectID Tenant Id

  4. Mark the checkbox labeled I agree to the terms and conditions stated above.

  5. Click Purchase to deploy.

Option 2 - Manual Deployment of Azure Functions

Use the following step-by-step instructions to deploy the Armis Device data connector manually with Azure Functions (Deployment via Visual Studio Code).

  1. Deploy a Function App

NOTE: You will need to prepare VS code for Azure function development.

  1. Download the Azure Function App file. Extract archive to your local development computer.

  2. Start VS Code. Choose File in the main menu and select Open Folder.

  3. Select the top level folder from extracted files.

  4. Choose the Azure icon in the Activity bar, then in the Azure: Functions area, choose the Deploy to function app button. If you aren't already signed in, choose the Azure icon in the Activity bar, then in the Azure: Functions area, choose Sign in to Azure If you're already signed in, go to the next step.

  5. Provide the following information at the prompts:

    a. Select folder: Choose a folder from your workspace or browse to one that contains your function app.

    b. Select Subscription: Choose the subscription to use.

    c. Select Create new Function App in Azure (Don't choose the Advanced option)

    d. Enter a globally unique name for the function app: Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. (e.g. ARMISXXXXX).

    e. Select a runtime: Choose Python 3.12

    f. Select a location for new resources. For better performance and lower costs choose the same region where Microsoft Sentinel is located.

  6. Deployment will begin. A notification is displayed after your function app is created and the deployment package is applied.

  7. Go to Azure Portal for the Function App configuration.

  8. Configure the Function App

  9. In the Function App, select the Function App Name and select Configuration.

  10. In the Application settings tab, select + New application setting.

  11. Add each of the following application settings individually, with their respective values (case-sensitive): Location Workspace Name Armis Secret Key Armis URL (https://<armis-instance>.armis.com/api/v1/) Armis Device Table Name Armis Schedule KeyVault Name Azure Client Id Azure Client Secret Azure Entra ObjectID Tenant Id logAnalyticsUri (optional)

  • Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: https://<CustomerId>.ods.opinsights.azure.us.
  1. Once all application settings have been entered, click Save.

Atlassian Confluence Audit (via Codeless Connector Framework)

Supported by:Microsoft Corporation

The Atlassian Confluence Audit data connector provides the capability to ingest Confluence Audit Records events into Microsoft Sentinel through the REST API. Refer to API documentation for more information. The connector enables event retrieval to assess potential security risks, monitor collaboration, and diagnose and troubleshoot configuration issues.

Log Analytics table(s):

TableDCR supportLake-only ingestion
ConfluenceAuditLogsNoNo

Data collection rule support: Not currently supported

Prerequisites:

Setup Instructions:

Connect Atlassian Confluence to Microsoft Sentinel

Add one connection per Atlassian Confluence site. Follow the Atlassian API token instructions to create an API token.

  • Data Connectors Grid (configure in portal)

Atlassian Jira Audit (via Codeless Connector Framework)

Supported by:Microsoft Corporation

The Atlassian Jira Audit data connector provides the capability to ingest Jira Audit Records events into Microsoft Sentinel through the REST API. Refer to API documentation for more information. The connector enables event retrieval to assess potential security risks, monitor collaboration, and diagnose and troubleshoot configuration issues.

Log Analytics table(s):

TableDCR supportLake-only ingestion

Supported by:Microsoft Corporation

The Bitglass data connector provides the capability to retrieve security event logs of the Bitglass services and more events into Microsoft Sentinel through the REST API. The connector enables event retrieval to assess potential security risks, monitor collaboration, and diagnose and troubleshoot configuration issues.

Log Analytics table(s):

Follow the instructions to obtain the credentials.

  1. Please contact Bitglass support and obtain the BitglassToken and BitglassServiceURL ntation].
  2. Save credentials for using in the data connector.

STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function

TableDCR supportLake-only ingestion
SyslogYesYes
CiscoSDWANNetflow_CLNoNo

Data collection rule support:Workspace transform DCR

Supported by:Commvault

The Commvault Security IQ data connector ingests anomaly detection events from Commvault environments into Microsoft Sentinel, enabling detection and response for threats targeting backup infrastructure such as ransomware and suspicious file operations. Events are stored in the CommvaultAlertsCCF_CL table.

Log Analytics table(s):

Commvault Security IQ Connector Instances

This connector polls Commvault every 30 minutes and ingests threat anomaly events into the CommvaultAlertsCCF_CL table.

  • Data Connectors Grid (configure in portal)

NOTE: The newest version of the ESET PROTECT Platform and Microsoft Sentinel integration pulls not only detections logs but also newly created incidents. If your integration was set up before 20.06.2025, please follow these steps to update it.

Step 1 - Create an API user

Use this instruction to create an ESET Connect API User account with Login and Password.

Step 2 - Create a registered application

Create a Microsoft Entra ID registered application by following the steps in the Register a new application instruction.

Step 3 - Deploy the ESET Protect Platform data connector using the Azure Resource Manager (ARM) template

  1. Click the Deploy to Azure button below.

    aka.ms

  2. Select the name of the Log Analytics workspace associated with your Microsoft Sentinel. Select the same Resource Group as the Resource Group of the Log Analytics workspace.

  3. Type the parameters of the registered application in Microsoft Entra ID: Azure Client ID, Azure Client Secret, Azure Tenant ID, Object ID. You can find the Object ID on Azure Portal by following this path Microsoft Entra ID -> Manage (on the left-side menu) -> Enterprise applications -> Object ID column (the value next to your registered application name).

  4. Provide the ESET Connect API user account Login and Password obtained in Step 1.

  5. Select one or more ESET products (ESET PROTECT, ESET Inspect, ESET Cloud Office Security) from which detections are retrieved.

Deprecated) Exchange Security Insights On-Premises Collector

Supported by:Community

Connector used to push Exchange On-Premises Security configuration for Microsoft Sentinel Analysis - Deprecated, use Azure Monitor Version

Log Analytics table(s):

Table DCR support Lake-only ingestion
ESIExchangeConfig_CL No No

Data collection rule support: Not currently supported

Prerequisites:

  • Azure Log Analytics HTTP Data Collector API will be deprecated: Azure Log Analytics HTTP Data Collector API will be deprecated, Update to Log Monitor API is REQUIRED. Learn more
  • Service Account with Organization Management role: The service Account that launch the script as scheduled task needs to be Organization Management to be able to retrieve all the needed security Information.
  • Detailed documentation: >NOTE: Detailed documentation on Installation procedure and usage can be found here

Setup Instructions:

NOTE - UPDATE

Note:

NOTE - UPDATE:

We recommend to Update the Collector to Version 8.0.0.0 or higher AND switching to new Log Monitor API. The Collector Script Update procedure could be found here : ESI On-Premises Collector Update, Update to Log Monitor API procedure could be found here : Upgrade an existing deployment. The new version of the Collector is using DCR (Data Collection Rules) for data collection. You need to configure DCR before running the script.

1. Install the ESI Collector Script on a server with Exchange Admin PowerShell console

This is the script that will collect Exchange Information to push content in Microsoft Sentinel.

Script Deployment

Download the latest version of ESI Collector

The latest version can be found here : https://aka.ms/ESI-ExchangeCollector-Script. The file to download is CollectExchSecIns.zip

Copy the script folder

Unzip the content and copy the script folder on a server where Exchange PowerShell Cmdlets are present.

Unblock the PS1 Scripts

Click right on each PS1 Script and go to Properties tab. If the script is marked as blocked, unblock it. You can also use the Cmdlet 'Unblock-File . in the unzipped folder using PowerShell.

**Configure Network Access **

Ensure that the script can contact Azure Analytics (*.ods.opinsights.azure.com).

2. Configure the ESI Collector Script

Be sure to be local administrator of the server. In 'Run as Administrator' mode, launch the 'setup.ps1' script to configure the collector. Fill the Log Analytics (Microsoft Sentinel) Workspace information. Fill the Environment name or leave empty. By default, choose 'Def' as Default analysis. The other choices are for specific usage.

  • Workspace ID: <variable value provided at install time>
  • Primary Key: <variable value provided at install time>

3. Schedule the ESI Collector Script (If not done by the Install Script due to lack of permission or ignored during installation)

The script needs to be scheduled to send Exchange configuration to Microsoft Sentinel. We recommend to schedule the script once a day. The account used to launch the Script needs to be member of the group Organization Management

NOTE: This data connector depends on a parser based on a Kusto Function to work as expected. Parsers are automatically deployed with the solution. Follow the steps to create the Kusto Functions alias : ExchangeAdminAuditLogs

Parsers are automatically deployed during Solution deployment. If you want to deploy manually, follow the steps below

Manual Parser Deployment

1. Download the Parser file

The latest version of the file ExchangeAdminAuditLogs

2. Create Parser ExchangeAdminAuditLogs function

In 'Logs' explorer of your Microsoft Sentinel's log analytics, copy the content of the file to Log explorer

3. Save Parser ExchangeAdminAuditLogs function

Click on save button. No parameter is needed for this parser. Click save again.

(Deprecated) Exchange Security Insights Online Collector (using Azure Functions)

Supported by:Community

Connector used to push Exchange Online Security configuration for Microsoft Sentinel Analysis - Deprecated, use Azure Monitor Version

Log Analytics table(s):

Table DCR support Lake-only ingestion
ESIExchangeOnlineConfig_CL Yes Yes

Data collection rule support:Workspace transform DCR

Prerequisites:

  • Azure Log Analytics HTTP Data Collector API will be deprecated: Azure Log Analytics HTTP Data Collector API will be deprecated. Update to the Azure Monitor Log Ingestion API is required. Learn more
  • Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. For more information, see Azure Functions.
  • microsoft.automation/automationaccounts permissions: Read and write permissions to create an Azure Automation with a Runbook is required. For more information, see Automation Account.
  • Microsoft.Graph permissions: Groups.Read, Users.ReadGroup.Read.All, User.Read.All, and Auditing.ReadAuditLog.Read.All permissions are required to retrieve user/user and group information linked to Exchange Online assignments. See the documentation to learn more.
  • Exchange Online permissions: Exchange.ManageAsApp permission and Global Reader or Security Reader Role are needed to retrieve the Exchange Online Security Configuration.See the documentation to learn more.
  • (Optional) Log Storage permissions: Storage Blob Data Contributor to a storage account linked to the Automation Account Managed identity or an Application ID is mandatory to store logs.See the documentation to learn more.

Setup Instructions:

NOTE - UPDATE

Note:

NOTE - UPDATE:

We recommend to Update the Collectorcollector to Versionversion 7.6.8.0.0.0 or highier. The Collector Script Update procedure could be found here :later and switch to the Azure Monitor Log Ingestion API. See ESI Online Collector Update and Upgrade an existing deployment.

NOTE: This data connector depends on a parser based on a Kusto Function to work as expected. Follow the steps for each Parser to create the Kusto Functions alias : ExchangeConfiguration and **ExchangeEnvironmentList STEP 12 - Parsers deployment**

Parser deployment (When using Microsoft Exchange Security Solution, Parsers are automatically deployed)

1. Download the Parser files

The latest version of the 2 files ExchangeConfiguration.yaml and ExchangeEnvironmentList.yaml

2. Create Parser ExchangeConfiguration function

In 'Logs' explorer of your Microsoft Sentinel's log analytics, copy the content of the file to Log explorer

3. Save Parser ExchangeConfiguration function

Click on save button. Define the parameters as asked on the header of the parser file. Click save again.

4. Reproduce the same steps for Parser ExchangeEnvironmentList

Reproduce the step 2 and 3 with the content of 'ExchangeEnvironmentList.yaml' file

NOTE: This connector uses Azure Automation to connect to 'Exchange Online' to pull its Security analysis into Microsoft Sentinel. This might result in additional data ingestion costs. Check the Azure Automation pricing page for details.

STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Automation

IMPORTANT: Before deploying the 'ESI Exchange Online Security Configuration' connector, have the Workspace ID and Workspace Primary Key (can be copied fromavailable and choose a generic environment display name for the following), as well asworkbooks. The template adds the Exchange Online tenant name (contoso.onmicrosoft.com), readily available.-cloud suffix when needed.

  • Workspace ID: <variable value provided at install time>
  • Primary Key: <variable value provided at install time>

Option 1 - Azure Resource Manager (ARM) Template

Use this method for automated deployment of the 'ESI Exchange Online Security Configuration' connector.

  1. Click the Deploy to Azure button below.

    aka.ms

  2. Select the preferred Subscription, Resource Group and Location.

  3. Enter the Workspace ID, Workspace Key, Tenant Name, 'and/or Other required fields'.

  4. Mark the checkbox labeled I agree to the terms and conditions stated above.

  5. Click Purchase to deploy.

Option 2 - Manual Deployment of Azure Automation

Use the following step-by-step instructions to deploy the 'ESI Exchange Online Security Configuration' connector manually with Azure Automation.

A. Create the Azure Automation Account

  1. From the Azure Portal, navigate to Azure Automation Account.
  2. Click + Add at the top.
  3. In the Basics tab, fill the required fields and give a name to the Azure Automation.
  4. In the Advanced and Networking and Tags Tabs, leave fields as default if you don't need to customize them.
  5. 'Make other preferable configuration changes', if needed, then click Create.

B. Add Exchange Online Management Module, Microsoft Graph (Authentication, User and Group) Modules

  1. On the Automation Account page, select Modules.
  2. Click on Browse gallery and search the ExchangeOnlineManagement module.
  3. Select it and click on Select.
  4. Choose Version 5.1 on Runtime version field and click on Import button. Repeat the step for the following modules : 'Microsoft.Graph.Authentication', 'Microsoft.Graph.Users' and 'Microsoft.Graph.Groups. Attention, you need to wait for Microsoft.Graph.Authentication installation before processing next modules

C. Download the Runbook Content

  1. Download the latest version of ESI Collector. The latest version can be found here : https://aka.ms/ESI-ExchangeCollector-Script
  2. Unzip the file to find the JSON file and the PS1 file for next step.

D. Create Runbook

  1. On the Automation Account page, select the Runbooks button.
  2. Click on Create a runbook and name it like 'ESI-Collector' with a runbook type PowerShell, Runtime Version 5.1 and click 'Create'.
  3. Import the content of the previous step's PS1 file in the Runbook window.
  4. Click on Publish

E. Create GlobalConfiguration Variable

  1. On the Automation Account page, select the Variables button.
  2. Click on Add a Variable and name it exaclty 'GlobalConfiguration' with a type String.
  3. On 'Value' field, copy the content of the previous step's JSON file.
  4. Inside the content, replace the values of WorkspaceID and WorkspaceKey.
  5. Click on 'Create' button.

F. Create TenantName Variable

  1. On the Automation Account page, select the Variables button.
  2. Click on Add a Variable and name it exaclty 'TenantName' with a type String.
  3. On 'Value' field, write the tenant name of your Exchange Online.
  4. Click on 'Create' button.

G. Create LastDateTracking Variable

  1. On the Automation Account page, select the Variables button.
  2. Click on Add a Variable and name it exaclty 'LastDateTracking' with a type String.
  3. On 'Value' field, write 'Never'.
  4. Click on 'Create' button.

H. Create a Runbook Schedule

  1. On the Automation Account page, select the Runbook button and click on your created runbook.
  2. Click on Schedules and Add a schedule button.
  3. Click on Schedule, Add a Schedule and name it. Select Recurring value with a reccurence of every 1 day, click 'Create'.
  4. Click on 'Configure parameters and run settings'. Leave all empty and click on OK and OK again.

STEP 3 - Assign Microsoft Graph Permission and Exchange Online Permission to Managed Identity Account

To be able to collect Exchange Online information and to be able to retrieve User information and memberlist of admin groups, the automation account need multiple permission.

Assign Permissions by Script

A. Download Permission Script

Permission Update script

B. Retrieve the Azure Automation Managed Identity GUID and insert it in the downloaded script

  1. Go to your Automation Account, in the Identity Section. You can find the Guid of your Managed Identity.
  2. Replace the GUID in $MI_ID = "XXXXXXXXXXX" with the GUID of your Managed Identity.

C. Launch the script with a Global-Administrator account

Attention this script requires MSGraph Modules and Admin Consent to access to your tenant with Microsoft Graph. The script will add 3 permissions to the Managed identity: 1. Exchange Online ManageAsApp permission 2. User.Read.All on Microsoft Graph API 3. Group.Read.All on Microsoft Graph API

D. Exchange Online Role Assignment

  1. As a Global Administrator, go to Roles and Administrators.
  2. Select Global Reader role or Security Reader and click to 'Add assignments'.
  • API Secret: (EnterClick on 'No member selected' and search your Secure Practice API Secret)Managed Identity account Name beginning by the name of your automation account like 'ESI-Collector'. Select it and click on 'Select'.
  • Enable/Disable ConnectionClick Next and validate the assignment by clicking Assign.

meshStack Event Logs1Password

Supported by:meshcloud GmbH1Password

  • Enable/Disable ConnectionWorkspace ID: <variable value provided at install time>
  • Primary Key: <variable value provided at install time>

Microsoft DataverseAtlassian Confluence Audit (via Codeless Connector Framework)

Supported by:Microsoft CorporationMicrosoft Corporation

Microsoft Dataverse is a scalable and secure data platform that enables organizations to store and manage data used by business applications. The Microsoft DataverseAtlassian Confluence Audit data connector provides the capability to ingest Dataverse and Dynamics 365 CRM activity logs from the Microsoft Purview Audit logConfluence Audit Records events into Microsoft Sentinel.Sentinel through the REST API. Refer to API documentation for more information. The connector enables event retrieval to assess potential security risks, monitor collaboration, and diagnose and troubleshoot configuration issues.

Log Analytics table(s):

Table DCR support Lake-only ingestion
DataverseActivityConfluenceAuditLogsNoNo

Data collection rule support: Not currently supported

Prerequisites:

Setup Instructions:

Connect Atlassian Confluence to Microsoft Sentinel

Add one connection per Atlassian Confluence site. Follow the Atlassian API token instructions to create an API token.

  • Data Connectors Grid (configure in portal)

Atlassian Jira Audit (via Codeless Connector Framework)

Supported by:Microsoft Corporation

The Atlassian Jira Audit data connector provides the capability to ingest Jira Audit Records events into Microsoft Sentinel through the REST API. Refer to API documentation for more information. The connector enables event retrieval to assess potential security risks, monitor collaboration, and diagnose and troubleshoot configuration issues.

Log Analytics table(s):

TableDCR supportLake-only ingestion

Supported by:Microsoft Corporation

The Bitglass data connector provides the capability to retrieve security event logs of the Bitglass services and more events into Microsoft Sentinel through the REST API. The connector enables event retrieval to assess potential security risks, monitor collaboration, and diagnose and troubleshoot configuration issues.

Log Analytics table(s):

Follow the instructions to obtain the credentials.

  1. Please contact Bitglass support and obtain the BitglassToken and BitglassServiceURL ntation].
  2. Save credentials for using in the data connector.

STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function

TableDCR supportLake-only ingestion
SyslogYesYes
CiscoSDWANNetflow_CL Yes Yes

Data collection rule support:Workspace transform DCR

Supported by:Commvault

The Commvault Security IQ data connector ingests threat indicator anomaly events from Commvault environments into Microsoft Sentinel, enabling detection and response for threats targeting backup infrastructure such as ransomware and suspicious file operations. Events are stored in the CommvaultAlertsCCF_CL table.

Log Analytics table(s):

Commvault Security IQ Connector Instances

This connector polls Commvault every 30 minutes and ingests threat indicator anomaly events into the CommvaultAlertsCCF_CL table.

  • Data Connectors Grid (configure in portal)

NOTE: The newest version of the ESET PROTECT Platform and Microsoft Sentinel integration pulls not only detections logs but also newly created incidents. If your integration was set up before 20.06.2025, please follow these steps to update it.

Step 1 - Create an API user

Use this instruction to create an ESET Connect API User account with Login and Password.

Step 2 - Create a registered application

Create a Microsoft Entra ID registered application by following the steps in the Register a new application instruction.

Step 3 - Deploy the ESET Protect Platform data connector using the Azure Resource Manager (ARM) template

  1. Click the Deploy to Azure button below.

    aka.ms

  2. Select the name of the Log Analytics workspace associated with your Microsoft Sentinel. Select the same Resource Group as the Resource Group of the Log Analytics workspace.

  3. Type the parameters of the registered application in Microsoft Entra ID: Azure Client ID, Azure Client Secret, Azure Tenant ID, Object ID. You can find the Object ID on Azure Portal by following this path Microsoft Entra ID -> Manage (on the left-side menu) -> Enterprise applications -> Object ID column (the value next to your registered application name).

  4. Provide the ESET Connect API user account Login and Password obtained in Step 1.

  5. Select one or more ESET products (ESET PROTECT, ESET Inspect, ESET Cloud Office Security) from which detections are retrieved.

Exchange Security Insights On-Premises Collector (Azure Monitor)

Supported by:Community

Connector used to send Exchange Server security configuration data to Microsoft Sentinel through the Azure Monitor Log Ingestion API.

Log Analytics table(s):

TableDCR supportLake-only ingestion
ESIAPIExchangeOnPremisesConfig_CLNoNo

Data collection rule support: Not currently supported

Prerequisites:

  • Tenant PermissionsMicrosoft Entra: 'Security Administrator'Permission to create an app registration in Microsoft Entra ID. Typically requires Entra ID Application Developer role or 'Global Administrator'higher.
  • Microsoft Azure: Permission to assign the Monitoring Metrics Publisher role on the workspace's tenant.Data Collection Rule (DCR). This typically requires the Azure RBAC Owner or User Access Administrator role.
  • Micorosft Purview AuditService Account with Organization Management role: Microsoft Purview Audit (Standard or Premium)The service account that runs the scheduled collector task must be activated.a member of the Exchange Organization Management role group.
  • Production DataverseDetailed documentation: Activity logging>NOTE: Detailed installation and usage documentation is available onlyhere.

Setup Instructions:

Note:

NOTE - UPDATE:

For an existing deployment, update the collector script to version 8.0.0.0 or later, before switching to the Azure Monitor Log Ingestion API. See ESI On-Premises Collector Update and Upgrade an existing deployment.For detailed documentation for Production environments. Other types, suchthe following steps, refer to the Official Documentation

1. Deploy the Azure Monitor connector resources

This connector enables the Exchange Server collector to send security configuration data to Microsoft Sentinel through the Azure Monitor Log Ingestion API.

2. Install the ESI Collector on the Exchange management server

Install the collector on a Windows server that has the Exchange Management Shell, Active Directory module for Windows PowerShell, and at least Az.Accounts module.

Script Deployment

Download the latest version of ESI Collector

Download the latest CollectExchSecIns.zip package from https://aka.ms/ESI-ExchangeCollector-Script.

Copy the script folder

Extract the package and copy the collector folder to a server where the Exchange PowerShell cmdlets are available.

Unblock the downloaded package

Before extraction, run Unblock-File -LiteralPath .\CollectExchSecIns.zip. If the package is already extracted, unblock the PowerShell files recursively.

Configure network access

Ensure that the collector can reach Microsoft Entra ID, https://raw.githubusercontent.com (if you accept the script AutoUpdate option), and the Data Collection Endpoint displayed by this connector.

3. Configure the ESI Collector and scheduled task

Run PowerShell as sandbox, doa local administrator and launch setup.ps1 to configure the collector and daily scheduled task.

Here is the documentation for Setup.ps1.

The On-Premises collector uses certificate authentication, using an application secret is an available option but this configuration is not support activity logging.recommended.

See the Certificate creation guide.

  • Tenant ID (Directory ID): <variable value provided at install time>
  • Dataverse Audit SettingsEntra App Registration Application ID: Audit settings must<variable value provided at install time>
  • Data Collection Endpoint URI: <variable value provided at install time>
  • Data Collection Rule Immutable ID: <variable value provided at install time>
  • Stream Name: <variable value provided at install time>

4. Verify the scheduled task

Verify that Setup.ps1 created the daily collector task. Remember the account used by the Scheduled Task needs to be configured both globallya member of the Organization Management group.

If the task is missing, re-run Setup.ps1.

Note

NOTE: Parsers are automatically deployed with the solution. For additional information, see the documentation.

Exchange Security Insights Online Collector (Azure Monitor)

Supported by:Community

Connector used to push Exchange Online Security configuration for Microsoft Sentinel Analysis using Azure Monitor Ingestion API.

Log Analytics table(s):

TableDCR supportLake-only ingestion
ESIAPIExchangeOnlineConfig_CLNoNo

Data collection rule support: Not currently supported

Prerequisites:

  • Microsoft Entra: Permission to create an app registration in Microsoft Entra ID. Typically requires Entra ID Application Developer role or higher.
  • Microsoft Azure: Permission to assign Monitoring Metrics Publisher role on data collection rule (DCR). Typically requires Azure RBAC Owner or User Access Administrator role.
  • microsoft.automation/automationaccounts permissions: Read and at the entity/table level.write permissions to create an Azure Automation with a Runbook is required. For more information, see Dataverse audit settingsAutomation Account.
  • Microsoft.Graph permissions: Group.Read.All, User.Read.All, and AuditLog.Read.All permissions are required to retrieve user and group information linked to Exchange Online assignments. See the documentation to learn more.
  • Exchange Online permissions: Exchange.ManageAsApp permission and Global Reader or Security Reader Role are needed to retrieve the Exchange Online Security Configuration.See the documentation to learn more.
  • (Optional) Log Storage permissions: Storage Blob Data Contributor to a storage account linked to the Automation Account Managed identity or an Application ID is mandatory to store logs.See the documentation to learn more.

Setup Instructions:

NOTE - UPDATE

Note:

NOTE - UPDATE:

For an existing deployment, update the collector script to version 8.0.0.0 or later, before switching to the Azure Monitor Log Ingestion API. See ESI On-Premises Collector Update and Upgrade an existing deployment.For detailed documentation for the following steps, refer to the Official Documentation

STEP 1. Deploy the Azure Monitor connector resources

This connector enables the Exchange Online collector to send configuration data to Microsoft Sentinel through the Azure Monitor Log Ingestion API.

Automated Azure Monitor resource deployment Selecting Deploy creates the Log Analytics table, Data Collection Endpoint (DCE), and Data Collection Rule (DCR). The Azure Automation deployment in the next step creates a system-assigned managed identity and grants it access to the DCR.

STEP 2 - Deploy / Updating the Azure Automation collector

IMPORTANT: Before deploying Azure Automation, record the values below. For new deployment, choose your environment display name (this name will be used in the workbooks - remember the table can contain information from several environments), for example Contoso. The deployment adds the -Cloud suffix when needed.

  • Tenant ID (Directory ID): <variable value provided at install time>
  • Data Collection Endpoint Uri: <variable value provided at install time>
  • Data Collection Rule Immutable ID: <variable value provided at install time>
  • Stream Name: <variable value provided at install time>
  • DataCollectionRuleName: <variable value provided at install time>

Option 1 : Deploy the Azure Automation template for a new deployment

  1. Select the Deploy to Azure button below.

    aka.ms

  2. Check the subscription, Select the resource group, Check the location.

  3. Enter the Automation account name, environment name, tenant ID, DCE URI, DCR immutable ID, and DCR name. To retrieve the DCR name, follow Retrieve the DCR name.

  4. Select Review + create, and then select Create.

The template creates the Automation account with a system-assigned managed identity, imports the required modules, deploys the runbook and daily schedule, creates the configuration variables, and assigns the managed identity to the DCR.

Option 2 : Update an existing Deployment of Azure Automation

Use the following documentation to update an existing Azure Automation deployment. Click Here

STEP 3 - Assign Microsoft Graph and Exchange Online permissions to the managed identity (only for new deployment)

The Automation account managed identity requires application permissions to collect Exchange Online and Microsoft Graph information.

Assign Permissions by Script

A. Download Permission Script

From a secure machine with the Microsoft Graph modules installed, download the Permission Update script.

(The script is also located in the CollectExchSecIns.zip file, so if the On-Premises solution is already deployed this modification can be done on this server.)

Permission Update script

B. Retrieve the Azure Automation managed identity object ID

Open the Automation account, select Identity, and copy the managed identity object ID.

C. Unblock the script and run the script with a Global Administrator account

Run ExchangeOnlinePermSetup.ps1 -MIIDParam <managed-identity-object-id> -TenantId <tenant-id> -InteractiveAuth. The script requires Microsoft Graph modules and admin consent. It assigns Exchange.ManageAsApp, User.Read.All, Group.Read.All, and AuditLog.Read.All.

D. Exchange Online Role Assignment. Do not forget this step !

  1. As a Global Administrator, go to Roles and Administrators.
  2. Select Global Reader role or Security Reader and click to 'Add assignments'.
  • API Secret: (Enter your Secure Practice API Secret)
  • Enable/Disable Connection

Menlo Security

Supported by:Menlo Security

The Menlo Security connector uses the Menlo Security Logs API to ingest Audit, Bandwidth, and Web proxy logs into Microsoft Sentinel. It runs as three timer-triggered Azure Functions, each polling the API every 3 minutes and writing events to custom Log Analytics tables (MenloAudit_CL, MenloBandwidth_CL, MenloWeb_CL).

Log Analytics table(s):

TableDCR supportLake-only ingestion
MenloAudit_CLNoNo
MenloBandwidth_CLNoNo
MenloWeb_CLNoNo

Data collection rule support: Not currently supported

Prerequisites:

  • Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. For more information, see Azure Functions.
  • Menlo Security API Token: A valid Menlo Security API token with permission to access the /api/rep/v2/fetch/client_select endpoint. Obtain this from the Menlo Security admin console.
  • Azure permissions for connector deployment: Deploying the connector's Azure resources (via the Deploy to Azure button in the steps below) requires Owner, or Contributor + User Access Administrator, on the target resource group — the template creates role assignments that grant the Function App's managed identity access to Key Vault, Storage, and the Data Collection Rule (Contributor alone is not sufficient). Creating the custom tables also requires write access to the Log Analytics workspace's resource group.

Setup Instructions:

Connect Microsoft Dataverse audit logs to Microsoft SentinelStep 1 — Deploy the connector infrastructure

ThisClick Deploy to Azure below. On the deployment page:

  • For Resource group, choose Create new and name it MenloSecurityLogs so all connector usesresources stay together and can be removed in one step later.
  • Enter your Log Analytics Workspace Resource Group, then select your workspace from the Office Managementdropdown. Connector resources are deployed automatically in the same region as the selected workspace — no manual region matching is required.
  • Enter your Menlo Security API to get your Dataverse audit logs. token.

The logs will be storedtemplate deploys the Function App, Key Vault, Storage Account, Data Collection Endpoint, and processedData Collection Rule, and creates the MenloAudit_CL, MenloBandwidth_CL, and MenloWeb_CL custom tables in your existingLog Analytics workspace.

aka.ms

To remove the connector later, delete the MenloSecurityLogs resource group and the three Menlo*_CL custom tables from the workspace.

Step 2 — Enable log collection

All log-collection functions are disabled by default. After deployment, navigate to the Function App in the Azure Portal and enable the log types you want to collect:

  1. Open the Function App created by this solution (named menlo-logs-func-<suffix>).
  2. Go to Configuration → Application settings.
  3. For each log type you want to enable, set the corresponding app setting value to 0:
Log typeApp setting nameEnable value
Audit logsAzureWebJobs.TimerTriggerAuditLogs.Disabled0
Bandwidth logsAzureWebJobs.TimerTriggerBandwidthLogs.Disabled0
Web logsAzureWebJobs.TimerTriggerWebLogs.Disabled0
  1. Click Save. Each enabled function will begin polling the Menlo Security API on a 3-minute interval.

Step 3 — Verify data ingestion

After enabling at least one log type, wait approximately 5–10 minutes for the first data to appear. Verify by running the following queries in Microsoft Sentinel workspace. You can findLogs:

MenloAudit_CL | take 10
MenloBandwidth_CL | take 10
MenloWeb_CL | take 10

If no data appears after 15 minutes, check the data in theFunction App's DataverseActivityMonitor table.tab for invocation errors.

meshStack Event Logs

Supported by:meshcloud GmbH

  • Enable/Disable Connection

Microsoft Defender for Cloud Apps

Supported by:Microsoft Corporation

[aka.ms](https://aka.ms/sentinel-ESI-MessageTrackingCustomTable)
  1. Select the preferred Subscription, Resource Group, Location and Analytic Workspace Name.
  2. Click Create to deploy.

Create Custom Table using PowerShell in Cloud Shell

  1. From the Azure Portal, open a Cloud Shell.
  2. Copy and paste and Execute the following script in the Cloud Shell to create the table. $tableParams = @' { "properties": { "schema": { "name": "MessageTrackingLog_CL", "columns": [ { "name": "directionality", "type": "string" }, { "name": "reference", "type": "string" }, { "name": "source", "type": "string" }, { "name": "TimeGenerated", "type": "datetime" }, { "name": "clientHostname", "type": "string" }, { "name": "clientIP", "type": "string" }, { "name": "connectorId", "type": "string" }, { "name": "customData", "type": "string" }, { "name": "eventId", "type": "string" }, { "name": "internalMessageId", "type": "string" }, { "name": "logId", "type": "string" }, { "name": "messageId", "type": "string" }, { "name": "messageInfo", "type": "string" }, { "name": "messageSubject", "type": "string" }, { "name": "networkMessageId", "type": "string" }, { "name": "originalClientIp", "type": "string" }, { "name": "originalServerIp", "type": "string" }, { "name": "recipientAddress", "type": "string" }, { "name": "recipientCount", "type": "string" }, { "name": "recipientStatus", "type": "string" }, { "name": "relatedRecipientAddress", "type": "string" }, { "name": "returnPath", "type": "string" }, { "name": "senderAddress", "type": "string" }, { "name": "senderHostname", "type": "string" }, { "name": "serverIp", "type": "string" }, { "name": "sourceContext", "type": "string" }, { "name": "schemaVersion", "type": "string" }, { "name": "messageTrackingTenantId", "type": "string" }, { "name": "totalBytes", "type": "string" }, { "name": "transportTrafficType", "type": "string" }, { "name": "FilePath", "type": "string" } ] } } } '@
  3. Copy, Replace, Paste and execute the following parameters with your own values: $SubscriptionID = 'YourGUID' $ResourceGroupName = 'YourResourceGroupName' $WorkspaceName = 'YourWorkspaceName'
  4. Execute the Following Cmdlet to create the table: Invoke-AzRestMethod -Path "/subscriptions/$SubscriptionID/resourcegroups/$ResourceGroupName/providers/microsoft.operationalinsights/workspaces/$WorkspaceName/tables/MessageTrackingLog_CL?api-version=2021-12-01-preview" -Method PUT -payload $tableParams

A. Create DCE (If not already created for Exchange Servers)

  1. From the Azure Portal, navigate to Azure Data collection Endpoint.
  2. Click + Create at the top.
  3. In the Basics tab, fill the required fields and give a name to the DCE, like ESI-ExchangeServers.
  4. 'Make other preferable configuration changes', if needed, then click Create.

B. Create a DCR, Type Custom log

  1. From the Azure Portal, navigate to Azure Data collection rules.
  2. Click on 'Create' button.
  3. On 'Basics' tab, fill the Rule name like DCR-Option6-MessageTrackingLogs, select the 'Data Collection Endpoint' with the previously created endpoint and fill other parameters.
  4. In the Resources tab, add your Exchange Servers.
  5. In Collect and Deliver, add a Data Source type 'Custom Text logs' and enter 'C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\MessageTracking*.log' in file pattern, 'MessageTrackingLog_CL' in Table Name. 6.in Transform field, enter the following KQL request : source | extend d = split(RawData,',') | extend TimeGenerated =todatetime(d[0]) ,clientIP =tostring(d[1]) ,clientHostname =tostring(d[2]) ,serverIp=tostring(d[3]) ,senderHostname=tostring(d[4]) ,sourceContext=tostring(d[5]) ,connectorId =tostring(d[6]) ,source=tostring(d[7]) ,eventId =tostring(d[8]) ,internalMessageId =tostring(d[9]) ,messageId =tostring(d[10]) ,networkMessageId =tostring(d[11]) ,recipientAddress=tostring(d[12]) ,recipientStatus=tostring(d[13]) ,totalBytes=tostring(d[14]) ,recipientCount=tostring(d[15]) ,relatedRecipientAddress=tostring(d[16]) ,reference=tostring(d[17]) ,messageSubject =tostring(d[18]) ,senderAddress=tostring(d[19]) ,returnPath=tostring(d[20]) ,messageInfo =tostring(d[21]) ,directionality=tostring(d[22]) ,messageTrackingTenantId =tostring(d[23]) ,originalClientIp =tostring(d[24]) ,originalServerIp =tostring(d[25]) ,customData=tostring(d[26]) ,transportTrafficType =tostring(d[27]) ,logId =tostring(d[28]) ,schemaVersion=tostring(d[29]) | project-away d,RawData and click on 'Destination'.
  6. In 'Destination', add a destination and select the Workspace where you have previously created the Custom Table
  7. Click on 'Add data source'.
  8. Fill other required parameters and tags and create the DCR

Assign the DCR to all Exchange Servers

Add all your Exchange Servers to the DCR

Microsoft Power Automate

Supported by:Microsoft Corporation

Power Automate is a Microsoft service that helps users create automated workflows between apps and services to synchronize files, get notifications, collect data, and more. It simplifies task automation, increasing efficiency by reducing manual, repetitive tasks, and enhancing productivity. The Power Automate data connector provides the capability to ingest Power Automate activity logs from the Microsoft Purview Audit log into Microsoft Sentinel.

Log Analytics table(s):

TableDCR supportLake-only ingestion
PowerAutomateActivityYesYes

Data collection rule support:Workspace transform DCR

Prerequisites:

  • Tenant Permissions: 'Security Administrator' or 'Global Administrator' on the workspace's tenant.
  • Micorosft Purview Audit: Microsoft Purview Audit (Standard or Premium) must be activated.

Setup Instructions:

Connect Microsoft Power Automate audit logs to Microsoft Sentinel

This connector uses the Office Management API to get your Power Automate audit logs. The logs will be stored and processed in your existing Microsoft Sentinel workspace. You can find the data in the PowerAutomateActivity table.

  • Enable/Disable Connection

Microsoft Power Platform Admin Activity

Supported by:Microsoft Corporation

Microsoft Power Platform is a low-code/no-code suite empowering both citizen and pro developers to streamline business processes by enabling the creation of custom apps, automation of workflows, and data analysis with minimal coding. The Power Platform Admin data connector provides the capability to ingest Power Platform administrator activity logs from the Microsoft Purview Audit log into Microsoft Sentinel.

Log Analytics table(s):

TableDCR supportLake-only ingestion
PowerPlatformAdminActivityYesYes

Data collection rule support:Workspace transform DCR

Prerequisites:

  • Tenant Permissions: 'Security Administrator' or 'Global Administrator' on the workspace's tenant.
  • Micorosft Purview Audit: Microsoft Purview Audit (Standard or Premium) must be activated.

Setup Instructions:

Connect Microsoft Power Platform Admin Activity audit logs to Microsoft Sentinel

This connector uses the Office Management API to get your Power Platform administrator audit logs. The logs will be stored and processed in your existing Microsoft Sentinel workspace. You can find the data in the PowerPlatformAdminActivity table.

  • Enable/Disable Connection

Microsoft PowerBI

  1. Select Add.
  2. 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 configuration parameter for the execution of Mimecast Data Connector.

Reference link:/azure/active-directory/develop/quickstart-register-app#add-a-client-secret

STEP 3 - Get Object ID of your application in Microsoft Entra ID

After creating your app registration, follow the steps in this section to get Object ID:

  1. Go to Microsoft Entra ID.
  2. Select Enterprise applications from the left menu.
  3. Find your newly created application in the list (you can search by the name you provided).
  4. Click on the application.
  5. On the overview page, copy the Object ID. This is the AzureEntraObjectId needed for your ARM template role assignment.

STEP 4 - Deploy Mimecast API Connector

IMPORTANT: Before deploying the Mimecast API connector, have the Mimecast API authorization key(s) or Token, readily available.

Azure Resource Manager (ARM) Template

Use this method for automated deployment of the Mimecast Targeted Threat Protection Data connector.

  1. Click the Deploy to Azure button below.

    aka.msaka.ms

  2. Select the preferred Subscription, Resource Group and Region.

  3. Enter the below information :

    a. Location - The location in which the data collection rules and data collection endpoints should be deployed

    b. WorkspaceName - Enter Microsoft Sentinel Workspace Name of Log Analytics workspace

    c. AzureClientID - Enter Azure Client ID that you have created during app registration

    d. AzureClientSecret - Enter Azure Client Secret that you have created during creating the client secret

    e. AzureTenantID - Enter Azure Tenant ID of your Azure Active Directory

    f. AzureEntraObjectID - Enter Object id of your Microsoft Entra App

    g. MimecastBaseURL - Enter Base URL of Mimecast API 2.0 (e.g. https://api.services.mimecast.com)

    h. MimecastClientID - Enter Mimecast Client ID for authentication

    i. MimecastClientSecret - Enter Mimecast Client Secret for authentication

    j. StartDate - Enter the start date in the 'yyyy-mm-dd' format. If you do not provide a date, data from the last 60 days will be fetched automatically. Ensure that the date is in the past and properly formatted

    k. MimecastTTPAttachmentTableName - Enter name of the table used to store TTP Attachment data. Default is 'Ttp_Attachment'

    l. MimecastTTPImpersonationTableName - Enter name of the table used to store TTP Impersonation data. Default is 'Ttp_Impersonation'

    m. MimecastTTPUrlTableName - Enter name of the table used to store TTP Attachment data. Default is 'Ttp_Url'

    n. Schedule - Please enter a valid Quartz cron-expression. (Example: 0 0 */1 * * *) Do not keep the value empty, minimum value is 10 minutes

    l. LogLevel - Please add log level or log severity value. By default it is set to INFO

    o. AppInsightsWorkspaceResourceId - Migrate Classic Application Insights to Log Analytic Workspace which is retiring by 29 Febraury 2024. Use 'Log Analytic Workspace-->Properties' blade having 'Resource ID' property value. This is a fully qualified resourceId which is in format '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/{workspaceName}'

  4. Mark the checkbox labeled I agree to the terms and conditions stated above.

  5. Click Purchase to deploy.

Mimecast Targeted Threat Protection (using Azure Functions)

Supported by:Mimecast

The data connector for Mimecast Targeted Threat Protection provides customers with the visibility into security events related to the Targeted Threat Protection inspection technologies within Microsoft Sentinel. The data connector provides pre-created dashboards to allow analysts to view insight into email based threats, aid in incident correlation and reduce investigation response times coupled with custom alert capabilities. The Mimecast products included within the connector are:

  • URL Protect
  • Impersonation Protect
  • Attachment Protect

Log Analytics table(s):

Table DCR support Lake-only ingestion
MimecastTTPUrl_CL No No
MimecastTTPAttachment_CL No No
MimecastTTPImpersonation_CL No No

Data collection rule support: Not currently supported

Prerequisites:

  • Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. For more information, see Azure Functions.
  • REST API Credentials/permissions: You need to have the following pieces of information to configure the integration:
  • mimecastEmail: Email address of a dedicated Mimecast admin user
  • mimecastPassword: Password for the dedicated Mimecast admin user
  • mimecastAppId: API Application Id of the Mimecast Microsoft Sentinel app registered with Mimecast
  • mimecastAppKey: API Application Key of the Mimecast Microsoft Sentinel app registered with Mimecast
  • mimecastAccessKey: Access Key for the dedicated Mimecast admin user
  • mimecastSecretKey: Secret Key for the dedicated Mimecast admin user
  • mimecastBaseURL: Mimecast Regional API Base URL

The Mimecast Application Id, Application Key, along with the Access Key and Secret keys for the dedicated Mimecast admin user are obtainable via the Mimecast Administration Console: Administration | Services | API and Platform Integrations.

The Mimecast API Base URL for each region is documented here: https://integrations.mimecast.com/documentation/api-overview/global-base-urls/

Setup Instructions:

Resource group

You need to have a resource group created with a subscription you are going to use.

Functions app

You need to have an Azure App registered for this connector to use

  1. Application Id
  2. Tenant Id
  3. Client Id
  4. Client Secret

NOTE: This connector uses Azure Functions to connect to a Mimecast API to pull its logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the Azure Functions pricing page 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 to use Azure Key Vault with an Azure Function App.

Configuration:

STEP 1 - Configuration steps for the Mimecast API

Go to Azure portal ---> App registrations ---> [your_app] ---> Certificates & secrets ---> New client secret and create a new secret (save the Value somewhere safe right away because you will not be able to preview it later)

STEP 2 - Deploy Mimecast API Connector

IMPORTANT: Before deploying the Mimecast API connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the Mimecast API authorization key(s) or Token, readily available.

  • Workspace ID: <variable value provided at install time>
  • Primary Key: <variable value provided at install time>

Deploy the Mimecast Targeted Threat Protection Data Connector:

  1. Click the Deploy to Azure button below.

    aka.ms

  2. Select the preferred Subscription, Resource Group and Location.

  3. Enter the following fields:

  • appName: Unique string that will be used as id for the app in Azure platform
  • objectId: Azure portal ---> Azure Active Directory ---> more info ---> Profile -----> Object ID
  • appInsightsLocation(default): westeurope
  • mimecastEmail: Email address of dedicated user for this integraion
  • mimecastPassword: Password for dedicated user
  • mimecastAppId: Application Id from the Microsoft Sentinel app registered with Mimecast
  • mimecastAppKey: Application Key from the Microsoft Sentinel app registered with Mimecast
  • mimecastAccessKey: Access Key for the dedicated Mimecast user
  • mimecastSecretKey: Secret Key for dedicated Mimecast user
  • mimecastBaseURL: Regional Mimecast API Base URL
  • activeDirectoryAppId: Azure portal ---> App registrations ---> [your_app] ---> Application ID
  • activeDirectoryAppSecret: Azure portal ---> App registrations ---> [your_app] ---> Certificates & secrets ---> [your_app_secret]
  • workspaceId: Azure portal ---> Log Analytics Workspaces ---> [Your workspace] ---> Agents ---> Workspace ID (or you can copy workspaceId from above)
  • workspaceKey: Azure portal ---> Log Analytics Workspaces ---> [Your workspace] ---> Agents ---> Primary Key (or you can copy workspaceKey from above)
  • AppInsightsWorkspaceResourceID : Azure portal ---> Log Analytics Workspaces ---> [Your workspace] ---> Properties ---> Resource ID

Note: If using Azure Key Vault secrets for any of the values above, use the@Microsoft.KeyVault(SecretUri={Security Identifier})schema in place of the string values. Refer to Key Vault references documentation for further details.

  1. Mark the checkbox labeled I agree to the terms and conditions stated above.
  2. Click Purchase to deploy.
  3. Go to Azure portal ---> Resource groups ---> [your_resource_group] ---> [appName](type: Storage account) ---> Storage Explorer ---> BLOB CONTAINERS ---> TTP checkpoints ---> Upload and create empty files on your machine named attachment-checkpoint.txt, impersonation-checkpoint.txt, url-checkpoint.txt and select them for upload (this is done so that date_range for TTP logs are stored in consistent state)

Miro AI Interaction Logs (Beta) (Enterprise Plan + Enterprise Guard)

Supported by:Miro

The Miro AI Interaction Logs data connector enables you to ingest AI interaction logs from Miro into Microsoft Sentinel. AI interaction logs capture user interactions with AI features in Miro: the prompt received from the user, the response returned to them, and the model and tool calls made in between.

This connector is in Beta: the AI interaction logs API may change before general availability.

Key features:

  • Track AI interactions by user, session, and affected object.
  • Follow each step of an interaction: input, model calls, tool calls, and output.
  • Support compliance and eDiscovery requirements.

Requirements:

  • Miro Plan: Enterprise Plan + Enterprise Guard add-on.
  • Collection enabled: A Miro admin turns on Collect AI interaction logs in Admin console > Security > Audit logs > Settings. Only interactions after that are recorded. If the setting is not visible, contact your Miro account manager.
  • OAuth scope: aiinteractionlogs:read.
  • Organization ID: Your Miro organization identifier.

Note: The details column may contain unstructured data that could reveal information used in interactions with the LLM. Azure Monitor truncates any field value longer than 64 KB at ingestion, so a long details value can arrive cut off.

For detailed instructions, refer to the documentation.

Log Analytics table(s):

TableDCR supportLake-only ingestion
MiroAIInteractionLogs_CLNoNo

Data collection rule support: Not currently supported

Prerequisites:

  • Miro Enterprise Plan with Enterprise Guard: Miro Enterprise Plan with Enterprise Guard add-on is required. AI interaction logs are not available on base Enterprise Plan or lower tiers.
  • AI interaction logs collection: A Miro admin must turn on Collect AI interaction logs in Admin console > Security > Audit logs > Settings. Only interactions after that are recorded.
  • Miro OAuth Application: Miro OAuth application with aiinteractionlogs:read scope is required.
  • Miro Organization ID: Your Miro organization ID is required to access AI interaction logs.

Setup Instructions:

Step 1: Verify your Miro plan and enable collection

  1. Ensure your organization has Miro Enterprise Plan with Enterprise Guard add-on.
  2. If you don't have Enterprise Guard yet, contact your Miro account manager to upgrade.
  3. As a Miro admin, open Admin console > Security > Audit logs > Settings and turn on Collect AI interaction logs. Only interactions after that are recorded.
  4. If the setting is not visible, contact your Miro account manager.

Step 2: Choose your setup option

There are two ways to set up the Miro AI Interaction Logs connector.

Option 1 (recommended): Use Enterprise integrations

  • Simplest setup with automatic token generation.
  • Recommended for most users.
  • See Option 1 below.

Option 2 (alternative): Create custom OAuth application

  • More control over OAuth app configuration.
  • For advanced users or custom integration needs.
  • See Option 2 below.

Note: When using Option 1, the integration is automatically tied to the team with the largest number of users in your organization. When using Option 2, you can choose which team to install the app to. However, the team selection does not affect which logs are collected—both options provide organization-wide log access.

Option 1: Enterprise integrations (recommended)

  1. Open Miro Company Settings.
  2. Expand the Apps and integrations section.
  3. Click Enterprise integrations.
  4. Enable the SIEM toggle.
  5. Copy the Access Token value that appears.
  6. Get your Organization IDfrom the browser URL:
    • Look at the browser URL to find your Organization ID.
    • The URL format is: https://miro.com/app/settings/company/{ORGANIZATION_ID}/.
    • Copy your Organization ID from the URL (the numeric value).
  7. Important: Store both the token and Organization ID securely—they provide full access to AI interaction logs.
  8. The token will work until you disable the toggle.
  9. Proceed to Step 3.

One token for all Miro connectors: the SIEM toggle creates one access token with every log scope your organization is entitled to: auditlogs:read (Enterprise Plan), contentlogs:export (Enterprise Guard add-on) and aiinteractionlogs:read (Enterprise Guard add-on with AI interaction logs). If the SIEM toggle was enabled before it offered these scopes, turn it off and on again to get a token that includes them, then update the token in every connector that uses it. Turning the toggle off invalidates its current token, so every connector that uses it fails to poll until it has the new token.

Option 2: Custom OAuth application (alternative)

  1. Go to Miro App Settings.
  2. Click Create new app.
  3. Select Non-expiring access token option during app creation.
  4. Enable the OAuth scope: aiinteractionlogs:read.
  5. Click Install app and get OAuth token.
  6. Authorize the app to access your organization.
  7. Copy the Access Token that is displayed.
  8. Get your Organization ID:
    • Go to Miro Company Settings.
    • Look at the browser URL to find your Organization ID.
    • The URL format is: https://miro.com/app/settings/company/{ORGANIZATION_ID}/.
    • Copy your Organization ID from the URL (the numeric value).
  9. Important: Store both the token and Organization ID securely—they provide full access to AI interaction logs.
  10. The token will work until you uninstall the app.

Step 3: Learn more

For detailed information about Miro AI interaction logs:

Connect to Miro to start collecting AI interaction logs in Microsoft Sentinel.

Step 4: Connect to Miro

Provide the required values below to complete the connection.

  • Organization ID: (Enter your Miro Organization ID)
  • Access token: (Enter your Miro Access Token)
  • Enable/Disable Connection

Miro Audit Logs (Enterprise Plan)

Supported by:Miro

The Miro Audit Logs data connector enables you to ingest organization-wide audit events from Miro into Microsoft Sentinel. Monitor user activities, security events, content access, team changes, and administrative actions to enhance your security operations and compliance capabilities.

Key features:

  • Track user authentication and access patterns.
  • Monitor content creation, sharing, and deletion.
  • Audit team and organization configuration changes.
  • Detect suspicious activities and policy violations.
  • Meet compliance and regulatory requirements.

Requirements:

  • Miro Plan: Enterprise Plan.
  • OAuth scope: auditlogs:read.
  • Role: Company Admin in your Miro organization.

💡 Not on Enterprise Plan yet? Upgrade to Miro Enterprise to unlock audit logs and gain comprehensive visibility into your team's activities in Microsoft Sentinel.

For detailed instructions, refer to the documentation.

Log Analytics table(s):

TableDCR supportLake-only ingestion
MiroAuditLogs_CLYesYes

Data collection rule support:Workspace transform DCR

Prerequisites:

  • Miro Enterprise Plan: Miro Enterprise Plan subscription is required.
  • Miro OAuth Application: Miro OAuth application with auditlogs:read scope and Company Admin role is required.

Setup Instructions:

Step 1: Verify your Miro plan

  1. Ensure your organization has an active Miro Enterprise Plan.
  2. If you need to upgrade, contact Miro Sales or your account manager.
  3. You must be a Company Admin to set up this integration.

Step 2: Choose your setup option

There are two ways to set up the Miro Audit Logs connector.

Option 1 (recommended): Use Enterprise integrations

  • Simplest setup with automatic token generation.
  • Recommended for most users.
  • See Option 1 below.

Option 2 (alternative): Create custom OAuth application

  • More control over OAuth app configuration.
  • For advanced users or custom integration needs.
  • See Option 2 below.

Note: When using Option 1, the integration is automatically tied to the team with the largest number of users in your organization. When using Option 2, you can choose which team to install the app to. However, the team selection does not affect which logs are collected—both options provide organization-wide log access. All integration-relevant events from all teams are included in your logs.

Option 1: Enterprise integrations (recommended)

  1. Open Miro Company Settings.
  2. Expand the Apps and integrations section.
  3. Click Enterprise integrations.
  4. Enable the SIEM toggle.
  5. Copy the Access Token value that appears.
  6. Important: Store the token securely—it provides full access to audit logs.
  7. The token will work until you disable the toggle.
  8. Proceed to Step 3.

One token for all Miro connectors: the SIEM toggle creates one access token with every log scope your organization is entitled to: auditlogs:read (Enterprise Plan), contentlogs:export (Enterprise Guard add-on) and aiinteractionlogs:read (Enterprise Guard add-on with AI interaction logs). If the SIEM toggle was enabled before it offered these scopes, turn it off and on again to get a token that includes them, then update the token in every connector that uses it. Turning the toggle off invalidates its current token, so every connector that uses it fails to poll until it has the new token.

Option 2: Custom OAuth application (alternative)

  1. Go to Miro App Settings.
  2. Click Create new app.
  3. Select Non-expiring access token option during app creation.
  4. Enable the OAuth scope: auditlogs:read.
  5. Click Install app and get OAuth token.
  6. Authorize the app to access your organization.
  7. Copy the Access Token that is displayed.
  8. Important: Store the token securely—it provides full access to audit logs.
  9. The token will work until you uninstall the app.

Step 3: Learn more

For detailed information about Miro audit logs:

Connect to Miro to start collecting audit logs in Microsoft Sentinel.

Step 4: Connect to Miro

Provide your Miro access token below to complete the connection.

  • Access token: (Enter your Miro Access Token)
  • Enable/Disable Connection

Miro Content Logs (Enterprise Plan + Enterprise Guard)

Supported by:Miro

The Miro Content Logs data connector enables you to ingest content activity logs from Miro into Microsoft Sentinel. Part of Miro's Enterprise Guard eDiscovery capabilities, this connector provides content-level visibility for compliance, legal hold, and advanced threat detection.

Key features:

  • Track all content item changes.
  • Monitor content modifications by user and timestamp.
  • Support compliance and eDiscovery requirements.
  • Detect data exfiltration and insider threats.
  • Meet regulatory and legal hold obligations.

Requirements:

  • Miro Plan: Enterprise Plan + Enterprise Guard add-on.
  • OAuth scope: contentlogs:export.
  • Role: Company Admin in your Miro organization.
  • Organization ID: Your Miro organization identifier.

💡 Not on Enterprise Plan yet? Upgrade to Miro Enterprise to unlock advanced security and compliance features for your team's collaboration activities in Microsoft Sentinel.

💡 Need Content Logs? Content activity logging is part of Miro Enterprise Guard, which provides advanced security, compliance, and eDiscovery features. Contact your Miro account manager to add Enterprise Guard to your Enterprise Plan and unlock content-level monitoring in Microsoft Sentinel.

Note: If you only have the base Enterprise Plan (without Enterprise Guard), please use the Miro Audit Logs connector instead for organization-level event monitoring.

For detailed instructions, refer to the documentation.

Log Analytics table(s):

TableDCR supportLake-only ingestion
MiroContentLogs_CLYesYes

Data collection rule support:Workspace transform DCR

Prerequisites:

  • Miro Enterprise Plan with Enterprise Guard: Miro Enterprise Plan with Enterprise Guard add-on is required. Content logs are part of Miro's eDiscovery features and are not available on base Enterprise Plan or lower tiers.
  • Miro OAuth Application: Miro OAuth application with contentlogs:export scope and Company Admin role is required.
  • Miro Organization ID: Your Miro organization ID is required to access content logs.

Setup Instructions:

Step 1: Verify your Miro plan and Enterprise Guard

  1. Ensure your organization has Miro Enterprise Plan with Enterprise Guard add-on.
  2. Content logs are part of Miro's eDiscovery (Enterprise Guard) features.
  3. If you don't have Enterprise Guard yet, contact your Miro account manager to upgrade.
  4. Without Enterprise Guard, use the Miro Audit Logs connector for organization-level monitoring.
  5. You must be a Company Admin to set up this integration.

Step 2: Choose your setup option

There are two ways to set up the Miro Content Logs connector.

Option 1 (recommended): Use Enterprise integrations

  • Simplest setup with automatic token generation.
  • Recommended for most users.
  • See Option 1 below.

Option 2 (alternative): Create custom OAuth application

  • More control over OAuth app configuration.
  • For advanced users or custom integration needs.
  • See Option 2 below.

Note: When using Option 1, the integration is automatically tied to the team with the largest number of users in your organization. When using Option 2, you can choose which team to install the app to. However, the team selection does not affect which logs are collected—both options provide organization-wide log access. All integration-relevant events from all teams are included in your logs.

Option 1: Enterprise integrations (recommended)

  1. Open Miro Company Settings.
  2. Expand the Apps and integrations section.
  3. Click Enterprise integrations.
  4. Enable the eDiscovery toggle.
  5. Copy the Access Token value that appears.
  6. Get your Organization IDfrom the browser URL:
    • Look at the browser URL to find your Organization ID.
    • The URL format is: https://miro.com/app/settings/company/{ORGANIZATION_ID}/.
    • Copy your Organization ID from the URL (the numeric value).
  7. Important: Store both the token and Organization ID securely—they provide full access to content logs.
  8. The token will work until you disable the toggle.
  9. Proceed to Step 3.

Alternative: one token for all Miro connectors. Instead of the eDiscovery toggle, you can use the SIEM toggle. It creates one access token with every log scope your organization is entitled to: auditlogs:read (Enterprise Plan), contentlogs:export (Enterprise Guard add-on) and aiinteractionlogs:read (Enterprise Guard add-on with AI interaction logs). If the SIEM toggle was enabled before it offered these scopes, turn it off and on again to get a token that includes them, then update the token in every connector that uses it. Turning the toggle off invalidates its current token, so every connector that uses it fails to poll until it has the new token.

Option 2: Custom OAuth application (alternative)

  1. Go to Miro App Settings.
  2. Click Create new app.
  3. Select Non-expiring access token option during app creation.
  4. Enable the OAuth scope: contentlogs:export.
  5. Click Install app and get OAuth token.
  6. Authorize the app to access your organization.
  7. Copy the Access Token that is displayed.
  8. Get your Organization ID:
    • Go to Miro Company Settings.
    • Look at the browser URL to find your Organization ID.
    • The URL format is: https://miro.com/app/settings/company/{ORGANIZATION_ID}/.
    • Copy your Organization ID from the URL (the numeric value).
  9. Important: Store both the token and Organization ID securely—they provide full access to content logs.
  10. The token will work until you uninstall the app.

Step 3: Learn more

For detailed information about Miro content logs and eDiscovery:

Connect to Miro to start collecting content logs in Microsoft Sentinel.

Step 4: Connect to Miro

Provide the required values below to complete the connection.

  • Organization ID: (Enter your Miro Organization ID)
  • Access token: (Enter your Miro Access Token)
  • Enable/Disable Connection

MISP2Sentinel

  • Data Connectors Grid (configure in portal)

Plugin 'Message Tracking' for Exchange Security Insights Online Collector (Azure Monitor)

Supported by:Community

Plugin Connector used in addition to Exchange Security Insights Online Collector (Azure Monitor) to collect MOnline Message Tracking using Azure Monitor Ingestion API.

Log Analytics table(s):

TableDCR supportLake-only ingestion
ExchangeOnlineMessageTracking_CLNoNo

Data collection rule support: Not currently supported

Prerequisites:

  • Microsoft Entra: Permission to create an app registration in Microsoft Entra ID. Typically requires Entra ID Application Developer role or higher.
  • Microsoft Azure: Permission to assign Monitoring Metrics Publisher role on data collection rule (DCR). Typically requires Azure RBAC Owner or User Access Administrator role.

Setup Instructions:

NOTE

Note:

NOTE:

You need to install the Modern Exchange Online Collector Data Connector before to be able to use this connector.

STEP 1. Create ARM Resources and Provide the Required Permissions

This connector enables your Exchange Online Collector Message Tracking to push Exchange Online Message Tracking directly to Microsoft Sentinel via the Azure Monitor Ingestion API.

Automated Configuration and Secure Data Ingestion with Entra Application Clicking on "Deploy" will trigger the creation of a Log Analytics table and a Data Collection Rule (DCR). It will then create an Entra application, link the DCR to it, and set the entered secret in the application. This setup enables data to be sent securely to the DCR using an Entra token.

STEP 2 - Activate Message Tracking Plugin in the Collector.

To enable the Message Tracking Plugin, you need to modify the configuration of the Exchange Online Collector. This involves adding a specific section to the collector's configuration file, which will activate the plugin and allow it to start collecting message tracking data.

  • Tenant ID (Directory ID): <variable value provided at install time>
  • Entra App Registration Application ID: <variable value provided at install time>
  • Entra App Registration Secret: <variable value provided at install time>
  • Data Collection Endpoint Uri: <variable value provided at install time>
  • Data Collection Rule Immutable ID: <variable value provided at install time>
  • Stream Name: <variable value provided at install time>

Configure Instance

To configure the instance, you need to update the Exchange Online Collector configuration file with the provided parameters. This will enable the Message Tracking Plugin to send data to Microsoft Sentinel via the Azure Monitor Ingestion API.

Deploy Message Tracking Instance Scheduler - Azure Resource Manager (ARM) Template

Use this method for automated deployment of the 'ESI Exchange Online Security Configuration Message Tracking Plugin' connector.

  1. Click the Deploy to Azure button below.

    aka.ms

  2. Select the preferred Subscription, Resource Group and Location.

  3. Enter the Workspace ID, Workspace Key, Tenant Name, 'and/or Other required fields'.

  4. Mark the checkbox labeled I agree to the terms and conditions stated above.

  5. Click Purchase to deploy.

Prancer Data Connector

Supported by:Prancer PenSuiteAI Integration

  • Data Connectors Grid (configure in portal)

QCrypton PQC Scanner (via Codeless Connector Framework)

Supported by:QCrypton, Inc.

The QCrypton PQC Scanner data connector provides the capability to ingest post-quantum cryptography readiness findings from your Azure environment into Microsoft Sentinel through the QCrypton API. Findings include Key Vault key posture (RSA/ECC vs. PQ-hybrid), TLS certificate signature algorithms on public endpoints, Storage Account and App Service TLS configuration, and CMK provenance.

Log Analytics table(s):

TableDCR supportLake-only ingestion
PQReadiness_CLNoNo

Data collection rule support: Not currently supported

Prerequisites:

  • QCrypton API Key: A QCrypton PQC Scanner API key is required. Obtain one from the QCrypton Portal.

Setup Instructions:

Connect QCrypton PQC Scanner to Microsoft Sentinel

This connector polls the QCrypton PQC Scanner API to retrieve post-quantum cryptography readiness findings and ingest them into the PQReadiness_CL table in your Log Analytics workspace.

  1. API Key Obtain your QCrypton API key from the QCrypton Portal. Navigate to Settings > API Keys and generate a key with read access to scan findings.
  2. API Server URL Enter the base URL of your QCrypton API server. The default is https://api.qcrypton.com. If you use a dedicated or regional instance, enter the URL provided by QCrypton.
  • QCrypton API Key: (Enter your QCrypton API key)
  • QCrypton API Server URL: (https://api.qcrypton.com)
  • Enable/Disable Connection

QscoutAppEventsConnector (via Codeless Connector Framework)

Supported by:Quokka

  • Auth Events Stream Name: <variable value provided at install time>
  • Email Forensics Events Stream Name: <variable value provided at install time>

RedRays SAP Security Findings

Supported by:RedRays, Inc.

Bring RedRays SAP security findings into Microsoft Sentinel. Review vulnerability assessments, ABAP code findings, BTP security, segregation of duties, profile parameter checks and password security in one workbook, with analytics rules for findings that need attention. RedRays pushes data on a schedule you choose through the Azure Monitor Logs Ingestion API and stays in your existing on-premises or cloud environment. This connector does not collect SAP Security Audit Log events or populate ABAPAuditLog. You need a RedRays license with Microsoft Sentinel integration. Azure ingestion and retention charges apply.

Log Analytics table(s):

TableDCR supportLake-only ingestion
RedRaysExportHealth_CLNoNo

Data collection rule support: Not currently supported

Prerequisites:

  • Microsoft Entra: Permission to create an app registration in Microsoft Entra ID. Typically requires the Application Developer role or higher.
  • Microsoft Azure: Permission to assign the Monitoring Metrics Publisher role on data collection rules. Typically requires the Owner or User Access Administrator role.
  • RedRays settings access: Permission to configure the Microsoft Sentinel integration in RedRays.

Setup Instructions:

1. Deploy the push connector resources

Select Deploy to create a data collection endpoint (DCE), a data collection rule (DCR) and the eight RedRays tables in this workspace. Microsoft Sentinel also creates a Microsoft Entra app registration with a client secret and grants it the Monitoring Metrics Publisher role on the DCR, so RedRays can send data with OAuth 2.0 client credentials. Workspace shared keys are not used.

Note: The client secret is shown only once, right after deployment. Copy it immediately. If you miss it, open Microsoft Entra ID > App registrations, select RedRays SAP Security Findings, and create a new client secret under Certificates & secrets.

2. Configure RedRays

In RedRays, open Platform Settings > Microsoft Sentinel and enter the values below. Choose the modules to export and how often to send data. Keep baseline alerting disabled for the first import, then save and enable the integration. RedRays needs outbound HTTPS access to Microsoft Entra and the data collection endpoint. No inbound connection is required.

  • Tenant ID: <variable value provided at install time>
  • Application (client) ID: <variable value provided at install time>
  • Client secret: <variable value provided at install time>
  • Ingestion endpoint (DCE URI): <variable value provided at install time>
  • DCR immutable ID: <variable value provided at install time>

3. Verify delivery

Send a test event from RedRays, then wait for a scheduled export. Query RedRaysExportHealth_CL for RecordKind == 'HEARTBEAT'. A successful test means Azure accepted the request; the record may take a few minutes to appear in queries. RedRays sends each module to its own stream (Custom-RedRaysExportHealth_CL, Custom-RedRaysScanRuns_CL, Custom-RedRaysVulnerabilities_CL, Custom-RedRaysAbapFindings_CL, Custom-RedRaysCloudFindings_CL, Custom-RedRaysSoDFindings_CL, Custom-RedRaysProfileChecks_CL and Custom-RedRaysPasswordFindings_CL) on the same DCR.

4. Enable security content

Open Manage solution to create the workbook and selected analytics rules from templates. Review the initial findings before enabling rules. Most finding rules alert on actionable High or Critical candidates. The profile rule raises Medium severity alerts for VULNERABLE checks. The workbook flags heartbeats older than 60 minutes; adjust the threshold above your export interval and expected ingestion delay. Disable equivalent rules from earlier RedRays deployments to avoid duplicate alerts. For help, contact [email protected].

RSA ID Plus Admin Logs Connector

Supported by:RSA Support Team

Supported by:Microsoft Corporation

The Sophos Endpoint Protection data connector provides the capability to ingest Sophos eventsSophos events and Sophos alertsSophos alerts into Microsoft Sentinel. Refer to Sophos Central Admin documentation for more information.

Log Analytics table(s):

Table DCR support Lake-only ingestion
WindowsFirewallYesYes

Data collection rule support: Not currently supportedWorkspace transform DCR

Windows Firewall Events via AMA

Table DCR support Lake-only ingestion
ASimNetworkSessionLogsYesYes

Data collection rule support: Not currently supportedWorkspace transform DCR

Windows Forwarded Events

  • Engine (optional): (default)
  • Engine Group (optional): (default)

WithSecure Elements API (Azure Function)

Supported by:WithSecure

[Deprecated] This Azure Function based connector is deprecated and is no longer actively maintained. Please use the WithSecure Elements via Codeless Connector Framework (CCF) solution instead, which provides the same data ingestion without the need to deploy and maintain an Azure Function. New deployments should use the CCF solution.

WithSecure Elements is the unified cloud-based cyber security platform designed to reduce risk, complexity, and inefficiency.

Elevate your security from your endpoints to your cloud applications. Arm yourself against every type of cyber threat, from targeted attacks to zero-day ransomware.

WithSecure Elements combines powerful predictive, preventive, and responsive security capabilities - all managed and monitored through a single security center. Our modular structure and flexible pricing models give you the freedom to evolve. With our expertise and insight, you'll always be empowered - and you'll never be alone.

With Microsoft Sentinel integration, you can correlate security events data from the WithSecure Elements solution with data from other sources, enabling a rich overview of your entire environment and faster reaction to threats.

With this solution Azure Function is deployed to your tenant, polling periodically for the WithSecure Elements security events.

For more information visit our website at: https://www.withsecure.com.

Log Analytics table(s):

TableDCR supportLake-only ingestion
WsSecurityEvents_CLYesYes

Data collection rule support:Workspace transform DCR

Prerequisites:

  • Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. For more information, see Azure Functions.
  • WithSecure Elements API client credentials: Client credentials are required. See the documentation to learn more.

Setup Instructions:

1. Create WithSecure Elements API credentials

Follow the user guide to create Elements API credentials. Save credentials in a safe place.

2. Create Microsoft Entra application

Create new Microsoft Entra application and credentials. Follow the instructions and store values of Directory (tenant) ID, Object ID, Application (client) ID and Client Secret (from client credentials field). Remember to store Client Secret in a safe place.

3. Deploy Function App

NOTE: This connector uses Azure Functions to pull logs from WithSecure Elements. This might result in additional data ingestion costs. Check the Azure Functions pricing page for details.

(Optional Step) Securely store Microsoft Entra client credentials and WithSecure Elements API client credentials in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. Follow these instructions to use Azure Key Vault with an Azure Function App.

IMPORTANT: Before deploying the WithSecure Elements connector, have the Workspace Name (can be copied from the following), data from Microsoft Entra (Directory (tenant) ID, Object ID, Application (client) ID and Client Secret), as well as the WithSecure Elements client credentials, readily available.

  • Workspace Name: <variable value provided at install time>

Deploy all the resources related to the connector

  1. Click the Deploy to Azure button below.

    aka.ms

  2. Select the preferred Subscription, Resource Group and Location.

  3. Enter the Workspace ID, Entra Client ID, Entra Client Secret, Entra Tenant ID, Elements API Client ID, Elements API Client Secret.

Note: If using Azure Key Vault secrets for any of the values above, use the@Microsoft.KeyVault(SecretUri={Security Identifier})schema in place of the string values. Refer to Key Vault references documentation for further details. 4. You can also fill in optional fields: Elements API url, Engine, Engine Group. Use default value of Elements API url unless you have some special case. Engine and Engine Group map to security events request parameters, fill in those parameters if you are interested only in events from specific engine or engine group, in case you want to receive all security events leave the fields with default values. 5. Mark the checkbox labeled I agree to the terms and conditions stated above. 6. Click Purchase to deploy.

Wiz for Microsoft Sentinel

Supported by:Wiz Prerequisites:

  • Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. For more information, see Azure Functions.
  • REST API Credentials/permissions: API token is required. For more information, see API tokenAPI token

Setup Instructions: