Forum Discussion
EXO's "User" and "Trustee" properties returned from Get-Mailbox/RecipientPermission
The_Exchange_Team I have a situation where FullAccess and Send-As permission holder users have their PrimarySmtpAddress/UserPrincipalName value stored within various properties on multiple different ...
In my current scenario, there are 2 separate Exchange orgs with Hybrid Configs into the same tenant. There are some users from org1 who have moved over to org 2. They only require 1 mailbox, but require a user account in both orgs, and need to be visible in both orgs' Address Books. This was accomplished by converting the original mailbox to mailuser and the externalEmailAddress is the new mailbox in org2.
Everything is happy with this arrangement, such as AAD Connect and AAD (no conflicts etc). The only issue is this mailbox permissions non-repudiation.
It's funny because I remember way back in 2004, my teacher Jim, who was teaching me courses for MCSA 2003, ways very vocal about the importance of non-repudiation in IT security and compliance. Here it is 20 years later and customers do not have guaranteed non-repudiation within their mailbox ACL's.
Everything is happy with this arrangement, such as AAD Connect and AAD (no conflicts etc). The only issue is this mailbox permissions non-repudiation.
It's funny because I remember way back in 2004, my teacher Jim, who was teaching me courses for MCSA 2003, ways very vocal about the importance of non-repudiation in IT security and compliance. Here it is 20 years later and customers do not have guaranteed non-repudiation within their mailbox ACL's.
Well to end off my week with a little more grace, I am here to dial back some of my harsh word choices earlier. In the end, I do appreciate the -ReadFromDomainController secret move, however I will prefer to do Get-Recipient -Filter for UPN instead. Which leaves confirmation of what the other value is (Name, something else) when it's not the UPN format, for GrantSendOnBehalf property.