Hey everyone - it's time for the next installment of the Ignite recap blogs. This one is brought to you by Elisabeth and Jose from the external identities team. They are doing a ton of exciting work ...
Updated Jul 24, 2020
Version 16.0
Blog Post
I understand the directory services account management, SAML assertions for authentication, and the RBAC concepts of Azure B2B.
What I don't understand , however, is attestation.
The account itself is secure as are the authentication mechanism and conditional access elements, but how is a person who assets an identity and is granted an account an credentials validated ? In my organization, a user is only granted an on-premise directory account following an interview proces where a manager reviews their identity proofing pieces , such as driver's license, passport etc.
I don't see how Azure B2B addresses this, and it seems less robust than a federation agreement with a trusted organization.
Am I missing something?