Avoid a full app rewrite
Add customer login and MFA at the access layer instead of rebuilding every legacy application.
Customer identity for existing apps
Add Azure AD B2C Login and MFA to Legacy Apps Without Code Changes
Use Datawiza Access Proxy to extend Azure AD B2C, now part of the Microsoft Entra External ID family, to customer-facing, partner, legacy, and on-prem web applications without rebuilding login.
Why teams use this pattern
Customer-facing legacy apps still need modern login and MFA
Preserve existing app behavior
Keep the application, session model, and backend logic intact while modernizing access.
Protect external users
Add stronger authentication for customers, partners, members, vendors, or other external users.
Roll out gradually
Pilot one portal or app first, then expand the same pattern across more web properties.
How it works
Put Azure AD B2C login in front of the existing app
Route traffic through Datawiza
Users reach the application through Datawiza Access Proxy before they reach the legacy app.
Connect Azure AD B2C
Use Azure AD B2C or Entra External ID as the customer identity provider.
Enforce MFA and policy
Challenge users and apply access rules before allowing traffic to continue.
Forward trusted identity context
Datawiza can pass approved identity context to the app through supported proxy patterns.
Best fit
Where this works best
This page is most relevant when the goal is customer or external-user access for an application that already exists. If the app cannot be changed quickly, Datawiza lets teams place a modern identity layer in front of it.
For adjacent use cases, see MFA for customer portals and no-code MFA.
Good candidates include
Customer portals and partner portals
Member, patient, student, vendor, or supplier portals
On-premises web apps that need external-user login and MFA
Legacy apps that are not ready for a full CIAM or login migration
Deployment
Modernize customer login without forcing a big migration first
Hosted or self-hosted
Choose a Datawiza-hosted deployment or run the proxy in your own environment.
App-by-app rollout
Start with one customer-facing app and expand after validating user experience and policy.
External-user flexibility
Use identity and MFA policies that fit the audience rather than forcing every app into the same model immediately.
Audit and access visibility
Capture authentication and policy events for security review and operations.
FAQ
Azure AD B2C login and MFA FAQ
Is Azure AD B2C still relevant?
Many teams still use the Azure AD B2C name in existing projects and searches. Microsoft has also introduced the Microsoft Entra External ID family for customer and external identity scenarios.
Can we add Azure AD B2C login without changing the app?
In many browser-based scenarios, yes. Datawiza can sit in front of the app and enforce login and MFA before traffic reaches the application.
Is this only for cloud apps?
No. The pattern can support on-premises, private cloud, public cloud, and hybrid applications when the traffic can be routed through Datawiza.
Can this protect customer portals?
Yes. It is a strong fit for existing customer, partner, member, and vendor portals that need stronger authentication without a full rewrite.
Add customer login and MFA to one existing app
Use Datawiza to test Azure AD B2C or Entra External ID login in front of one portal before expanding across more legacy apps.