Jitendra Shaw

My feedback

  1. 103 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Jitendra Shaw supported this idea  · 
    An error occurred while saving the comment
    Jitendra Shaw commented  · 

    Consider this requirement as immediate need of time and prioritize it.
    OATH tokens are useful in specific scenarios e.g. user cannot carry mobile device due to security measures or safety hazard.
    Until simplification of OATH token is not available, cloud MFA is not comprehensive solution.
    Current process to activate an OATH token is cumbersome, error prone and need Global Administrators (GA) valuable time. Just imagine all GA's time required for OATH token registration and activation, if an organization have 10000+ users who have to use OATH tokens.
    Rather than moving to automation and self registration, Azure AD users and GAs are stuck to manual/admin controlled process for OATH token as MFA offering.
    OATH registration can be done by GAs by BULK load operation but activation must be available as self service method for end user who have hardware token with them.

Feedback and Knowledge Base