Microsoft Office 365 Input
  • 09 Aug 2022
  • 2 Minutes to read
  • Dark
    Light

Microsoft Office 365 Input

  • Dark
    Light

Microsoft Office 365 is a widely used cloud-based suite of productivity tools that allows you to pull your organization’s Office 365 logs into Graylog for processing, monitoring, and alarming.

Note

This is a Graylog Operations Integrations feature and is only available since Graylog version 3.3.3. A valid Graylog Operations license is required.

Required Office 365 Setup

Prerequisites

To use the Office 365 plugin, create and authorize a Client Application through your organization’s Microsoft Azure portal.

A working Office 365 subscription with access to audit logs and access to the Microsoft Azure portal for your organization are required. E5/A5 accounts typically have the required access. 

The following steps are mandatory:

Azure Configuration

  1. Log in to Microsoft Azure.

  2. Select Azure Active Directory from the left-hand menu.

  3. Select App Registrations under the Manage heading from the left-hand menu.

  4. Select New Registration from the top of the right-hand pane.

  5. Register a new application.

    1. Provide a name for the application (e.g, “Graylog Log Access”).
    2. Select the appropriate account type. This should be either Single Tenant or Multitenant depending on whether your organization has a single or multiple Active Directory instance.
    3. Do not add a Redirect URI.
    4. Click the Register button.
  6. Once the application is created, the following fields are needed to set up the O365 plugin:

    1. Application (client) ID
    2. Directory (tenant) ID
  7. For the newly created application, navigate to Certificates & Secrets.

  8. Click on  New Client Secret.

  9. Add a description for the new secret, select an expiration time, and then click Add.

  10. Make a note of the generated value; you will need it to set up the O365 Plugin.

Client Application Permissions in O365

  1. For the newly created application, navigate to API permissions.
  2. Click on Add a permission.
  3. Select Office 365 Management APIs.
  4. Select Application Permissions.
  5. Select all available permissions on the list and click Add permissions.
  6. Click on Grant admin consent for... Click Yes in the pop-up dialog to confirm.

Enable Unified Audit Logging

Navigate to the Audit Log Search page in Microsoft Office 365, and enable Unified Audit Logging. Up to 24 hours may be needed for logs to enter Graylog the first time Unified Audit Log is enabled.

Plugin Configuration

Note

You will need the Client ID, Tenant ID, and Client Secret from the previous sections to proceed.

  • Input Name

    • Provide a unique name for your new O365 Input.
  • Directory (tenant) ID

    • The ID of the Active Directory instance for which Graylog will collect log data.
  • Application (client) ID

    • The ID of the Client Application created above.
  • Client Secret

    • This is the client secret generated above.
  • Subscription Type

    • Indicates what type of Office 365 subscription you have.
    • Enterprise and GCC government plans are the most common values.

O365 Content Subscription

  • Log Types To Collect

    • Determines which of the five available log types the input will pull from Office 365. Log type options are: AZURE_ACTIVE_DIRECTORY, SHAREPOINT, EXCHANGE, GENERAL, DLP_ALL).
  • Polling Interval

    • Determines how often (in minutes) the Input will check for new log data.
    • Value cannot be less than 1 (minute).
  • Drop DLP logs containing sensitive data

    • O365 produces a summary log with no sensitive data and a detailed log with sensitive data for each DLP event. When set, this option causes detailed logs to drop and prevent sensitive data from being stored in Graylog. This option is only available since Graylog version 4.0.6.
  • Enable Throttling

    • Enables Graylog to stop reading new data for this input whenever the system falls behind on message processing and needs to catch up.
  • Store Full Message

    • Permits Graylog to store the raw log data in the full_message field for each log message.
    • Selection can result in a significant increase in the amount of data stored.

Was this article helpful?