Getting msExchRecipientDisplayType values via $dirObj, returns a System.__ComObject reference, not the integer.

This is interesting. I am seeing the same results and cannot seem to find a way to retrieve the values from the ComObject. Looks like these values may need to be retrieved via the QAD cmdlets, such as the following example:

$dn = $DirObj.Get("distinguishedname")
$objUser = Get-QADUser -Proxy -Identity $dn -IncludedProperties msExchRemoteRecipientType, msExchRecipientTypeDetails, mail

$msExchRecipientTypeDetails = $objUser.msExchRecipientTypeDetails
$msExchRemoteRecipientType = $objUser.msExchRemoteRecipientType

This is interesting. I am seeing the same results and cannot seem to find a way to retrieve the values from the ComObject. Looks like these values may need to be retrieved via the QAD cmdlets, such as the following example:

$dn = $DirObj.Get("distinguishedname")
$objUser = Get-QADUser -Proxy -Identity $dn -IncludedProperties msExchRemoteRecipientType, msExchRecipientTypeDetails, mail

$msExchRecipientTypeDetails = $objUser.msExchRecipientTypeDetails
$msExchRemoteRecipientType = $objUser.msExchRemoteRecipientType

Thanks for confirming. There is a noticeable performance impact with policy scripts when get-qaduser is used, the SDK recommends that you use DirObj instead, which is why I went that route. Is this worth taking to the product team ?

Why not use the native Get-ADuser?