Topic starter
15/05/2026 7:33 pm
TL;DR: The Cloud Private option places the full Omada Identity Cloud platform inside a customer-owned Microsoft Azure tenant, according to Omada Identity, giving regulated organisations a deployment model that preserves tenant boundaries and keeps identity data in a chosen environment while retaining the SaaS release cadence. The governance shift is that cloud velocity no longer has to require shared-tenant compromise.
Editorial analysis by NHI Mgmt Group, based on content published by Omada Identity: “Omada stellt „Omada Identity Cloud Private“ für regulierte Unternehmen und Behörden vor”.
Key questions
Q: How should regulated teams evaluate cloud IGA when tenant control matters?
A: They should assess whether the deployment model preserves residency, operator accountability, and audit evidence, not just feature coverage.
Q: Why does tenant ownership matter for identity governance platforms?
A: Tenant ownership matters because auditors and regulators often care about where identity data resides and who can operate the environment.
Q: What should identity teams check before moving regulated workloads to cloud-private IGA?
A: They should check data residency, administrative ownership, logging retention, and whether the deployment model still supports access review and change evidence.
Practitioner guidance
- Define the tenant boundary as a control boundary Document who owns the Azure tenant, who administers it, and which controls remain under customer authority before any deployment decision is made.
- Map residency requirements to the deployment model Trace DORA, NIS2, FINMA, and internal residency obligations to the specific environment where identity data will be processed and stored.
- Separate release governance from hosting governance Review change management so that SaaS cadence does not blur decisions about where the platform runs or which tenant controls apply.
Bottom line: Cloud-private IGA changes the deployment debate by separating cloud delivery from shared-tenant ownership concerns.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
15/05/2026 7:34 pm
Cloud-private IGA is really a governance architecture choice, not a product feature. The important change is that regulated teams can keep cloud delivery while preserving a tenant boundary they can explain to auditors and supervisors. That matters because many identity programmes fail not on technical capability but on evidenceability, residency, and ownership ambiguity. The practitioner conclusion is simple: deployment model is now a governance decision, not just an infrastructure decision.
A question worth separating out:
Q: What is the difference between private IGA deployment and on-premises identity governance?
A: Private IGA in a customer cloud tenant keeps cloud operating patterns while preserving a controlled boundary, whereas on-premises deployment places the full stack inside customer-managed infrastructure. The practical difference is speed and operations versus maximum local control. Regulated teams should choose based on evidence requirements, not terminology.
👉 Read our full editorial: Cloud-private IGA changes the governance trade-off for regulated identity