Anonymous

My feedback

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

    We’ll send you updates on this idea

    409 comments  ·  Azure Active Directory » SaaS Applications  ·  Flag idea as inappropriate…  ·  Admin →

    We’re currently evaluating an option that will provide the functionality offered by nested groups, but removes the complexity nested groups adds. We appreciate your patience on this ask and want to ensure we deliver a solution that benefits all of our customers. Below are use cases that we’d like for you to stack rank, with #1 being priority for you. We thank you for the continued comments and feedback.

    Use case A: nested group in a cloud security group inherits apps assignment
    Use case B: nested group in a cloud security group inherits license assignment
    Use case C: nesting groups under Office 365 groups

    Anonymous supported this idea  · 
  2. 196 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Anonymous commented  · 

    Completely agreed.
    Although It is possible to set users' company phone numbers in on-premise AD and sync them through AAD Connect, you can't set company phone number as a way of OneWaySMS.
    An Administrator should be able to do the same thing for users' authentication phone numbers.
    That way MFA would be set before users actually start using their account, and users wouldn't be able to change it by themselves in the future.

    Anonymous supported this idea  · 

Feedback and Knowledge Base