This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 95%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELW%3C/text%3E%3C/svg%3E)
Hello i keep getting this error when trying to assign admin roles "Object class organizationalUnit is not recognized as a valid object class for E-mail recipient objects."
any suggestions how to go about it ?
Could you provide more detailed information to us to narrow down this one?
The version am running is Exchange 2019. And this comes up when am using EAC to assign admin roles from the permission column after I add the permissions.
Are you trying to assign default RBAC permissions or customized RBAC permissions to the user? Based on my searching, this issue may relate to customized RBAC admin role.
Could you provide the detailed steps about it? I will check whether it could be recurrent in my tenant.
Any update about this thread now? Could you provide more detailed information about how you create this RBAC admin role to us for narrowing down this issue.
The image shows the actual error message being displayed @KyleXu-MSFT
And this one shows the roles am trying to assign. @KyleXu-MSFT
I try with this one, I would work in my Exchange 2019:
I guess this issue is related to the admin account that you used, I would suggest you create a new mailbox, then add it to those AD groups from ADUC:
Then try to use this new admin group to login EAC and create RBAC group.
I am seeing this error as well. Running Exchange 2019 CU12 with Feb23SU. Has anyone figured out a solution to this issue impacting the use of the ECP to create custom roles with OU filtering?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 75%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECA%3C/text%3E%3C/svg%3E)
The problem can be resolved by first creating the management role with the default scope. Once created, edit the role with the OU filter.
Source (in the comments): https://practical365.com/exchange-server-role-based-access-control-in-action/
"I know it has been a while, but I just came across this same error:
“Object class organizationalUnit is not recognized as a valid object class for E-mail recipient objects.”
What I had to do was create it with the Write Scope set to Default, save it, then I could come back and change the write scope to an Organizational Unit.
Hope this helps someone in the future."