Skip to main content
Sumo Logic

Microsoft Azure Activity Log

Configure an HTTP Source to ingest Microsoft Azure Activity Log messages and to be parsered by CSE's system parser for Azure Activity Log.

This page has instructions for collecting Azure Activity log messages and sending them to Sumo Logic to be ingested by CSE.

Step 1: Configure CIP collection

In this step, you configure an HTTP Source to collect Azure Activity log messages. You can configure the source on an existing Hosted Collector or create a new collector. If you’re going to use an existing collector, jump to Configure an HTTP Source below. Otherwise, create a new collector as described in Configure a hosted collector below, and then create the HTTP Source on the collector.

Configure a Hosted Collector

  1. In Sumo Logic CIP, select Manage Data > Collection > Collection.
  2. Click Add Collector.
  3. Click Hosted Collector.
  4. The Add Hosted Collector popup appears.
    add-hosted-collector.png
  5. Name. Provide a Name for the Collector.
  6. Description. (Optional)
  7. Category. Enter a string to tag the output collected from the source. The string that you supply will be saved in a metadata field called _sourceCategory
  8. Fields
    1. If you are planning that all the sources you add to this collector will forward log messages to CSE, click the +Add Field link, and add a field whose name is _siemForward and value is true. This will cause the collector to forward all of the logs collected by all of the sources on the collector to CSE.
    2. If all sources in this collector will be Microsoft Azure sources, add an additional field with key _parser and value /Parsers/System/Microsoft/Microsoft Azure JSON.

Configure an HTTP Source

  1. In the Sumo Logic web app, select Manage Data > Collection > Collection
  2. Navigate to the Hosted Collector where you want to create the source.
  3. On the Collectors page, click Add Source next to a Hosted Collector.
  4. Select HTTP Logs & Metrics
  5. The page refreshes.
    http-source.png
  6. Name. Enter a name for the source. 
  7. Description. (Optional) 
  8. Source Host. (Optional) Enter a string to tag the messages collected from the source. The string that you supply will be saved in a metadata field called _sourceHost.
  9. Source Category. Enter a string to tag the output collected from the source. The string that you supply will be saved in a metadata field called _sourceCategory.
  10. Fields. If you are not parsing all sources in the hosted collector with the same parser, click the +Add Field link, and add a field whose name is _parser with value /Parsers/System/Microsoft/Microsoft Azure JSON.
  11. Advanced Options for Logs. For information about the optional advance options you can configure, see HTTP Logs and Metrics Source.
  12. Click Save.
  13. Make a note of the HTTP Source URL that is displayed. You’ll supply it in Step 2 below.

Step 2: Configure Azure Activity Log

In this step you configure Azure Activity Log to send log messages to CIP. For instructions, see steps for Collect Logs for the Azure Audit App from Event Hub.

Step 3: Verify ingestion

In this step, you verify that your logs are successfully making it into CSE. 

  1. Click the gear icon, and select Log Mappings under Incoming Data.
    log-mappings-link.png
  2. On the Log Mappings page search for "Azure" and check under Record Volume.
    azure-activity-log-record-volume.png
  3. For a more granular look at the incoming records, you can also use CIP to search for Azure security records.
    azure-activity-log-search.png