Jeremy Adkins

My feedback

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

    We’ll send you updates on this idea

    under review  ·  Azure AD Team responded

    Thank you for your feedback! The feature team is aware of this suggestion and will keep it under consideration. There are technical challenges to overcome in order to make this happen. Please keep the votes coming if this feature matters to you.

    Chen

    Jeremy Adkins supported this idea  · 
  2. 146 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Jeremy Adkins supported this idea  · 
  3. 191 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  Azure AD Team responded

    Thank you for your feedback! We have heard you and are considering future implementation options. There is no timeline yet for implementation. If this feature matters to you, keep voting as it will help us prioritize.

    Jeremy Adkins supported this idea  · 
  4. 127 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    24 comments  ·  Azure Active Directory » Conditional Access  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy Adkins supported this idea  · 
  5. 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

    Jeremy Adkins supported this idea  · 
  6. 48 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    12 comments  ·  Azure Active Directory » Identity Protection  ·  Flag idea as inappropriate…  ·  Admin →
    started  ·  Azure AD Team responded

    Thanks for your feedback, folks. We have been working towards resolving the locations for IPv6 logins. Currently, a subset of such logins are getting resolved for location and the % will gradually go up. Are you seeing some of your IPv6 logins with resolved location?

    An error occurred while saving the comment
    Jeremy Adkins commented  · 

    This should be getting more attention. Major mobile providers and ISPs are moving to IPv6 T-Mobile, Verizon, Charter\Spectrum to name a few. This issue makes it impossible to effectively use the include unknown locations option in CA policies. Combined with the inability to include or exclude IPv6 addresses or ranges in the same way you can IPv4 this causes a huge gap in what is otherwise a great resource for Identity Security.

    Jeremy Adkins supported this idea  · 
  7. 99 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Jeremy Adkins supported this idea  · 
  8. 67 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  Azure AD Team responded

    We’ll take this in consideration as we plan new features. In the short term, we are working on Graph API‘s that will allow you to change phone numbers in the StrongAuthentication fields.

    Richard

    An error occurred while saving the comment
    Jeremy Adkins commented  · 

    This would be useful. Other options that could work in our scenario would be to set this based on the countryCode attribute rather than requiring it in the telephoneNumber attribute with a <space> after the +1. You could also let the user select the country if it isn't included in they synced telephoneNumber attribute.

    Jeremy Adkins supported this idea  · 
  9. 18 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Jeremy Adkins shared this idea  · 

Feedback and Knowledge Base