We’re still considering this, and would love to hear your scenarios for this combination. Please add comments to give us more details.
An error occurred while saving the commentAlex Bedig commented
One use case is streamlining the migration from an internal app to a customer-facing one. As it stands today, there are different customer records and a migration and synchronization process between the two tenants that must be addressed by the developer, i.e. it is not "you have users in your directory, now we can create a different authentication path and support the same user accounts via configuration." This would reduce friction in using B2B's invitation system as an entry point for partners while doing early betas (super easy to get started), prior to rolling out with B2C as the primary front door to the commercial offering.
Rest assured we still have this request in mind and are continually reviewing it. Please keep your feedback coming!
151 votes14 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
Azure MFA is currently designing the experience for FIDO 2.0. This is the next iteration of the FIDO U2F standard that the link references.