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
-
Admin
Manager open
/connectors/entraid, connect and remove tenants, rotate secrets, runSync now, edit the segregation-of-duties patterns, start access reviews, assign reviewers and decide on discovered SaaS. Accepting a SaaS proposal also needs the right to create a record in that register (vendors, the DORA register or the AI inventory); without it onlyDismissis offered. -
Contributor cannot open
the connector page; the link sends them away. A Contributor can be assigned
as an access-review reviewer, and then sees and works on that review under
/connectors/entraid/access-reviews. - Viewer has no access. Reviewers are chosen from Contributors and above, so a Viewer is never assigned one.
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
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:
-
No connection yet — the form
Connect a Microsoft Entra tenantfills the page, with the fieldsDisplay name (optional),Tenant ID,Application (client) IDandClient secret, and the buttonVerify & save. -
One or more connections — one card per tenant. The card shows the display
name (or
Untitled tenant), the tenant and client IDs, and a status dot. On the right areSync now,Rotate secretandRemove. Below them are theSegregation of dutiespattern lists and the sectionEvidence from this connection. Under the last card,Add another tenantopens the connect form again.
| 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:
-
Open
/connectors/entraid. With no connection yet, the connect form is already showing; otherwise selectAdd another tenantunder the existing cards. -
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. -
Paste the
Tenant IDand theApplication (client) ID(both look like00000000-0000-0000-0000-000000000000). - Paste the client secret Value, not the Secret ID. The help text under the field reminds you of this.
-
Select
Verify & save. Aegis asks Microsoft for a token with these credentials first. If Microsoft accepts them, the messageTenant verified and savedappears and the form gives way to the new card with the statusNot 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
-
On the connection card, select
Sync now. The button changes toSyncing…and the messageSync startedappears. -
Wait on the page. Aegis checks the connection every few seconds and, when
the sync ends, shows
Sync finished.orSync failed. See the error on the connection.If it is still running after about ten minutes, Aegis tells you to reload the page later. -
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, readingAccess snapshot offollowed by the date and time. - 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
-
On the connection card, select
Rotate secret. A small form opens under the card with the fieldNew client secret. - Paste the new secret Value. A value shorter than eight characters is refused straight away, because it is almost always the Secret ID.
-
Select
Verify & rotate. The new secret is tested against Microsoft before it replaces the old one; on success the messageClient secret rotatedappears.Cancelcloses 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.
- 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.
- 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.
-
Select
Save patterns. The messageSoD patterns saved; the next sync uses themappears. 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
-
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. -
Confirm. The card disappears and the message
Connection removed; historic snapshots preservedappears.
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
-
Select
User access reviewson the connector page. The page lists the reviews in a table with the columnsPeriod,Connection,Status(OpenorSigned off),Progress(kept, removed and pending counts),ReviewersandSigned off. -
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 selectStart 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 seeNo successful sync to review yet. - 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
-
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 removeandPending. -
As a manager, assign reviewers in the
Reviewerssection (Contributor role or higher) and selectSave reviewers. Only assigned reviewers can record decisions. -
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. -
Tick accounts, or the header box to tick every account shown. A bar appears
with the number selected,
Keep selected, a reason field andRemove selected. A removal needs a reason. -
Check the
DecisionandFollow-upcolumns. Each decision shows who made it and when. A removal showsAwaiting ITuntil a sync sees the account disabled or gone, thenConfirmed by sync onand the date. -
When nothing is pending, select
Sign off reviewand confirm. Until then the button is held back with a count of the accounts still needing a decision.
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.
-
Select
Discovered SaaSon 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. -
Each card lists its proposals by kind, with a state:
Proposed,Accepted,DismissedorAlready registered(a matching record exists;Open recordtakes you to it). -
To accept, select
Add as vendor,Add to DORA registerorAdd to AI inventory. The record is created, the messageRecord createdappears and the proposal showsAcceptedwith anOpen recordlink. -
To reject, select
Dismiss, optionally type a reason and selectConfirm 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
- Control monitors. Aegis keeps monitors on your privileged-access controls (permanent Global Administrators and stale admins) and on your leaver controls. Both also grade sync health, so stale data never reads as healthy. See Control monitoring.
- Leavers. When HR records exist, each sync looks for people recorded as having left whose Entra account is still enabled. Without HR data the check is reported as unknown, not as zero.
-
Change alerts. From the second successful sync onwards, Aegis compares each
snapshot with the previous one. A newly assigned built-in admin role, a
Conditional Access policy that was switched off, or a rise in permanent
Global Administrators each becomes an
action item and is offered to your
auto-incident rules under the source
entraid; your rules decide whether an incident opens. - CMDB. When the CMDB module is on, devices are imported as machines and enterprise apps as software. See CMDB.
- Entra groups as targets. Policy required readers and training assignments can target everyone in an Entra group, expanded from the latest snapshot. Policy acknowledgement and training pages can also measure coverage against the active member accounts in the directory. See Policies and Security awareness.
Tips and limits
- A failed sync produces no evidence: an outage is not proof of a control.
- If users, groups or role assignments cannot be read, the whole sync fails. Conditional Access, sign-in activity, devices, applications and group membership are optional: a failure there marks the snapshot partial and the rest still counts.
- Without Entra ID P1 or P2, sign-in activity is skipped, so the stale-admin check reads as unknown rather than zero.
- This connector is separate from Entra ID single sign-on, which needs no Graph permissions of its own.
-
The client secret never leaves the server once saved. When it expires, the
connection shows the error; enter a new secret with
Rotate secret. - A new pattern list or a new secret applies from the next sync; earlier snapshots stay as they were recorded.
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.