You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2021. It is now read-only.
Email administrators may use TargetAddress to forward email outside the company, and this property does ignore a tenant's forwarding rules.
I've been able to locate this property using ADSI/On Premise AD, I have not been able to locate it in EOP, O365, AzureAD, or Exchange Online powershell commands. More information: https://serverfault.com/q/920344/477213
Once the relevant TargetAddress attribute is located, please add it to DumpDelegatesandForwardingRules.ps1 as the logical effect of "forwarding" is the same as what that script is trying to report on.
The text was updated successfully, but these errors were encountered:
TargetAddress gets mapped direct through In sync rules (this is user, same for inetorgperson and contact on this property),
however, in four Tenants with AAD Sync I couldn't manage to pull that attribute up through MSOnline, AzureAD, AzureADPreview, Exchange Online remote shell, or Exchange Online Hybrid Shell.
It's interesting, because it shows that those attributes are mapped through, but I don't see them anywhere in AzureAD or O365
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Email administrators may use TargetAddress to forward email outside the company, and this property does ignore a tenant's forwarding rules.
I've been able to locate this property using ADSI/On Premise AD, I have not been able to locate it in EOP, O365, AzureAD, or Exchange Online powershell commands. More information:
https://serverfault.com/q/920344/477213
Once the relevant TargetAddress attribute is located, please add it to DumpDelegatesandForwardingRules.ps1 as the logical effect of "forwarding" is the same as what that script is trying to report on.
The text was updated successfully, but these errors were encountered: