Skip to content

Commit e4d9433

Browse files
authored
Merge pull request #112568 from Rinki-MSFT/patch-7
Update faq-customers.md - why no Entra branding for B2C
2 parents 7556b9d + c26cc35 commit e4d9433

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/active-directory/external-identities/customers/faq-customers.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,6 +67,10 @@ Opt for the next generation Microsoft Entra External ID platform if:
6767
- You’re starting fresh building identities into apps or you're in the early stages of product discovery.
6868
- The benefits of rapid innovation, new features and capabilities are a priority.
6969

70+
### Why is Azure AD B2C not part of Entra ID/External ID?
71+
72+
Microsoft Entra External ID and Azure AD B2C are two separate platforms powered by ESTS and IEF respectively. Entra External ID is our new converged platform which is future proof and developer friendly to meet all your identity needs – B2E, B2B and B2C. At the same time, we will still continue to support Azure AD B2C as a separate product offering with no change in SLA, and we’ll continue investments in the product to ensure security, availability, and reliability.
73+
7074
## Next steps
7175

72-
[Learn more about Microsoft Entra External ID for customers](index.yml)
76+
[Learn more about Microsoft Entra External ID for customers](index.yml)

0 commit comments

Comments
 (0)