Share via


Custom attributes for Dynamic Distribution Groups in EMC

Question

Monday, February 3, 2020 6:12 PM

How do custom attributes work? Does it simply search for the entered string in the value of all unlisted attributes? For example, we want each of our 3 sites to have a distribution list, and each user has the name of the site they are stationed at in the Office field. Simply entering the value of the Office field as a custom attribute doesn't work.

All replies (3)

Tuesday, February 4, 2020 5:40 AM âś…Answered

Hi,

We can refer to the introduction about custom attributes in the official document: Custom attributes

In your scenario, if we want to create dynamic DG according to custom attributes set to uses, we can follow the following steps, I have tried in my environment and it can work properly:

1. Make sure all the users in your organization have their own custom attribute. (For example, custom attribute1 records us)

2. Then we can create Dynamic DG, choose add a rule, select custom attribute1 and specify the site value  

3. Check the configuration of the Dynamic DG again after saving it, make sure the Recipient Container is correct

Regards,

Joyce Shen

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].


Tuesday, February 4, 2020 8:07 AM

Custom Attributes stands as filtering property so that you target the audience only with tagged Custom attributes

Pickup a Unique Attribute from AD based on Office Address or Department and created DDL as mentioned below by Joyce

Vinny | Freelancer | Microsoft Certified Azure Solutions Architect Expert| Microsoft 365 Certified: Enterprise Administrator | Microsoft 365 Certified: Messaging Administrator Associate| ITILV3 | PMP


Tuesday, February 4, 2020 1:21 PM

So, I understand how to do that - I think what I didn't understand was that "custom attribute" is a field that already exists in AD. We want to pull from a specific field that already exists in AD that is not a custom field - looks like that is achievable by creating the DDL via powershell. Thanks for the help y'all.