Skip to content
Microsoft Entra ID coexistence Federated identity governance

Microsoft Entra ID and SafePaaS: what each one governs

SafePaaS does not replace Microsoft Entra ID. It governs what a role permits once the user is inside the ERP — the layer an identity platform cannot see.

Beside Microsoft Entra ID, not instead of it — one rule book across every system in the same business process.

Book a Demo See How It Connects
Role definition read as Microsoft Entra ID defines it, down to the eligible or active Every snapshot re-tested in full, so a conflict reintroduced since the last one surfaces One rule book applied across every system in the process, not one tool per application
The entitlement model we read

A Microsoft Entra ID user’s authority is five layers below the role name

SafePaaS reads the Microsoft Entra ID security model as Entra ID defines it: user and group, role definition, role assignment, administrative unit, eligible or active. Each layer is resolved, not assumed.

Only the deepest layers say what a user can actually do, and where. Everything above them is a container.

Figure 1 How SafePaaS resolves a Microsoft Entra ID user to effective authority
  1. Layer 1 User and group
  2. Layer 2 Role definition what a directory role permits
  3. Layer 3 Role assignment who holds it
  4. Layer 4 Administrative unit the scope it applies in
  5. Layer 5 Eligible or active where Privileged Identity Management is in use

A container in this chain can be widened while keeping the name an access review sees, and the deepest layer differs with every assignment. That is why SafePaaS tests the authority a user actually resolves to, not the label attached to it.

Coverage in detail

Where SafePaaS and Microsoft Entra ID divide the work

What does Microsoft Entra ID already govern?

Microsoft Entra ID owns the account and the process around it, reading its own model to do so: user and group, role definition, role assignment, administrative unit, eligible or active. None of that is in question, and SafePaaS does not replace any of it.

▸ The account itself — joiners, movers and leavers ▸ Birthright access, and the request and approval workflow ▸ Provisioning a user into the downstream system, and recording that they hold a role there ▸ Certification campaigns, run against what it knows

What can Microsoft Entra ID not see once the user is inside the ERP?

What the role PERMITS. Microsoft Entra ID records that a user holds a role; what that role resolves to lives several layers down in the target system’s own security model and does not travel with the assignment.

▸ The entitlement behind the role name, which is where the permission actually lives ▸ A conflict that exists only where two duties share an org unit — so it is a column, not a row ▸ A role whose contents were widened after it was built, while the name an access review sees stayed the same ▸ Configuration and transaction change inside the ERP, which no access model describes at all ▸ Service, batch and integration accounts that no joiner-mover-leaver process was built to review

What does SafePaaS add on top of Microsoft Entra ID?

One rule book, tested against an ERP Snapshot of the target system’s own security model — so a certification reflects the entitlement rather than the role name.

Modules Enterprise Access MonitorEnterprise Roles ManagerMonitorPaaS
▸ Resolves each role to the entitlement it actually grants, in the target system’s own vocabulary ▸ Tests segregation of duties across every system in a business process, not one application at a time ▸ Simulates a role change before it is applied, so a change does not reintroduce a violation that was already remediated ▸ Watches what happened — the posted document, the changed bank detail — not only who could have done it ▸ Extends the same policy to non-human identities and AI agents
Connection

How does SafePaaS connect to Microsoft Entra ID?

SafePaaS extracts through the platform’s own service interfaces — SOAP per security object, REST for transactions.

Inside Microsoft Entra ID → SafePaaS extraction SOAP services per security object returning XML; REST endpoints returning JSON for occurrences.
Transfer → DataProbe The collected data is pushed out to SafePaaS through DataProbe.
Normalize → DataPaaS The transformation layer. Normalizes the data where required so one rule book can test it.
Result ERP Snapshot The point-in-time copy every module tests against — SoD, monitoring, certification and audit evidence alike.
What is read User and group, Role definition, Role assignment, Administrative unit and Eligible or active How data moves Everything collected lands in the FSOD_* open interface tables, and DataPaaS normalizes it from there First snapshot A baseline of every user, role and entitlement assignment, and the first SoD test result set against your own rule book Protection Traffic terminates behind a WAF and an API gateway; the snapshot is tenant-isolated at rest
What runs inside Microsoft Entra ID Nothing Extraction runs through the platform’s own service interfaces, so no SafePaaS component is deployed into it.

Because every governance module tests the snapshot rather than the live system, the same rule book applies to Microsoft Entra ID and to every other system in the same business process.

FAQs

What Microsoft Entra ID teams ask first.

The security model as Entra ID defines it: user and group, role definition, role assignment, administrative unit, eligible or active. SafePaaS resolves the chain rather than recording the role name, because the role name is a container and the permission lives below it.

Nothing inside the application. Extraction runs through its own service interfaces. Everything collected is pushed out to DataProbe, where DataPaaS normalizes it into the snapshot every governance module tests.

Every test runs against a snapshot taken at a point in time, and Enterprise Roles Manager simulates a role change before it is applied. A change that would reintroduce a remediated conflict is visible before it reaches production rather than at the next review.

A baseline of every user, role and entitlement assignment, and the first SoD test result set against your own rule book — typically the first time the estate has been assessed against one rule book rather than several.

No. Your identity platform keeps the account, the joiner-mover-leaver process and the request workflow. SafePaaS governs what the entitlement behind the role actually permits, so a certification reflects the entitlement rather than the role name.

Go deeper on Microsoft governance
Pillar Enhance your IGA Pillar Policy-based access governance across the estate Index All application coverage
Next step

See how SafePaaS governs a Microsoft Entra ID estate

A working walkthrough against a demo environment, with a specialist who can map what you see onto the roles, organisation structure and audit pressure you actually have.

What the walkthrough covers How the entitlement chain is read as Microsoft Entra ID defines it — user and group, role definition, role assignment, administrative unit, eligible or active An SoD conflict traced from the rule to the entitlements that create it How a role change is simulated before it reintroduces a remediated conflict Where SafePaaS sits relative to the IGA and GRC tooling you already run