Microsoft Sentinel
Forward the audit log to Microsoft Sentinel with the Logs Ingestion API, and prove it works
Sentinel is a set of SIEM capabilities layered on a Log Analytics workspace. Events are ingested into the workspace, so everything below works against a plain Log Analytics workspace; enabling Sentinel on top changes nothing about the delivery path.
What it costs to try
You do not need to enable Sentinel to validate ingestion, and doing so starts a clock: Sentinel's own trial is 31 days at 10 GB/day, on new workspaces only. Validate against the workspace first, enable Sentinel afterwards if you want to demonstrate the analyst experience.
Overview
Three things have to line up: the token (Entra app + role assignment), the shape (a JSON array matching the DCR stream declaration), and the destination (a custom table with a TimeGenerated column).
Part 1 — Azure setup
1. Create the custom table
In your Log Analytics workspace, create a custom table named CISOAssistantAudit_CL. Custom table names must carry the _CL suffix.
If you create the table through the Azure portal using sample data, the DCR and its transformation are generated for you. Creating it any other way means building the DCR by hand, as below.
2. Create the data collection rule
Create a DCR with "kind": "Direct". Since March 2024 such a DCR exposes its own logsIngestion endpoint, so a separate data collection endpoint is only needed for Private Link or for older DCRs.
The stream declaration must match what CISO Assistant sends. The OCSF event has seven scalar fields and six nested objects, so the nested ones are declared dynamic:
The extra extend clauses are optional conveniences — they lift the most-queried values out of the nested objects into flat columns. Add matching columns to the custom table if you keep them.
3. Register the application
Create a Microsoft Entra app registration and generate a client secret. Record the Application (client) ID, the Directory (tenant) ID, and the secret Value.
4. Grant the app access to the DCR
5. Collect the values you need
Ingestion endpoint
DCR → JSON view → logsIngestion endpoint (or the DCE hostname)
DCR immutable ID
DCR → Overview
Stream name
The key in streamDeclarations, e.g. Custom-CISOAssistantAudit
Tenant ID, client ID, secret
The app registration
Part 2 — CISO Assistant setup
Enable Audit log forwarding under Settings → Feature flags.
Open the Audit log forwarding tab in Settings and click Add audit sink.
Set Transport to
HTTPand Event format toOCSF.Set URL to the ingestion endpoint, assembled as:
For example:
Set Body envelope to JSON array.
Set Authentication to OAuth 2.0 client credentials, then fill in:
Token endpoint
https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token
Client ID
Application (client) ID
Client secret
The secret Value
Scope
https://monitor.azure.com/.default
Leave HTTP headers empty. The bearer token is added automatically; static headers are for collectors that authenticate with a fixed token instead.
Optionally restrict Target Domains. Leave empty to forward events from all domains.
Save.
Request payload
Each audit entry is sent as its own request: a JSON array holding exactly one OCSF event. Entries are never batched into a single request.
A representative body, for an update to an applied control:
The body is sent minified; it is indented here for readability. Things to know when building the stream declaration and the transformation:
time
Epoch milliseconds, integer. There is no TimeGenerated in the body; the transformation derives it.
activity_id, api.operation
1 / create, 2 / read, 3 / update, 4 / delete. type_uid is always 600300 + activity_id.
actor
{} when the change has no user behind it, such as a system task.
src_endpoint
{} when no client IP was recorded.
metadata.correlation_uid
Omitted when the entry has no request correlation id.
unmapped.changes
Free-form. A plain field is [old, new]. A many-to-many change arrives as its own event, shaped {"owner": {"type": "m2m", "operation": "add", "objects": ["John Smith"]}}. Keep it dynamic.
unmapped.folder_id
The domain the object belongs to; null for objects outside any domain.
Part 3 — Verify it works
Generate an event
Make any tracked change — create an applied control, rename a domain, deactivate a user. A change produces one or more audit entries — a many-to-many change, such as editing an object's owners, is logged separately — each delivered asynchronously by the background worker. Entries from the same request share a CorrelationId.
Query the workspace
In Log Analytics → Logs, or in Sentinel under Logs:
A successful run looks like this — one row per change, with the actor, the operation and the object:
Confirm the round trip, not just the arrival
Delivery is proven when the row matches the change you made. Check three things:
Operationiscreate,updateordelete, matching what you did.Objectis the object's name as it appears in CISO Assistant.Changesholds the field-level diff — for a rename,{"name": ["Old", "New"]}.
Confirm token renewal
The point of client credentials is that nothing expires silently. Entra access tokens last roughly an hour; CISO Assistant caches each token until a minute before expiry, then re-mints it.
To prove renewal rather than assume it, leave the sink running and make a change more than an hour after the first one. A row from the second change confirms the token was renewed without intervention.
Backfill anything missed
If events were generated before the sink was working, use Replay events on the sink and pick a From date. Historical entries are re-read from the database and re-queued, so a misconfigured first attempt costs nothing.
Troubleshooting
403 Forbidden
The Monitoring Metrics Publisher role is missing on the DCR, or was assigned less than 30 minutes ago. Check it is on the DCR, not the workspace.
400 Bad Request
Body envelope is not set to JSON array, or the payload does not match the stream declaration.
401 Unauthorized, repeatedly
Wrong scope, wrong tenant in the token endpoint, or an expired client secret. CISO Assistant retries once with a fresh token before backing off, so a persistent 401 is a credential problem, not a timing one.
invalid_scope from the token endpoint
Try the single/double-slash variant of https://monitor.azure.com/.default.
404 Not Found
The DCR immutable ID or the stream name in the URL is wrong. The stream name must match the streamDeclarations key exactly, including the Custom- prefix.
Events accepted, nothing in the table
The DCR transformation dropped the rows, or outputStream names a table that does not exist. Verify outputStream is Custom-<table>_CL.
Rows present, TimeGenerated wrong
The transformKql is missing the epoch-milliseconds conversion of time.
Table creation fails: Columns 'time' are invalid or reserved
Leave time out of the table; the transformation drops it after deriving TimeGenerated.
Nothing sent at all
The audit_log_forwarding feature flag is off, the sink is inactive, or Target Domains excludes the domain you changed.
Related
Audit log forwarding — transports, event formats, replay, and the OCSF payload reference.
Audit log — the source record being forwarded.
Feature flags — enabling the capability.
Last updated
Was this helpful?