Daily Defender News
Aboutmerill.net
Microsoft Sentinel
Cloud and workloads

Microsoft Sentinel Migration: Select a Data Ingestion Tool

4 September 2026Doc update+38 / −33 lines

In brief

The page updates its title, date, metadata, section headings, navigation anchors, and step numbering for ingestion methods including LightIngest, Azure Blob Storage, Azure Data Factory, and AzCopy.

What Defender admins need to know

Administrators should use the revised headings and anchors when navigating or linking to this guidance. No action is specified.

Summaries are generated from the documentation change itself.

Documentation change

View full page diffView on Microsoft Learn

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

title: "Microsoft Sentinel migration:Migration: Select a data ingestion toolData Ingestion Tool" description: Select a tool to transfer your historical data to the selected target platform. author: EdB-MSFT ms.author: edbaynash ms.topic: how-to ms.date: 06/15/07/01/2026 ai-usage: ai-assisted ms.custom: msecd-doc-authoring-10141016

#Customer intent: As a data engineer, I want to select the appropriate data ingestion tool so that I can efficiently transfer historical data to my target platform.

Microsoft Sentinel data lake Azure Data Explorer Azure Blob Storage General tools
•- Azure Monitor custom log ingestion tool
•- Direct API		 •- LightIngest
•- Logstash		 •- Azure Data Factory or Azure Synapse
•- AzCopy		 •- Azure Data Box
•- SIEM data migration accelerator

Microsoft Sentinel data lake

Azure Monitor custom log ingestion tool

The Azure Monitor Custom Log Ingestion Tool on GitHub is a PowerShell script that sends custom data to an Azure Monitor Logs workspace. You can point the script to the folder where all your log files reside, and the script pushes the files to that folder. The script accepts a CSV or JSON format for log files.

Direct API

With this option, you ingest your custom logs into Azure Monitor Logs. For more information, see Tutorial: Send data to Azure Monitor Logs with Logs ingestion API. You ingest the logs with a PowerShell script that uses a REST API. Alternatively, you can use any other programming language to perform the ingestion, and you can use other Azure services to abstract the compute layer, such as Azure Functions or Azure Logic Apps.

Azure Data Explorer

Azure Data Explorer (ADX) supports several data ingestion methods. For more information, see Azure Data Explorer data ingestion overview.

Review the LightIngest and Logstash, two methods that are better tailored to the data migration use case.

Use LightIngest for data ingestion

ADX has developed the LightIngest utility specifically for the historical data migration use case. You can use LightIngest to copy data from a local file system or Azure Blob Storage to ADX.

Here are a few main benefits and capabilities of LightIngest:

  • Because there's no time constraint on ingestion duration, LightIngest is most useful when you want to ingest large amounts of data.
  • LightIngest is useful when you want to query records according to the time they were created, and not the time they were ingested.
  • You don't need to deal with complex sizing for LightIngest, because the utility doesn't perform the actual copy. LightIngest informs ADX about the blobs that need to be copied, and ADX copies the data.

If you choose LightIngest, review these tips and best practices.

  • To speed up your migration and reduce costs, increase the size of your ADX cluster to create more available nodes for ingestion. Decrease the size once the migration is over.
  • For more efficient queries after you ingest the data to ADX, ensure that the copied data uses the timestamp for the original events. The data shouldn't use the timestamp from when the data is copied to ADX. You provide the timestamp to LightIngest as the path of file name as part of the CreationTime property.
  • If your path or file names don't include a timestamp, you can still instruct ADX to organize the data using a partitioning policy.

Logstash

Logstash is an open source, server-side data processing pipeline that ingests data from many sources simultaneously, transforms the data, and then sends the data to your favorite "stash". Learn how to ingest data from Logstash to Azure Data Explorer. Logstash runs on Windows, Linux and macOS Machines.

To optimize performance, configure the Logstash tier size according to the events per second. We recommend that you use LightIngest wherever possible, because LightIngest relies on the ADX cluster computing to perform the copy.

Ingest data into Azure Blob Storage

You can ingest data to Azure Blob Storage in several ways.

Review Azure Data Factory or Azure Synapse, which are better tailored to the data migration use case.

Use Azure Data Factory or Azure Synapse to copy data

To use the Copy activity in Azure Data Factory (ADF) or Synapse pipelines:

  1. Create and configure a self-hosted integration runtime. This component is responsible for copying the data from your on-premises host.
  2. Create linked services for the source data store (filesystem and the sink data store blob storage.
  3. To copy the data, use the Copy data tool. Alternatively, you can use method such as PowerShell, Azure portal, a .NET SDK, and so on.

Use AzCopy to copy data

AzCopy is a simple command-line utility that copies files to or from storage accounts. AzCopy is available for Windows, Linux, and macOS. Learn how to copy on-premises data to Azure Blob storage with AzCopy.

You can also use these options to copy the data:

In a scenario where the source SIEM doesn't have good connectivity to Azure, ingesting the data using tools such as AzCopy, LightIngest, or Azure Data Factory might be slow or even impossible. To address this scenario, you can use Azure Data Box to copy the data locally from the customer's data center into an appliance, and then ship that appliance to an Azure data center. While Azure Data Box isn't a replacement for AzCopy or LightIngest, you can use this tool to accelerate the data transfer between the customer data center and Azure.

Azure Data Box offers three different SKUs, depending on the amount of data to migrate:

After you complete the migration, the data is available in a storage account under one of your Azure subscriptions. You can then use AzCopy, LightIngest, or Azure Data Factory to ingest data from the storage account.

Use the SIEM data migration accelerator

In addition to selecting an ingestion tool, your team needs to invest time in setting up the foundation environment. To ease this process,environment setup, you can use the SIEM data migration accelerator, which automates the following tasks:

  • Deploys a Windows virtual machine that will be used to move the logs from the source to the target platform
  • Downloads and extracts the following tools into the virtual machine desktop:
  • Deploys the target platform that will host your historical logs:
    • Azure Storage account (Azure Blob Storage)
    • Azure Data Explorer cluster and database
    • Azure Monitor Logs workspace (Basic Logs; enabled with Microsoft Sentinel)

To use the SIEM data migration accelerator:

  1. From the SIEM data migration accelerator page, click Deploy to Azure at the bottom of the page, and authenticate.
  2. Select Basics, select your resource group and location, and then select Next.
  3. Select Migration VM, and do the following:
    • Type the virtual machine name, username and password.
    • Select an existing vNet or create a new vNet for the virtual machine connection.
    • Select the virtual machine size.
    • For Azure Blob Storage accounts, select an existing account. If you don't have an account, provide a new account name, type, and redundancy.
    • For Azure Monitor Logs, type the name of the new workspace.

Next stepsstep

In this article, you learned how to select a tool to ingest your data into the target platform.

[!div class="nextstepaction"] Ingest your data