Microsoft Sentinel Forwarder
Forwarding Logs from Apica Ascent to Microsoft Sentinel
This guide explains how to forward logs from Apica Ascent into Microsoft Sentinel using the Azure Log Analytics HTTP Data Collector API.
Microsoft Sentinel does not provide a standalone ingestion endpoint. Instead, it consumes data stored in an Azure Log Analytics workspace. Logs forwarded from Apica into Log Analytics automatically become available to Sentinel for querying, analytics rules, and incident generation.
Architecture Overview
Apica Ascent
↓
Azure Log Analytics Workspace
↓
Microsoft SentinelApica forwards logs to the Log Analytics HTTP Data Collector API
Azure stores the data in a custom log table
Sentinel queries and analyzes the data from that table
Prerequisites
Before configuring the forwarder, ensure the following:
A Log Analytics workspace exists
Microsoft Sentinel is enabled on that workspace
You have one of the following Azure roles on the workspace:
Log Analytics Contributor
Monitoring Contributor
Owner
You can access Azure Cloud Shell (browser-based CLI)
Required Azure Values
You will need the following values from Azure:
Workspace ID
GUID of the Log Analytics workspace
Shared Key
Primary shared key for the workspace
Resource ID
Azure resource ID of the workspace
DNS Name
Log Analytics ingestion endpoint suffix
Step 1: Retrieve the Workspace ID
Open Azure Portal
Navigate to Log Analytics workspaces
Select your workspace
On the Overview page, copy:
Workspace ID
Step 2: Retrieve the Shared (Primary) Key using Azure Cloud Shell
The Azure portal no longer reliably displays shared keys. Use Cloud Shell instead.
In the Azure portal, click the Cloud Shell ( >_ ) icon
Select Bash if prompted
Paste and run the following command (replace values):
Copy the value of:
This value will be used as the Shared key in Apica.
Step 3: Retrieve the Workspace Resource ID
In Azure Portal, open the Log Analytics workspace
Click Properties
Copy the full Resource ID
Example:
Step 4: Configure the Apica Ascent Forwarder
Fill out the forwarder configuration as follows:
Workspace ID
Log Analytics Workspace ID (GUID)
DNS name
.ods.opinsights.azure.com
Shared key
Primary shared key
Log type
"Use Sourcetype in log as log type" as default
"Provide log type manually" for custom naming
Type
ApicaAscentLogs (example)
Resource ID
Full workspace resource ID
Queue policy
Drop incoming events
Filter forward
true
Name
azure-sentinel-forwarder (example)
Step 5: Verify Log Ingestion
Once logs are forwarded, verify ingestion in Log Analytics.
Find the Custom Table
Custom logs appear as:
Example:
Verification Query
Last updated
Was this helpful?