Allowed for multiple SSO providers
Distributed Cloud customers often have multiple directories that they would like to link to a single tenant.
For example, a customer may have one AAD environment for Dev, and another for Prod. Or some may have PCI, and non-PCI.
-
Glen Willms
- Apr 10 2023
Related ideas
@scott beatty
In our case, which I assume is fairly common.
We have a locked down Prod tenant. We have a more loosely managed Dev tenant. Two different azure tenants. For compliance reasons we restrict access from the PRod tenant but for development reasons we kep dev tenant more open.
In an enterprise it seems weird to do this. You typically have 1 AD forest and use groups or OUs to manage that function. But as a service provider you have SOC, PCI, and other compliance that might drive you to keep your users out of the tenant.
@glen can you share any more info about the customer? I guess I don't really understand why a customer would choose to have muiltiple SSO providers. Even if some were PCI and others not I would think it would be easier to push everyone onto one system.