How it works

From invisible drift to a directory you can prove

The story of every Entra ID tenant, and where VisualizerEngine changes it. The product itself takes three steps: consent, sync, see.

The story

The drift

The directory grows a shape nobody designed

Every Entra ID tenant grows the same way: groups get nested inside groups, licenses get assigned to groups, people inherit access through chains nobody remembers building. Circular references, abandoned groups, and runaway depth accumulate silently, because nothing in the native tooling flags them.

The question

Then a ticket arrives

"Why does this user have an E5 license?" The Azure portal shows flat lists, so the answer lives in PowerShell scripts, exported CSVs, and institutional memory. When someone asks "what happens if I move this group?", the honest answer is that you find out who lost access when the next tickets arrive.

Day one · Step 1

Consent

A global admin opens a standard Entra admin-consent link and grants exactly three Microsoft Graph permissions, all read-only. No agents, nothing installed, nothing modified. This is everything the platform will ever ask for:

Microsoft Graph permissions requested by VisualizerEngine
PermissionUsed for
Group.Read.AllGroups, nesting, memberships, and group license assignments
User.Read.AllUsers and their license assignments
Organization.Read.AllTenant-level subscription and SKU information

Day one · Step 2

Sync

VisualizerEngine crawls the directory once and builds a per-tenant mirror. From then on, Microsoft Graph delta queries keep it current on a per-tenant schedule, including correct handling of deletions. Everything you explore runs against the mirror at interactive speed, never against your live directory.

Day one · Step 3

See

The full nesting map is live in your browser. Circular references surface, every license shows the exact path it travelled through nested groups, and depth violations rank against the thresholds you set. Users sign in with Entra ID single sign-on, and Viewer, Analyst, Admin, and Auditor roles are enforced server-side.

Nesting analysis on day one. Product interface preview.

The new normal

The directory stops surprising you

Changes are simulated before they happen, with the full blast radius visible. Policies score compliance as a trend you watch. Snapshots prove exactly what changed between any two points in time. Alerts arrive when the structure moves. The directory stops changing behind your back.

What-if simulationPolicy engineSnapshots and diffsChange awareness

See your directory's real shape

VisualizerEngine is pre-launch. Onboarding is a read-only admin-consent link: no agents, nothing installed, nothing modified.