Others

Fix Exchange Dynamic Distribution List Showing Object IDs Instead of Names

Amos GikundaAmos Gikunda Oct 7, 2026 869 views

Question details

Administrators need a way to resolve user names instead of object IDs for specified senders in Dynamic Distribution Lists.

Fix Exchange Dynamic Distribution List Showing Object IDs Instead of Names
Product
Microsoft Exchange
Device & OS
not provided
Scenario
An administrator is attempting to identify, manage, or remove specified senders from an Exchange Dynamic Distribution List.
Observed behavior
Authorized senders appear as raw object IDs rather than readable user names in the admin interface, making management difficult.
Before you start

Ensure you have the necessary Exchange Administrator privileges and have the Exchange PowerShell module installed and connected to your environment.

Solution 1Recommended

Use Exchange PowerShell to Inspect and Update Sender Properties

PowerShell provides direct access to underlying Exchange properties, allowing you to correctly identify and update sender restrictions when the graphical interface fails to resolve object IDs.

When the Exchange Admin Center cannot resolve an object ID to a display name, PowerShell can expose the true attributes. It is important to look at message delivery restriction settings rather than ownership settings. The 'ManagedBy' property controls who owns the list, not who is allowed to send to it.

1
Connect to Exchange PowerShell

Open Windows PowerShell as an administrator and connect to your Exchange organization (for Exchange Online, use the Connect-ExchangeOnline cmdlet).

2
Inspect the Distribution Group

Run 'Get-DynamicDistributionGroup -Identity "YourGroupName" | Format-List' to view all configured properties for the affected list.

3
Check Sender Restrictions

Review properties such as 'AcceptMessagesOnlyFromSendersOrMembers' to see the current list of authorized senders and identify the problematic object IDs.

4
Update the Specified Senders

Use the 'Set-DynamicDistributionGroup' cmdlet to explicitly re-add or correct the authorized senders by their correct user principal names or identities, which often forces the system to resolve the names properly.

Use Exchange PowerShell to Inspect and Update Sender Properties
Need further PowerShell assistance?: For complex environments or bulk automated fixes, consider consulting the Microsoft PowerShell Tech Community for customized script solutions.
Free Microsoft Office alternative

Need a Lightweight Office Suite for Your Daily Tasks?

While resolving Exchange administration issues requires specialized Microsoft tools, your daily documentation doesn't have to be complicated. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office for creating documents, spreadsheets, and presentations.

  1. 1. Download the Installer: Visit the official WPS Office website and click the free download button.
  2. 2. Install the Software: Run the downloaded installer and follow the quick on-screen instructions to set up the suite.
  3. 3. Start Creating: Open WPS Writer, Spreadsheet, or Presentation to immediately start working with your existing Microsoft Office files.
Seamlessly compatible with Microsoft Office formats including DOCX, XLSX, and PPTXFree to use with a lightweight installation that saves system resourcesFamiliar tabbed user interface for an easy transition from other office suitesBuilt-in PDF editing tools for easy document management alongside your emails
microsoft office alternative - wps office

Frequently Asked Questions

Why do Dynamic Distribution Lists show object IDs instead of display names?

This commonly occurs due to synchronization delays, a missing display name attribute in the active directory, or a glitch in the graphical Exchange Admin Center that fails to translate the underlying GUID into a readable user object.

Does the ManagedBy property control who can send emails to the list?

No. The ManagedBy property is strictly used to designate the owners or administrators of the distribution list. To manage who can send messages to the list, you must modify delivery restriction properties like AcceptMessagesOnlyFrom.

Can I permanently fix this object ID issue from the Exchange Admin Center (EAC)?

Often, if the EAC is failing to resolve the object IDs, a permanent fix requires an administrator to use Exchange PowerShell to query the raw attributes and re-apply the correct user identities directly to the list.