Microsoft 365

Install Integration

Configure Microsoft 365 Logging

By deploying this integration, you can forward Unified Audit Logging logs from Microsoft 365 to Logit.io using the Microsoft 365 Management API. This approach currently supports several Microsoft 365 content types, including:

• "Audit.AzureActiveDirectory"
• "Audit.Exchange"
• "Audit.SharePoint"
• "Audit.General"
• "DLP.All"

To utilize this integration, you'll need an active Microsoft 365 subscription with an administrator account that has the appropriate provisioning.

Additionally, Unified Audit Logging (opens in a new tab) must be enabled within Microsoft 365's Security and Audit Center.

Register a new application in Azure AD

• Sign in to the portal.zure.com and navigate to the Azure Active Directory service.
• Select "App registrations" and click "New registration."
• Enter a name for the application and select the appropriate account type and redirect URI.

Create a client secret for your application

• Select "App registrations" and click on the application that we created in step 2.
• Go to the "Certificates & secrets" page and click "New client secret."
• Enter a description for the client secret and choose an expiration option.
• Click "Add" to create the client secret and copy the value as it will not be displayed again.
• Store the client secret value securely, as it cannot be retrieved later.
• Go to the "API permissions" on the left hand side and click "Add a permission."
• On the "Application permissions" tab, activate the "ActivityFeed.Read" and "ActivityFeed.ReadDlp" permissions.

Install Filebeat

cd 'C:\Program Files\filebeat'

.\install-service-filebeat.ps1

PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-filebeat.ps1

.\install-service-filebeat.ps1

PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-filebeat.ps1

Configure Filebeat

Copy the configuration file below and overwrite the contents of the Filebeat module file typically located at /etc/filebeat/modules.d/o365.yml.disabled

Save the file as o365.yml.

# Module: o365
# Docs: https://www.elastic.co/guide/en/beats/filebeat/8.6/filebeat-module-o365.html
 
- module: o365
  audit:
    enabled: true
 
    # Set the application_id (also known as client ID):
    var.application_id: <ApplicationID>
 
    # Configure the tenants to monitor:
    # Use the tenant ID (also known as directory ID) and the domain name.
    # var.tenants:
    #  - id: "tenant_id_1"
    #    name: "mydomain.onmicrosoft.com"
    #  - id: "tenant_id_2"
    #    name: "mycompany.com"
    var.tenants:
    - id: <TenantID>
      name: <TenantName>
 
    # List of content-types to fetch. By default all known content-types
    # are retrieved:
    # var.content_type:
    #  - "Audit.AzureActiveDirectory"
    #  - "Audit.Exchange"
    #  - "Audit.SharePoint"
    #  - "Audit.General"
    #  - "DLP.All"
 
    # Use the following settings to enable certificate-based authentication:
    # var.certificate: "/path/to/certificate.pem"
    # var.key: "/path/to/private_key.pem"
    # var.key_passphrase: "myPrivateKeyPassword"
 
    # Client-secret based authentication:
    # Comment the following line if using certificate authentication.
    var.client_secret: "<ClientSecret>"
 
    # Advanced settings, use with care:
    # var.api:
    #   # Settings for custom endpoints:
    #   authentication_endpoint: "https://login.microsoftonline.us/"
    #   resource: "https://manage.office365.us"
    #
    #   max_retention: 168h
    #   max_requests_per_minute: 2000
    #   poll_interval: 3m

Copy the configuration file below and overwrite the contents of the Filebeat configuration Inputs section, the file is typically located at /etc/filebeat/filebeat.yml

# ============================== Filebeat inputs ===============================
filebeat.config:
  modules:
    enabled: true            
    path: modules.d/*.yml
 
  fields:
      type: o365
  fields_under_root: true
 
# ================================== Outputs ===================================
output.logstash:
    hosts: ["@logstash.host:@logstash.sslPort"]
    loadbalance: true
    ssl.enabled: true

It's a good idea to run the configuration file through a YAML validator to rule out indentation errors, clean up extra characters, and check if your YAML file is valid. Yamllint.com (opens in a new tab) is a great choice.

Validate configuration

.\@beatname.exe test config -c @beatname.yml

Launch Logit.io to view your logs

Data should now have been sent to your Stack.

If you don't see take a look at How to diagnose no data in Stack below for how to diagnose common issues.

How to diagnose no data in Stack

If you don't see data appearing in your stack after following this integration, take a look at the troubleshooting guide for steps to diagnose and resolve the problem or contact our support team and we'll be happy to assist.