Microsoft Entra ID

Take read-only snapshots of your Microsoft Entra ID directory and turn them into identity and access evidence, access reviews and SaaS discovery.

Microsoft Entra ID is Microsoft's cloud directory: the list of your people, their groups, the admin roles they hold and the apps they sign in to. This connector reads that directory on a schedule and keeps each reading as a snapshot (a dated, read-only copy of what the directory looked like at that moment). Aegis then checks every snapshot for stale admins, permanent Global Administrators and segregation-of-duties conflicts (one person holding two roles that should be kept apart), and records it as evidence for your identity and access controls. Aegis never writes to your directory: any change it suggests is work for your IT team.

At a glance

Direction Into Aegis. Read-only: Aegis never changes your directory.
What it brings in Users, groups and group membership, directory role assignments, devices, enterprise applications (service principals), Conditional Access policies and sign-in activity.
Where it lands A snapshot per sync on the connection. Each successful snapshot becomes one Evidence item, mapped to the identity and access controls of your frameworks and approved on creation as trusted connector output (a reviewer may still reject it). Snapshots also feed quarterly user access reviews, segregation-of-duties checks, control monitors, change alerts, and the discovered SaaS publishers, which you can accept as vendors, as DORA ICT third-party providers or as AI systems.
Credentials and permissions An app registration with a client secret (application permissions, admin consent). Directory.Read.All covers users, groups, role assignments and devices. Add Policy.Read.All for Conditional Access, Application.Read.All for applications and AuditLog.Read.All for sign-in activity; a missing one skips only that part and the snapshot is marked partial. Sign-in activity also needs an Entra ID P1 or P2 licence on your Microsoft tenant.
Owner of imported records The snapshot evidence belongs to the person who created the connection. A vendor accepted from SaaS discovery belongs to the person who accepted it. The evidence for a signed-off access review belongs to the reviewer who signed it off.
When it runs Every 30 minutes (at :07 and :37), and on demand with Sync now on the connection row. Access reviews are checked daily, so each connection gets one review per calendar quarter.
Set it up /connectors/entraid, by people allowed to configure connectors, on a plan that includes the connector. The credentials are tested against Microsoft before they are saved.

Who uses it

If the connector is not enabled or not licensed for your organisation, every Entra ID page shows a not-found state instead.

What's on this screen

No screenshot in this chapter

The demo organisation used for this guide has no Entra ID tenant connected, so this chapter describes the screens from the product itself rather than from a capture.

The page opens with a breadcrumb back to Connectors, the title Microsoft Entra ID and a short description. Under the description sit two buttons: User access reviews and Discovered SaaS, each opening its own page.

What follows depends on whether a tenant is connected:

Status What it means
Not yet synced Saved, but no sync has finished yet.
Connected The last sync succeeded (in full or in part).
Error The last sync failed. The card shows the error text and when it happened, so you can see which permission or secret is at fault.

Connect a tenant

First, in the Azure portal, register an app in your Entra tenant, give it the application permissions in the table above, grant admin consent and create a client secret. Copy the secret's Value: the portal shows it once. Then in Aegis:

  1. Open /connectors/entraid. With no connection yet, the connect form is already showing; otherwise select Add another tenant under the existing cards.
  2. Optionally type a Display name, for example the name of the tenant. It is the label you will see on the card, in access reviews and in evidence.
  3. Paste the Tenant ID and the Application (client) ID (both look like 00000000-0000-0000-0000-000000000000).
  4. Paste the client secret Value, not the Secret ID. The help text under the field reminds you of this.
  5. Select Verify & save. Aegis asks Microsoft for a token with these credentials first. If Microsoft accepts them, the message Tenant verified and saved appears and the form gives way to the new card with the status Not yet synced. If Microsoft rejects them, nothing is saved and the form shows an error; if Microsoft is briefly unavailable, nothing is saved either and you try again later.

A missing tenant ID, client ID or secret is caught before anything is sent, with a message naming the empty field. When at least one connection exists, the form also has a Cancel button.

Sync now and read the result

  1. On the connection card, select Sync now. The button changes to Syncing… and the message Sync started appears.
  2. Wait on the page. Aegis checks the connection every few seconds and, when the sync ends, shows Sync finished. or Sync failed. See the error on the connection. If it is still running after about ten minutes, Aegis tells you to reload the page later.
  3. Look at Evidence from this connection. It shows the total number of records, the time of the last successful sync, and one line per snapshot, newest first, reading Access snapshot of followed by the date and time.
  4. Each line shows its review status badge and how many controls it is linked to. Select the line to open the evidence record.

Before the first successful sync the section reads No evidence yet. You do not have to press Sync now: the scheduled run picks up a new connection within half an hour.

Rotate the client secret

  1. On the connection card, select Rotate secret. A small form opens under the card with the field New client secret.
  2. Paste the new secret Value. A value shorter than eight characters is refused straight away, because it is almost always the Secret ID.
  3. Select Verify & rotate. The new secret is tested against Microsoft before it replaces the old one; on success the message Client secret rotated appears. Cancel closes the form without changes.

The tenant ID and client ID cannot be changed here: they identify the trust relationship. To point at a different app registration, add a new connection and remove the old one.

Set the segregation-of-duties patterns

Each card has two lists, Developer group patterns and Production access group patterns. A user who is in a group whose name contains a developer pattern and in a group whose name contains a production pattern, directly or through a nested group, counts as a segregation-of-duties violation. A new connection starts with developer, dev-team and engineering on the developer side and prod-admin, production, release-manager and deploy on the production side.

  1. Type one pattern per line in each list. Matching is plain text and ignores capitals. A row pasted from a spreadsheet works too: tabs separate patterns like new lines.
  2. Keep to the rules shown under the lists: 1 to 20 patterns per list, each at most 64 characters. A broken rule shows a red message naming the list and the line.
  3. Select Save patterns. The message SoD patterns saved; the next sync uses them appears. Existing snapshots are not recalculated.

People without the right to configure connectors see the lists read-only and no save button. If the group membership could not be read, or a group was too large to read completely, the snapshot reports the check as skipped, never as zero violations.

Remove a connection

  1. On the connection card, select Remove. A confirmation dialog explains that historic snapshots are kept as compliance evidence and that the connection will stop being counted.
  2. Confirm. The card disappears and the message Connection removed; historic snapshots preserved appears.

Run a user access review

A user access review is a periodic check that every account is still needed. Each quarter Aegis opens one review per connection, built from that connection's latest successful sync, and lists every enabled account in it. Aegis never disables an account itself: a removal opens an action item for IT, and a later sync confirms it.

The review list

  1. Select User access reviews on the connector page. The page lists the reviews in a table with the columns Period, Connection, Status (Open or Signed off), Progress (kept, removed and pending counts), Reviewers and Signed off.
  2. To start this quarter's review ahead of the scheduler, use the panel Start this quarter's review: pick the connection if there is more than one and select Start review. The new review opens. If this quarter's review already exists, Aegis opens that one instead; if the connection has no successful sync yet, you see No successful sync to review yet.
  3. Select a period in the table to open that review.

With no reviews yet, a manager sees No access reviews yet. One starts automatically each quarter. A reviewer with nothing assigned sees You are not assigned to any access review.

Working in a review

  1. Read the summary at the top: the period, the connection, the date of the sync it was built from, whether it was started by schedule or manually, and the counts Accounts, Kept, To remove and Pending.
  2. As a manager, assign reviewers in the Reviewers section (Contributor role or higher) and select Save reviewers. Only assigned reviewers can record decisions.
  3. In Accounts under review, narrow the list with the search box, the account type filter (All accounts, Members, Guests, Admins), the decision filter and the sort (Sort by account, Admins and guests first, Oldest accounts first). Admin and guest accounts carry a badge.
  4. Tick accounts, or the header box to tick every account shown. A bar appears with the number selected, Keep selected, a reason field and Remove selected. A removal needs a reason.
  5. Check the Decision and Follow-up columns. Each decision shows who made it and when. A removal shows Awaiting IT until a sync sees the account disabled or gone, then Confirmed by sync on and the date.
  6. When nothing is pending, select Sign off review and confirm. Until then the button is held back with a count of the accounts still needing a decision.
Four-eyes rules apply

Your own account is marked You and cannot be selected: another reviewer decides on it. Signing off turns the review into one evidence record that is not approved automatically; a different person must approve it in Evidence. After sign-off the summary shows who signed off and when, with a View evidence link.

Review discovered SaaS

Each sync reads the enterprise apps in your tenant and groups them by publisher. Aegis proposes each publisher as a vendor, a DORA ICT third-party provider or an AI system, but registers nothing until a person accepts it.

  1. Select Discovered SaaS on the connector page. A line at the top counts the proposals awaiting review. Below it is one card per publisher, with the number and names of its apps; publishers still awaiting a decision come first, then the rest alphabetically.
  2. Each card lists its proposals by kind, with a state: Proposed, Accepted, Dismissed or Already registered (a matching record exists; Open record takes you to it).
  3. To accept, select Add as vendor, Add to DORA register or Add to AI inventory. The record is created, the message Record created appears and the proposal shows Accepted with an Open record link.
  4. To reject, select Dismiss, optionally type a reason and select Confirm dismissal. The reason stays visible on the proposal.

Before the first successful sync the page reads No SaaS publishers discovered yet. If someone else decided the same proposal a moment earlier, Aegis says so and refreshes the list.

What else a snapshot feeds

Tips and limits

Where this connects

Sync-now and segregation-of-duties patterns are explained in Connectors; single sign-on in Connect Microsoft Entra ID. Snapshot and access-review evidence lands in Evidence; accepted SaaS publishers land in Vendors, DORA and EU AI Act.