Set up Microsoft Sentinel (In Preview)

Note

General availability is planned for Q1 2027

Microsoft Edge for Business integrates with Microsoft Sentinel to bring browser security events into your security operations workflow. Security teams can use these events alongside other data in Sentinel to investigate activity and understand what happened in the browser.

This article describes the connector's purpose, configuration flow, and checks to perform before you use it in your organization.

Before you begin

You need:

  • A Microsoft Sentinel environment and a Log Analytics workspace for the connector's data.
  • Permissions to configure the connector and its destination workspace in Microsoft Sentinel.
  • The Microsoft Edge Administrator role to configure Microsoft Edge reporting.

Configure the connection

Configure the integration through the Microsoft Sentinel connector experience. The connection associates your organization's Microsoft Edge reporting with the destination workspace.

Start in the Microsoft Defender portal. If your Sentinel workspace isn't connected to the portal, see Connect Microsoft Sentinel to the Microsoft Defender portal. For connector-specific setup instructions, see Resources for creating Microsoft Sentinel custom connectors.

The connector reports the event types supported by the integration. A browser event listed for another Edge reporting connector is not necessarily supported by the Sentinel connector.

Note

The initial configuration is tenant-wide. Do not use this connector to target individual users or groups.

Reference from Microsoft Defender portal:

Microsoft Defender Portal Sentinel

Verify that events are received

After configuration, use a test work profile and an activity that generates a supported event.

  1. Record when the test activity occurs.
  2. Open the connector's destination workspace.
  3. Check for the corresponding Edge event, including its timestamp and identifying information.
  4. Confirm that the event belongs to your test activity before expanding use.

A saved configuration or a displayed connection status does not by itself confirm that events are reaching the workspace.

Troubleshoot missing events

If you don't see the expected event, check that the correct tenant and workspace are connected, the test profile meets the reporting requirements, and the test activity is a supported event. Also check the permissions used to establish the connection.

Keep the test time, browser version, tenant, and destination workspace available when you contact your support team. Do not include sensitive page content in troubleshooting material unless your organization's process permits it.

See also