PAIRING · MEASURED SIDE BY SIDE
Lumos vs Microsoft Entra ID Governance: reach beyond the IdP and IGA
The short answer
On our default weights Microsoft Entra ID Governance scores higher overall, 6.15 against 6.13 out of 10. Lumos scores higher on Unmanaged app discovery, Accounts inside the app and Orchestrates through the existing stack; Entra ID Governance scores higher on Reach into apps without APIs or SCIM, Machine, service and agent accounts and Pricing transparency. They tie on Executes changes itself and Audit evidence. They sit in different layers (Identity governance (IGA) platform and Governance add-on to an identity provider), so many teams run both.
By The Credential Desk · IAM Compared · Published 2026-10-08
Desk research from public vendor pages and documentation read in September 2026, updated 2026-10-13. Editorial assessment; we did not test the products.
How do they score on each criterion?
| Criterion | Weight | Lumos | Entra ID Governance | Higher |
|---|---|---|---|---|
| Unmanaged app discovery | 18% | 6.0 Identity Analytics surfaces shadow IT alongside dormant and over-privileged accounts. | 3.5 Account discovery covers users inside connected apps; discovery of apps outside Entra is not described in the governance docs reviewed. | Lumos |
| Accounts inside the app | 16% | 6.2 Surfaces dormant accounts and revokes local accounts; app-native role mapping is not detailed. | 5.5 Account discovery shows app users that match no Entra ID user; apps without provisioning rely on a CSV export. | Lumos |
| Reach into apps without APIs or SCIM | 14% | 5.0 Revocation described across custom and on-prem apps; handling of apps with no API is not detailed. | 6.5 SCIM, LDAP, SQL, REST, SOAP, PowerShell and ECMA connectors, including on-prem apps; a manual CSV path for the rest. | Entra ID Governance |
| Orchestrates through the existing stack | 14% | 7.0 Works across the IdP, HRIS, SaaS and cloud stack already in place, with 300+ integrations. | 5.0 Requires Entra ID P1 or P2 and fits best when Entra is the identity provider; manual removals can be routed to ServiceNow tickets. | Lumos |
| Executes changes itself | 12% | 8.0 HRIS-triggered joiner, mover and leaver workflows; leavers offboarded with licenses reclaimed. | 8.0 Lifecycle workflows before start, at status change and at departure, plus HR-driven provisioning. | Tie |
| Machine, service and agent accounts | 10% | 6.0 MCP Governance records agent tool calls with the human identity and policy decision; service account coverage is not detailed. | 8.0 Entra Agent ID is generally available, and workload identities are priced and governed in Entra. | Entra ID Governance |
| Audit evidence | 10% | 7.0 Full audit trail of every grant and revocation. | 7.0 Review decisions and assignments are recorded in Entra; no framework-mapped evidence pack described. | Tie |
| Pricing transparency | 6% | 2.0 No published prices. | 9.5 $7.00 per user per month, paid yearly, published, on top of Entra ID P1 or P2. | Entra ID Governance |
| Total | 100% | 6.13 | 6.15 | Entra ID Governance |
What shape is each tool's reach?
- DISC
- Unmanaged app discovery
- 6.0
- INAPP
- Accounts inside the app
- 6.2
- NOAPI
- Reach into apps without APIs or SCIM
- 5.0
- ORCH
- Orchestrates through the existing stack
- 7.0
- EXEC
- Executes changes itself
- 8.0
- NHI
- Machine, service and agent accounts
- 6.0
- EVID
- Audit evidence
- 7.0
- PRICE
- Pricing transparency
- 2.0
Each sector is one criterion. The longer the engraved sector, the higher the editorial score. Sectors are equal width, so the picture shows the shape of a tool's reach, not its weighted total.
- DISC
- Unmanaged app discovery
- 3.5
- INAPP
- Accounts inside the app
- 5.5
- NOAPI
- Reach into apps without APIs or SCIM
- 6.5
- ORCH
- Orchestrates through the existing stack
- 5.0
- EXEC
- Executes changes itself
- 8.0
- NHI
- Machine, service and agent accounts
- 8.0
- EVID
- Audit evidence
- 7.0
- PRICE
- Pricing transparency
- 9.5
Each sector is one criterion. The longer the engraved sector, the higher the editorial score. Sectors are equal width, so the picture shows the shape of a tool's reach, not its weighted total.
Which parts of the estate does each document?
| Zone | Lumos | Entra ID Governance |
|---|---|---|
| Unsanctioned SaaS | Partial Shadow IT surfaced in Identity Analytics | Not documented Discovery of apps outside Entra not described in the governance docs reviewed |
| On-prem and legacy apps | Partial Revocation across on-prem systems | Documented ECMA connector host, LDAP and SQL for on-prem apps |
| Custom-built apps | Partial Revocation across custom apps | Partial REST, SOAP and PowerShell connectors; CSV path otherwise |
| Local accounts in apps | Partial Revocation across local accounts; dormant accounts surfaced | Partial Account discovery shows app users not matched to Entra users |
| Service accounts and hardcoded credentials | Not documented Not described on the pages reviewed | Partial Workload identities priced and governed in Entra; hardcoded credentials in apps not described |
| AI agents | Partial MCP Governance for agent tool calls | Documented Entra Agent ID generally available |
What do they cost?
Microsoft Entra ID Governance
Pricing
$7.00 per user per month, paid yearly. Requires Microsoft Entra ID P1 ($7.00) or P2 ($10.00). Microsoft Entra Suite $12.00 per user per month. Workload ID $3.00 per workload identity per month.
Source: Microsoft Entra pricing · Read 27 Sep 2026
Deployment
Microsoft cloud service, with an on-prem connector host for provisioning.
Which should you choose?
Choose Lumos if
- you want to keep your current IdP, IGA and ticketing tools and feed them
- you need to see local, orphaned and dormant accounts inside each app
Choose Entra ID Governance if
- you need a published price before talking to sales
- service accounts, workload identities and AI agents are in scope
Frequently asked questions
Which scores higher overall, Lumos or Microsoft Entra ID Governance?
On our default weights Microsoft Entra ID Governance scores higher overall, 6.15 against 6.13 out of 10.
Where does Lumos score higher than Microsoft Entra ID Governance?
Lumos scores higher on Unmanaged app discovery (6.0 against 3.5), Accounts inside the app (6.2 against 5.5) and Orchestrates through the existing stack (7.0 against 5.0).
Can Lumos and Microsoft Entra ID Governance be used together?
It depends on your identity provider. Entra ID Governance requires Entra ID P1 or P2; the other platform can govern apps alongside Entra.