Anonymous

My feedback

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

    We’ll send you updates on this idea

    We’re really pleased to let you know that we’ve released the first authentication method APIs to public preview:

    https://docs.microsoft.com/graph/api/resources/authenticationmethods-overview

    So far there are APIs for managing phone numbers and password resets. When phone numbers are set with the API, the user can use that number for MFA and SSPR (as allowed by your tenant’s policy).

    The team is hard at work at building out APIs for all of the other authentication methods, and we’ll update the response here as they’re released.

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

    Although this is possible now by populating the correlated fields on the Azure AD user object - see this article - https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-sspr-authenticationdata

    It still is a concern for us, because the strongauthenticationuserdetails is secured so that only the user and admins can see it, where the AlternateEmail and MobilePhone fields on the object itself are viewable directory data, which we don't want populated for our users, because other users could possibly see this data.

  2. 55 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 327 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  44 comments  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base