Skip to content

Microsoft Entra ID

Identity & SaaS audit logs. Sign-in and directory-audit events from Microsoft Entra ID (formerly Azure AD).

Status: available on request - self-serve connect is not live yet

The collector and detections for this source are built and run in our lab, but switching it on from the console is not live yet, so connecting it there will not start collection. Ask for it through Integrate -> Request an integration, or email support@sheersafe.com, and we enable it on your dedicated instance. The steps below are accurate, so a credential you create now is the one it will use.

Not the same source as Azure

Entra ID covers identity: sign-ins and directory audits. Azure is a separate source covering the cloud control plane (Defender for Cloud and the Azure Activity Log). Connecting one does not give you the other.

What SheerSight reads

SheerSight reads two Entra audit feeds through Microsoft Graph:

  • Sign-ins (risky sign-ins, legacy-auth protocols, failed-sign-in bursts, password spray, impossible travel), and
  • Directory audits (privileged role grants, application credentials added, authentication methods weakened, conditional-access policy changes).

That feed powers detections such as a risky sign-in, legacy-auth sign-in, privileged role grant, app credential added, authentication method weakened, conditional-access change, a failed sign-in burst, impossible travel, and password spray.

It is read-only.

What you'll need

  • A Microsoft Entra administrator who can register an app and grant admin consent.
  • Your dedicated instance enrolled.

Create the read-only credential

You register an application with two read-only Microsoft Graph permissions.

  1. In the Microsoft Entra admin center (entra.microsoft.com), go to Identity -> Applications -> App registrations -> New registration. Name it something like sheersight-entra, choose single-tenant, and register.
  2. Open API permissions -> Add a permission -> Microsoft Graph -> Application permissions, and add both:
    • AuditLog.Read.All (sign-in and directory-audit logs), and
    • Directory.Read.All (the directory objects those records reference).
  3. Click Grant admin consent for . Application permissions do nothing until an admin consents.
  4. Go to Certificates & secrets -> New client secret, add one, and copy the secret value immediately (it is shown only once).
  5. From the app's Overview, copy the Directory (tenant) ID and the Application (client) ID.

Reusing the Azure app registration

If you are also connecting Azure, you can add these two Graph permissions to the same app registration instead of creating a second one. The Azure subscription role and these Graph permissions can live on one app.

Connect it in SheerSight

Self-serve connect is not live for Entra ID yet. Open Integrate -> Request an integration, choose Microsoft Entra ID, and say your credential is ready. We enable the source on your dedicated instance and arrange the handover of the Tenant ID, Client ID, and Client secret through the same browser-side encryption used for every live source, so the secret is never sent in the clear and we never see it.

Verify

  1. The source is enabled on your dedicated instance.
  2. Sign-in and directory-audit events begin appearing, and matching detections start firing.

Troubleshooting

  • No data. Confirm admin consent was granted for both Graph permissions (a common miss), and that the client secret has not expired.
  • Only some events. AuditLog.Read.All covers both sign-ins and directory audits; Directory.Read.All supplies the referenced directory objects. Both are needed.

What SheerSight can and cannot do

The permissions are read-only Graph audit and directory reads. SheerSight cannot change users, roles, policies, or authentication methods, and it cannot sign anyone in or out. It only reads the audit feeds.