Feb 10 2023 03:56 AM
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 after a few consultations I can't leave the place.
3) Briefly: I work with the big Tenet, with multiple domains. Although Tenet can be considered a large company and these domains are "its departments", these domains themselves are independent organizations that can even communicate with each other.
4) When you want to send a message to multiple recipients, querying the GAL, whether due to display limitations or an endless and non-assertive query, becomes a real inconvenience to the end user.
5) What's my best way?: Create custom Address Books (Address Book), where each List contains users from your own domain. That, in addition to the GAL itself, of course.
6) With that, I basically thought of:
- Create an Address Book
New-AddressList -Name 'DOMAIN1'
New-AddressList -Name 'DOMAIN2'
- Add the conditions and filters for each one:
Set-AddressList -Identity "DOMAIN1" -RecipientFilter "(RecipientType -eq 'UserMailbox')"
Set-AddressList -Identity "DOMAIN1" -RecipientFilter "(UserPrincipalName -like '*@domain1.com')"
Set-AddressList -Identity "DOMAIN2" -RecipientFilter "(RecipientType -eq 'UserMailbox')"
Set-AddressList -Identity "DOMAIN2" -RecipientFilter "(UserPrincipalName -like '*@domain1.com')"
... Although I would like to increment these lists from the CompanyName field of each user, existing in Azure AD ....
7) Well. the Address List appears normally, about a few minutes after I run the command for it to be created, but I really have difficulties in the part that deals with the user of each domain.
8) Could someone explain to me what could be happening? Better... Where am I going wrong, either in the execution OR in the conception of the idea?!
Many, many thanks for your attention and patience in helping with this issue!
Feb 10 2023 09:30 AM
Feb 10 2023 02:56 PM
Feb 10 2023 04:29 PM
Feb 12 2023 07:44 AM
SolutionFeb 15 2023 12:01 PM