Forum Discussion
tcboeira
Feb 10, 2023Brass Contributor
Difficulties in creating Personalized Address Lists
Hi Good Morning Friends, 1) First of all, as always, I apologize if the words seem strange. I don't speak English and I use an online translator 2) Well, having said that, I have a doubt that...
- Feb 12, 2023Well if you've cleared the value of CustomAttribute11, those mailboxes will definitely not appear in the newly created AL. If you are using the recipient filter shown above, set the value of CustomAttribute11 for few mailboxes, give it few minutes and check the AL membership (preferably in OWA). The "touch" part needs to be done once the AL is created, and you can use any attribute, such as changing the CustomAttribute11 from $null to something in this scenario.
VasilMichev
Feb 10, 2023MVP
You need one additional step here - in Exchange Online, you need to "touch" each object before they appear in Address Lists. Read here for details: https://learn.microsoft.com/en-US/exchange/troubleshoot/administration/new-address-lists-not-contains-all-recipients
If after "touching" the objects you're still having issues, double-check your RecipientFilter.
If after "touching" the objects you're still having issues, double-check your RecipientFilter.
- tcboeiraFeb 10, 2023Brass ContributorHello, I hope everyone is well...
Thank you very much Vasil Michev for his return...
If I may, let me ask if the logic for this outline is correct:
I adjusted the "CustomAttribute11" field of the domain accounts as desired (in this case I did it with two accounts of each):
Set-Mailbox email address removed for privacy reasons -CustomAttribute11 "DOMAIN1"
Set-Mailbox email address removed for privacy reasons -CustomAttribute11 "DOMAIN2"
That done, I created the lists:
New-AddressList -Name 'DOMAIN1'
New-AddressList -Name 'DOMAIN2'
Finally, I adjusted the list as follows:
Set-AddressList -Identity "DOMAIN1" -ConditionalCustomAttribute11 "DOMAIN1" -IncludedRecipients MailboxUsers
Set-AddressList -Identity "DOMAIN2" -ConditionalCustomAttribute11 "DOMAIN2" -IncludedRecipients MailboxUsers
I remove/clean the CustomAttribute11 attribute field (which is what I chose to use)
Set-Mailbox email address removed for privacy reasons -CustomAttribute11 $null
Set-Mailbox email address removed for privacy reasons -CustomAttribute11 $null
Is this the same idea? The "playback" time in the Exchange environment which is "tense" since we don't know if something is happening or not hehehe
Finally, now rereading, I found myself thinking that: When before I applied the "Set-AddressList" command twice where once I used "-RecipientFilter "(RecipientType -eq 'UserMailbox')"" and on the other "-RecipientFilter "(UserPrincipalName -like '*@domain1.com')"" I didn't actually add the two together. One overwrote the other.
I applied it here, as I mentioned above... I'm waiting to see "what happens".
Well, thank you very much for your feedback, for your help. Not only does it help me to better understand these applications, which are all new to me, but it makes me want to learn and do more and more.
Thank you very much, I look forward to your return and Hugs to all!!!- tcboeiraFeb 11, 2023Brass ContributorHello again...
After two hours it didn't have the desired effect...
When querying the return is the following:
Get-AddressList 'DOMAIN1'
Name DisplayName RecipientFilter
---- ----------- ---------------
DOMAIN1 DOMAIN1 ((CustomAttribute11 -eq 'DOMAIN1') -and (RecipientType -eq 'UserMailbox'))
Where could I be going wrong?!- VasilMichevFeb 12, 2023MVPWell if you've cleared the value of CustomAttribute11, those mailboxes will definitely not appear in the newly created AL. If you are using the recipient filter shown above, set the value of CustomAttribute11 for few mailboxes, give it few minutes and check the AL membership (preferably in OWA). The "touch" part needs to be done once the AL is created, and you can use any attribute, such as changing the CustomAttribute11 from $null to something in this scenario.