Single Sign-On with SAML2 & Azure AD / Entra ID
Every standalone login is access your identity team can't see
Every standalone login is an account your identity team can't see. When a compliance platform keeps its own usernames and passwords, joiners and leavers fall out of sync with the corporate directory, and offboarding leaves orphaned access that surfaces in the next access review.
Auditors expect access to your privacy and InfoSec tooling to follow the same identity policy as everything else: central provisioning, enforced MFA, and a clean logout. A tool that can't speak SAML2 or connect to Entra ID becomes the exception you have to explain — and exceptions are findings.
What you can do with enterprise SSO
- Sign in through your corporate IdP via SAML2 or Azure Entra ID.
- Configure the service provider with the OneLogin builder — ACS endpoints and SP metadata.
- Connect Azure AD / Entra ID using tenant-specific authorize and token URLs.
- Set the IdP entity ID, SSO URL and SLO URL so single logout works end to end.
- Upload your X.509 certificate to verify signed SAML assertions.
- Choose the SSO type per company — SAML2 or OAuth2 — with an Entra ID enable flag.
What it delivers to your program
- No separate credentials to govern — access follows your directory, so joiners and leavers stay in sync.
- MFA and conditional access apply automatically — your IdP's policy now covers the compliance platform too.
- Single logout closes the session everywhere — no lingering authenticated tab after offboarding.
- Cleaner access reviews — one identity source to evidence, fewer exceptions to explain to auditors.
- A fallback that keeps you working — local Passport authentication stays available if the IdP is unreachable.
Built for compliance
Supports the access-control evidence SOC 2 reviewers look for, and helps you demonstrate that compliance tooling sits inside your standard identity governance.
| What DPMS does | Maps to | How |
|---|---|---|
| Federates login to your enterprise IdP | ISO 27001:2022 Annex A 5.16 | Identity management via SAML2 / Entra ID, no local accounts to provision |
| Verifies signed assertions | ISO 27001:2022 Annex A 5.17 | X.509 certificate upload validates SAML assertion signatures |
| Standards-based federation | SAML2 | SP configured with the OneLogin toolkit — entity ID, ACS, metadata |
| Terminates sessions on logout | ISO 27001:2022 Annex A 8.5 | SLO (single logout) URL propagates logout to the IdP |
Why Priverion
Unlike general-purpose GRC tools that bolt federation on as an afterthought, DPMS handles single logout and X.509-signed assertions natively. SAML2 and Azure Entra ID OAuth2 are both driven from a single configurable IAM settings document, with the SSO type chosen per company — so a multi-entity group can run different identity setups under one platform. The result is privacy and InfoSec tooling governed by the same identity controls as the rest of your estate.
Questions CISOs ask before a demo
Does DPMS support SAML2 and Azure Entra ID?
What do I configure on my side?
Does it handle single logout?
What if our IdP is unavailable?
Explore related capabilities
Ready to put DPMS behind your IdP?
