How to seamlessly failover from Okta to Microsoft Entra ID

Don’t let Okta take you offline. Use Identity Continuity to allow users to securely authenticate to critical apps with Microsoft Entra ID anytime Okta is unavailable.

Read the docsTry this in Maverics
  • Allow users to automatically log into mission critical apps with Microsoft Entra ID when Okta is offline.
  • Easily configure failover and failback parameters through the Maverics UI.
  • Seamlessly map key attributes between Okta and Microsoft Entra ID with the Schema Abstraction Layer™.

Don’t get caught with your apps down

Recipe details

This is how everything works together.

Diagram showing Maverics Orchestrator connecting to Okta and Microsoft Entra ID via a Schema Abstraction Layer, with cloud IDP failover and the capability for failover from Microsoft Entra ID to on-prem Active Directory (AD).

Setup details

Just add in your ingredients and deploy.

Screenshot of a web application displaying an interface for managing identity services with sections for different identity fabrics, including Okta and CyberArk integrations, a Learning Center for resources, and options to failover from your cloud IDP to a backup cloud IDP.

App users don’t care how they authenticate — they care about accessing apps exactly when they need to. Use Identity Continuity to give key users seamless access to the mission-critical apps that directly impact business function — with automatic failover between Okta and Microsoft Entra ID.

  • Familiar login. Users log in via their Okta portal and follow the typical app authentication access flow.
  • Invisible redirection. Behind the scenes, Maverics’ health check functionality evaluates whether Okta is online and — if it isn’t — directs the user to Microsoft Entra ID.
  • Quick authentication. The user enters their details, gets authenticated and logs in. Everything in the app looks the same as before and access is securely granted.

Key users will need to access a mission-critical app even when Okta goes offline. Use Identity Continuity to automatically switch authentication requests to Microsoft Entra ID without users ever knowing there was a problem.

  • Define your strategy. Set Okta as your primary IDP and Microsoft Entra ID as your secondary IDP in the Maverics UI, then use your Identity Fabric to define your failover strategy.
  • Define the attributes your application needs in the Schema Abstraction Layer™. Separately map them to claims available between Okta and Microsoft Entra ID.
  • Configure continuity. Set health check parameters for triggering failover, simulate outages, and prepare your systems (and users) for any continuity scenarios. Maverics’ hybrid air-gap architecture ensures orchestrator availability so that identity services are available even when Okta is inaccessible.

Ready to cook up your perfect identity modernization solution?

Stop juggling disparate identity services. Unleash the power of Strata’s orchestration recipes.
Whether you’re dealing with legacy app modernization or controlling multi-cloud access, Orchestration Recipes have got you covered.

Read the docsTry this in Maverics