The current access review configuration in image_d03e22.png uses the Manager as the designated reviewer, with Megan Bowen defined as the fallback reviewer. Because all requests are falling back to Megan Bowen, the system is unable to determine a valid manager for the users under review (likely due to the manager attribute being unconfigured in Microsoft Entra ID for these accounts).

Creating a separate access review for each role does not address the root issue of missing manager attributes, nor does it dynamically align review routing by department. To meet the goal, you should either ensure the manager property is properly populated for all administrators or create separate access reviews targeted at specific groups or departments with their respective department heads explicitly assigned as reviewers.

A. Yes: Creating separate reviews by role does not change the reviewer routing logic or fix missing user-manager relationships, meaning requests will continue going to the fallback reviewer.

Microsoft Official Documentation: What are Microsoft Entra access reviews? & Create an access review of Azure AD roles in Privileged Identity Management (PIM). Section: "Advanced / Reviewers selection" (Specifies that if 'Manager' is chosen and a user has no manager assigned in the directory, the review falls back to the designated fallback reviewer).