Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,25 @@ Microsoft Entra ID (formerly Azure AD) secures identities and access, enhanced b
3. Sign in with a Microsoft Entra ID administrator account and consent to the requested permissions.
4. Click **Allow** to authorize the connection.

## Configuration Options

When creating or editing a Microsoft Entra ID instance, admins can control what the connector
collects:

- **Data collection scope:** Choose **Users**, **Apps**, or both. Selecting only Users skips
enterprise application discovery for that instance; selecting only Apps skips directory user
collection. Both scopes are selected by default, and at least one scope must always remain
selected.
- **Sync app status details:** An opt-in switch available when **Apps** is selected. When on,
each sync refreshes application approval status and criticality from Microsoft Entra ID. When
off (the default), previously set approval status and criticality values are preserved between
syncs.
- **Configure user condition:** When the instance's forwarding scope is not set to send all audit
events, an additional filter section lets admins add attribute-based conditions that scope which
users are collected. This section is specific to Microsoft Entra ID and is not shown for other
Microsoft-ecosystem integrations (Azure Cloud, Microsoft Intune, Microsoft Calendar, Microsoft
Purview) that share the same underlying connection.

## Required Scopes

| Scope Group | Permissions | Purpose |
Expand Down
19 changes: 19 additions & 0 deletions docs/release-notes/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,25 @@ hide_copy_dropdown: true

# Release Notes

## July 23, 2026

### New

- [Integrations](/platform-areas/integrations/identity-providers/microsoft-entra-id): Added a
**Data collection scope** selector to the Microsoft Entra ID integration setup. Admins can
choose to collect **Users**, **Apps**, or both for each instance, and can opt in to a **Sync app
status details** switch that refreshes application approval status and criticality on every
sync. When left off, previously set approval status and criticality values are preserved between
syncs.

### Fixed

- [Integrations](/platform-areas/integrations/identity-providers/microsoft-entra-id): The
**Configure user condition** filter section no longer appears for Microsoft-ecosystem
integrations that share Microsoft Entra ID's connection configuration, such as Azure Cloud,
Microsoft Intune, Microsoft Calendar, and Microsoft Purview. It now correctly shows only for
Microsoft Entra ID.

## July 16, 2026

### New
Expand Down