---
source_url: "https://docs.secureauth.com/iam/capability-identity-provider-flexibility?utm_source=openai"
title: "Identity provider flexibility | SecureAuth Connect Product Docs"
mirrored_at: 2026-08-06T01:10:46.680Z
host: docs.secureauth.com
cited_in_42a: true
mirror_canonical: "https://index.42a.ai/docs.secureauth.com/iam/capability-identity-provider-flexibility__q__utm_source_openai"
---

> **Original source:** https://docs.secureauth.com/iam/capability-identity-provider-flexibility?utm_source=openai

Avoid vendor lock-in by connecting with multiple identity providers simultaneously: Active Directory, Entra ID, Okta, or any standards-compliant provider. SecureAuth integrates with a wide range of IdPs to enable unified access for workforce, customers, and partners in hybrid or multi-cloud environments.

> **Why it matters**  
> Organizations often operate multiple IdPs due to acquisitions, partner access, or phased migrations. Flexibility prevents disruption and lock-in.

## Key capabilities[​](#key-capabilities "Direct link to Key capabilities")

-   **Multiple IdP support** – Connect SecureAuth with AD, Azure AD, Okta, or other IdPs
-   **Federated access** – Enable seamless access across enterprise and partner systems
-   **Custom attributes** – Enrich tokens and sessions with additional user data
-   **Centralized governance** – Apply consistent policies and logging across all IdPs

## Outcomes[​](#outcomes "Direct link to Outcomes")

Organizations that use identity provider flexibility achieve:

-   **Freedom from lock-in** by integrating multiple IdPs simultaneously
-   **Unified policies** that govern access across federated environments
-   **Faster onboarding** for partners, customers, and acquired organizations

## Design principles[​](#design-principles "Direct link to Design principles")

-   Support **protocol standards** (SAML, OIDC, LDAP) for broad compatibility
-   Apply **consistent security policies** regardless of source IdP
-   Use **attribute enrichment** to deliver needed claims to applications
-   Ensure **audit logging** across all identity flows for compliance

## Where to configure[​](#where-to-configure "Direct link to Where to configure")

-   [Identity provider integration](https://docs.secureauth.com/iam/integrate-identity-providers)

## Compliance note[​](#compliance-note "Direct link to Compliance note")

Identity provider flexibility supports federation standards and compliance frameworks by ensuring traceability and consistent access controls across providers.

* * *

## FAQ[​](#faq "Direct link to FAQ")

Which identity providers are supported?

SecureAuth supports Active Directory, Azure AD, Okta, and any IdP using SAML, OIDC, or LDAP.

Can policies differ by IdP?

Yes. SecureAuth lets you define policies and rules per IdP while still applying centralized governance.

How does this help in M&A scenarios?

**M&A** stands for _mergers and acquisitions_. When companies combine, each usually has its own identity provider (such as Active Directory, Okta, or Azure AD). SecureAuth allows you to integrate multiple IdPs from acquired or merged organizations without forcing an immediate migration. This reduces disruption, maintains secure access, and gives you time to plan a gradual consolidation if desired.

Is attribute mapping customizable?

Yes. You can enrich tokens and sessions with additional user attributes to meet app requirements.

-   [Hybrid IT support](https://docs.secureauth.com/iam/capability-hybrid-it-support)
-   [Risk-based access control](https://docs.secureauth.com/iam/capability-risk-based-access-control)
-   [Smart access policies](https://docs.secureauth.com/iam/capability-smart-access-policies)