Update (4/12/23): This feature was enabled in our worldwide and 21Vianet clouds in November 2022. All tenants in these clouds will see the changes. Rollout to our GCCH and DoD clouds has been paused ...
Updated Apr 12, 2023
Version 11.0
Blog Post
SHUikey In response to your question about piping. If we run get-recipientpermission and there are say 120 Trustees, if we then pipe the output into get-recipient to covert the Trustees names into something intelligible we have to wait for 120 instances of get-recipient to run.
Previously the output of get-recipientpermission was intelligible. Now for some Trustees it is and for others we see ExternalDirectoryObjectId
OK I know that I could find out the ExternalDirectoryObjectId of the recipient I'm interested in checking and then use the -trustee switch of get-recipientpermission to check for that trustee.
It's just that you have made something that was simple so much more difficult, particularly for access control admins who are not experienced Exchange Administrators and who are less confident with powershell, piping etc. I've had to create a custom function for our admins to use, whereas MS should be anticipating and providing this.