Skip to main content
Sumo Logic

Collect Logs for the Azure Active Directory App

This section has instructions for setting up the ingestion pipeline from Azure Active Directory to Sumo Logic.

Solution Overview

  • Azure Monitor collects logs for Azure Active Directory and streams the data to an Azure Event Hub. 
  • Event Hub streams the logs collected by Azure Monitor to an Azure function. 
  • The Azure function is a small piece of code that is triggered by Event Hub to send Azure Active Directory logs to the Sumo HTTP Source. The function also logs to one Storage Account and logs failover data to another.

CollectLogsforAzureAD.png

Prerequisites

Configure an HTTP Source

In this step, you configure an HTTP Source to receive logs from the Azure function.

  1. Select a Hosted Collector where you want to configure the HTTP Source. If desired, create a new Hosted Collector, as described on Configure a Hosted Collector.
  2. Configure an HTTP source, as described on HTTP Logs and Metrics Source

Configure Azure resources using ARM template

In this step, you use a Sumo-provided Azure Resource Manager (ARM) template to create an Event Hub, an Azure function and two Storage Accounts. The Azure function is triggered by Event Hub. Two storage accounts are used to store log messages from the Azure function and failover data from Event Hub.

  1. Download the azuredeploy_logs.json ARM template.
  2. Go to Template deployment in the Azure Portal.after step2.3.png
  3. Click Create.
  4. On the Custom deployment blade, click Build your own template in the editor.
  5. Copy the contents of azuredeploy_logs.json, and paste it into the editor window.after step2.6.png
  6. Click Save.
  7. Now you are back on the Custom deployment blade.
    1. Create a new Resource Group (recommended) or select an existing one.
    2. Choose Location.
    3. In the Sumo Endpoint URL field, enter the URL of the HTTP Source you configured in Step 1.
    4. Agree to the terms and conditions.
    5. Click Purchase.
      pipeline-custom-deployment.png
  8. Verify the deployment was successful by looking at Notifications at the top right corner of Azure Portal.
    go-to-resource-group.png
  9. (Optional) In the same window, you can click Go to resource group to verify all resources have been created successfully. You will see something like this:
    step2.11.png
  10. Go to Storage accounts and search for “sumofailmsg”. Click on “sumofailmsg<random-string>”.
    step2.12.png
  11. Under Blob Service, click Containers, then click + Container, enter the Name azureaudit-failover, and select Private for the Public Access Level. Click OK.
    step2.13.png

Troubleshooting log collection

If logs are not flowing into Sumo Logic, follow the steps in Troubleshooting log collection in the following document.