Blog Post

Microsoft Entra Blog
2 MIN READ

Introducing Machine Learning based recommendations in Azure AD Access reviews

Joseph Dadzie's avatar
Joseph Dadzie
Icon for Microsoft rankMicrosoft
Dec 01, 2022

Many of you are already using Azure AD access reviews to govern access of your employees, guests, and workload identities to sensitive resources. Over the years, one of the top requests from our customers is to make the review process easier so that reviewers can make quicker and more accurate decisions. Today, I’m excited to share that we’ve vastly enhanced our recommendations in access reviews using sophisticated machine learning models that determine users’ affiliation to the group being reviewed, based on the organization’s reporting structure. This additional recommendation makes the entire process much easier for reviewers, thereby increasing reviewer efficiency, reducing attestation fatigue, and ensuring that your sensitive resources are secure. 

 

Microsoft Entra Identity Governance is helping customers move beyond the traditional Identity governance approach of managing access, thereby reducing cost and increasing productivity.  

 

 

 

What is User-to-Group Affiliation? 

The User-to-Group Affiliation recommendation compares users’ relative affiliation with other users in the group, based on the organization’s reporting structure. Our machine learning based scoring mechanism identifies the distance between the users in an organizational hierarchy to detect those users who are very distant from other users in the group i.e., have "low affiliation" and our system then provides a ‘Deny’ recommendation. 

 

Enabling this recommendation in access reviews is a one-click process 

Switching on this recommendation while creating access reviews is easy – select the decision helper “User-to-Group Affiliation” in settings during the access review creation experience and the rest is the same as any other access review. 

 

 

 

Recommendations for Reviewers of access reviews: 

The reviewers of access reviews see the recommendations if a user has “Low Affiliation” with other users within the group along with our existing Inactive user recommendation. The reviewer can accept the recommendations by clicking on “Accept Recommendations” or can manually “Accept” or “Deny” access based on the recommendations, thereby helping the reviewer make a quick decision. 

 

 

 

Additional details to enhance access review decision making: 

A reviewer who needs additional information to make an access decision can click on “Details” and will get an option to “Accept” or “Deny” access. If the reviewer selects the recommended option, the decision can be submitted directly, whereas, if the reviewer goes against the recommended option, a reason is required before the decision is submitted.  

 

 

 

Try it now by navigating to the Entra Identity Governance and enabling access reviews on a group. 

 

Resources and Feedback: 

For more information, please visit User-to-Group Affiliation recommendation for Azure AD Access reviews 

As we work on simplifying identity governance processes through analytics, we want to hear from you! Please leave your comments down below or reach out to us on aka.ms/AzureADFeedback.  

 

Joseph Dadzie, Partner Director of Product Management 

Twitter: @joe_dadzie 

 

 

Learn more about Microsoft identity: 

Updated Dec 01, 2022
Version 2.0
  • Thanks. We use ML models such as the z-score normalization and others to determine distance between peers for organizations of varying sizes and org hierarchy complexities. The recommendation is immediately included in the review when it is started by the creator of Access review.

  • chrisp1992's avatar
    chrisp1992
    Brass Contributor

    This looks interesting!

     

    Is there anything coming to Approve/Deny based on last sign-in past 30 days? We have situations where a 90 day window is appropriate, and a 30 day is simply too short to reliably deny. 

  • Thanks for the feedback. The changes to provide inactive user recommendation for beyond 30 days is in our roadmap.

  • MikeCrowley's avatar
    MikeCrowley
    Iron Contributor

    Nice!

    Is this new behavior simply measuring the distance based on the manager attribute(s), or is there more to it? i.e. where is the ML part and/or what else should a reviewer be considering when they accept that aspect of the recommendation? Also, is this recommendation immediately incorporated, or is there a duration element as well?