KshitijGulatithanks for the reply! We have created many custom roles over the past decade in both Exchange On prem and Exchange Online, and we really appreciate the ability to go with a least privileged model. Which is why we were taken aback on the guidance from MSFT to NOT create child roles in Exchange Online as they may or may not work as expected. If this is still true, then I think it makes sense to either call that out or detail which roles shouldn't be made into pruned child roles in this blog post. This would be beneficial not only to your customers but also to your support staff. As my team wasted dozen of our own and MSFT supports' work hours troubleshooting why our child RBAC role wasn't working.