Skip to content

eric-ooi/elastic-m365

Repository files navigation

Microsoft 365 Dashboards for Elastic Kibana

A collection of custom dashboards to give you a holistc view of your Microsoft 365 environment. These dashboards can help you answer the following questions and more:

  • What files are users sharing internally and externally and with who? Are there users uploading or downloading an unusually large amount of data?
  • Who invited or added a guest user? Were they invited through a shared file or added directly through Active Directory?
  • Where in the world are users logging in from? Are there suspicious user agents attempting to login?
  • Which users receive the most suspicious mail? Where is this mail coming from?
  • What users does Azure AD consider to be risky and why?

Check out our blog for an in-depth walkthrough of these dashboards. Enjoy!

Requirements

Installation

Import Dashboards

First, we'll import the .ndjson file into Kibana.

  1. In Kibana, click on Stack Management in the left navigation menu.
  2. Next, click on Saved Objects in the left menu.
  3. In the top right, click on Import.
  4. In the window that opens, select the Microsoft 365 Dashboards.ndjson file and click Import.

Add Runtime Field

Next, we'll add a custom runtime field called m365-azure.event.id that enables us to correlate Microsoft 365 and Azure logs relating to the same activity.

  1. Still in the Stack Management window, click on Data Views in the left menu.
  2. Click on logs-*.
  3. In the top right, click on Add field.
  4. In the window that opens, set the following:
    • Name: m365-azure.event.id
    • Type: Keyword
    • Enable Set value and copy and paste the m365-azure.event.id source code into the Define script field.
    • Click Save when done.

View Dashboards

  1. Open the Kibana navigation menu again and click on Dashboard.
  2. Search for M365 and click on one of the three newly imported Microsoft 365 dashboards to start using them.

Note: This guide assumes you're already capturing Microsoft 365 and Azure logs into Elasticsearch via Elastic Agent.

If you are collecting logs via Filebeat, you will need to edit each of the panels in the dashboard and replace the logs-* index pattern with filebeat-*.

Releases

No releases published

Packages

No packages published