Anon E. Mousse

My feedback

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

    We’ll send you updates on this idea

    0 comments  ·  Azure Active Directory » Conditional Access  ·  Flag idea as inappropriate…  ·  Admin →
    Anon E. Mousse shared this idea  · 
  2. 42 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  3 comments  ·  Azure Active Directory » Conditional Access  ·  Flag idea as inappropriate…  ·  Admin →
    Anon E. Mousse supported this idea  · 
  3. 483 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    39 comments  ·  Azure Active Directory » Conditional Access  ·  Flag idea as inappropriate…  ·  Admin →
    Anon E. Mousse supported this idea  · 
  4. 189 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anon E. Mousse supported this idea  · 
  5. 412 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anon E. Mousse supported this idea  · 
    An error occurred while saving the comment
    Anon E. Mousse commented  · 

    Is there an update on this?
    SSPR with Hybrid AD and many remote users (no VPN) is almost useless without also updating the local cached credentials! Very poor end-user experience and far too confusing to try to explain.

  6. 70 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anon E. Mousse supported this idea  · 
  7. 8 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Azure Active Directory » Reporting  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anon E. Mousse commented  · 

    Is there an update on this?
    30 days of logs is often not nearly enough. Especially when running a forensic investigation where suspected activites took place several weeks ago.

    Anon E. Mousse supported this idea  · 
  8. 116 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anon E. Mousse supported this idea  · 
    An error occurred while saving the comment
    Anon E. Mousse commented  · 

    The feature in Windows 10 logon should be re-labeld as "Manage Password" or some similar. It absolutely needs to cover both password changes and account unlock functionality.

  9. 38 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Azure Active Directory » SaaS Applications  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anon E. Mousse commented  · 

    Absolutely need this feature! So many third-party iDP's don't necessarily align 1to1 with respect to claims attributes. ADFS has had this ability for quite a while now. This is the one missing feature that is keeping us on ADFS for a number of applications.

    Anon E. Mousse supported this idea  · 
  10. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Active Directory  ·  Flag idea as inappropriate…  ·  Admin →
    Anon E. Mousse supported this idea  · 
  11. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Active Directory » Conditional Access  ·  Flag idea as inappropriate…  ·  Admin →
    Anon E. Mousse shared this idea  · 
  12. 525 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

    Our feature team is looking into options for addressing this scenario, but we do not yet have any timelines to share. For now as a workaround, you can manually trigger the reprocessing by updating the membership rule to add a whitespace at the end. We’ve also added the ability to check the membership processing status, to keep track of the status and know if processing is complete.

    Anon E. Mousse supported this idea  · 

Feedback and Knowledge Base