Topic starter
17/05/2026 9:44 am
TL;DR: Omada Identity announced Omada Identity Cloud Private, which runs the full Omada Identity Cloud platform inside a customer’s own Microsoft Azure tenant while keeping the same release cadence as SaaS, according to Omada Identity. For regulated teams, deployment model is now part of identity governance design, not just an infrastructure preference.
Editorial analysis by NHI Mgmt Group, based on content published by Omada Identity: “Omada Launches Omada Identity Cloud Private for Regulated Enterprises and Government Organizations”.
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 control gaps can appear in customer-operated cloud IGA?
A: The main gap is ambiguity between application ownership and environment ownership.
Practitioner guidance
- Define the tenancy control boundary Document which party operates the Azure environment, which party owns the IGA application layer, and how evidence is produced for audits and risk reviews.
- Map residency requirements to deployment choices Validate whether the selected Azure region and tenant ownership model satisfy the organisation’s regulatory data residency and operational oversight obligations.
- Separate release management from environment management Write down who handles application releases, deployment guidance, support, patching, and tenant-level configuration so accountability does not blur in operations.
Bottom line: The core issue is not cloud versus on-premises, but whether the IGA deployment model preserves the control boundary regulated teams must defend.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
17/05/2026 9:44 am
Deployment model has become an identity governance control surface: The boundary between SaaS and customer-operated cloud tenancy now carries governance weight, not just infrastructure meaning. When regulated teams must prove where identity data resides and who can operate the environment, the hosting model becomes part of the assurance story. Practitioners should treat tenancy choice as a control decision that shapes auditability and accountability.
A question worth separating out:
Q: What should teams document before moving IGA into a regulated cloud tenant?
A: Teams should document the tenant boundary, regional data location, release ownership, support responsibilities, and the evidence required for audits. That record helps prove that cloud delivery still meets the organisation’s governance model and does not weaken regulatory accountability.
👉 Read our full editorial: Omada Identity Cloud Private reframes regulated IGA deployment