Skip to content
Notifications
Clear all

Migrated from Azure AD B2C to Entra ID for a customer portal - what we learned

2 Posts
2 Users
0 Reactions
68 Views
(@emilykim)
Reputable Member
Joined: 4 months ago
Posts: 349
Topic starter   [#21462]

Our organization recently completed a migration of a customer-facing portal from Azure AD B2C to Microsoft Entra ID (formerly Azure AD). The decision was driven by a need for deeper integration with our internal M365 ecosystem and a reassessment of long-term FinOps strategy. This was not a trivial lift-and-shift, and the operational differences are significant.

Key findings from the migration process:

* **Cost Structure Shift:** Moving from B2C's monthly active user (MAU) model to Entra ID's per-user licensing required a detailed analysis of our user base. For our low-frequency portal, the MAU model was initially more favorable. However, consolidating with our existing Entra ID P1 licenses for employees created a net saving by eliminating a separate billing line.
* **Feature Parity is Not Automatic:** Several B2C-specific features, like customizable user flows and identity providers (e.g., social logins), are implemented differently. We had to rebuild the authentication user journey using Entra ID External ID for customers, which offers more granular integration points but less pre-built UI.
* **Administrative Overhead Changed:** B2C operates in a somewhat isolated tenant. Entra ID integration means our customer identities now reside alongside employee identities. This demanded stricter governance and scoping of administrative roles to maintain security boundaries.

The most substantial learning was that this migration is fundamentally an identity architecture redesign, not a simple service swap. The development effort to adapt our application to the Microsoft Identity Platform libraries and the new policy configurations was considerable.

For teams considering a similar move, I recommend a thorough comparison of:
* The total cost of ownership under both models, factoring in license consolidation.
* The development cost of re-implementing authentication journeys.
* The operational model for managing external identities within your primary tenant.

—EK


Your bill is too high.


   
Quote
(@clarag)
Reputable Member
Joined: 4 months ago
Posts: 274
 

I'm a project manager at a 50-person professional services firm, and I run our internal resource planning and client portal access. We went through this exact evaluation last year for a client portal and stuck with B2C.

**Target Audience Fit:** B2C is built for external, high-volume, low-touch users. Entra ID External ID is for external users who need deep integration with your internal resources. If over 90% of your users are strangers signing up once, B2C.
**Real Cost for SMBs:** B2C's first 50,000 monthly active users are free. After that, it's about $0.00325 per MAU. Entra ID External ID requires at least Entra ID P1 licenses, which start around $6 user/month. For a portal with 10,000 low-engagement users, B2C costs pennies; Entra ID costs tens of thousands a year.
**Deployment & Customization Effort:** B2C user flows are quicker to set up for standard sign-up/sign-in. Entra ID required our devs to build more UI from scratch using MSAL and custom policies, which added about 3-4 weeks of work.
**Honest Limitation:** Entra ID's admin experience is far better if you're already managing employees there - one pane of glass. B2C feels like a separate, simpler tool, which was a con for our IT team but a pro for our project team managing the portal independently.

I'd only pick Entra ID for this if the portal users are an extension of your internal team (like contractors or partners) who need access to some internal SharePoint or Teams. For a pure customer portal, B2C still wins on cost and simplicity. Tell us the ratio of customer logins to internal M365 integrations, and the call becomes easy.



   
ReplyQuote