← Back to Recipes

How to extend Azure AD to any non-standard legacy app

Protect complex headers- and forms-based or LDAP-bound apps behind Azure AD without refactoring.

Read the docsTry this in Maverics
  • Extend Azure AD’s modern authentication and authorization to any legacy app
  • Deploy Azure AD in hours without navigating change management or app downtime
  • Protect all apps — no matter where they are — without disrupting the user experience
Ingredients
Modern Authentication Non-standard App Entra ID (Azure AD)

Don’t let non-standard apps delay your Azure AD migration timeline

Recipe details

This is how everything works together.

Sequence details

This is how everything works together.

What the user sees

App users don’t care what IDP you authenticate with — they care that it works. Use Identity Orchestration to deliver smooth consistency so that users get the consistent Azure AD experience for every app.

  • Familiar login. Users head to the same screen and start the app authentication flow.
  • Invisible redirection. Behind the scenes, Maverics evaluates the app policy in config and directs the user to Azure AD.
  • Quick authentication. The user enters their login details, gets authenticated and logs in. Everything in the app looks the same as before.

What the admin does

Switching to Azure AD stopped being optional when support started crumbling for your legacy IDP. Use Identity Orchestration to modernize for good.

  • Prepare your work surface. Define the upstream application and the port Maverics will use to communicate with the app.
  • Set the rules. Define the basic policy that enforces authentication to <IDP> and define how Maverics will provide context to the upstream application.
  • Configure. Set Maverics up as an authentication gateway and give it the right permissions to direct users correctly.

See it in action

Protect on-prem apps with Microsoft Entra ID

Interested to see more? We have a full workshop for you!

Watch now

Solve more modernization challenges with ready-to-deploy recipes

Identity Continuity
Active Directory (AD)
Okta
Failover from Okta to on-prem Active Directory (AD)

Keep your critical apps accessible. Use Identity Continuity to allow key users to securely authenticate locally with Keycloak if Microsoft Entra ID ever becomes unavailable.

Identity Continuity
Okta
Entra ID (Azure AD)
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.

Identity Continuity
Keycloak
Entra ID (Azure AD)
Failover from Microsoft Entra ID to on-prem Keycloak

Keep your critical apps accessible. Use Identity Continuity to allow key users to securely authenticate locally with Keycloak if Microsoft Entra ID ever becomes unavailable.

View all recipes

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