Contact Problems

Fix Dynamic Distribution Group Members Showing Object IDs Instead of Names

Ayan Masood Sep 28, 2026 869 views

Question details

Users see Object IDs instead of display names for certain members when using the Get-DynamicDistributionGroupMember command in Exchange Online.

Fix Dynamic Distribution Group Members Showing Object IDs Instead of Names

Product: Microsoft Exchange Online
Device & OS: not provided
Scenario: Managing Dynamic Distribution Group memberships via PowerShell in hybrid or cloud-only tenant environments.
Observed behavior: The PowerShell command output displays the external directory Object ID rather than the actual user name for synchronized Active Directory members.

Before you start

Ensure you have Exchange Administrator privileges and the latest Exchange Online PowerShell module installed on your system before proceeding.

Solution 1Recommended

Update the User Display Name via Exchange Online PowerShell

Connect to your Exchange Online environment using PowerShell and manually override the mismatched Name parameter for affected synchronized users.

This behavior is usually the result of a naming convention change applied to the Exchange Online Name parameter for users synchronized from a local Active Directory. Because the Name parameter defaults to matching the external directory object ID, PowerShell outputs the ID instead of the expected human-readable name. Updating the parameter manually with the Set-User cmdlet resolves this display discrepancy.

Open PowerShell as Administrator

Right-click your Start menu and select Windows PowerShell (Admin) or Terminal (Admin) to open an elevated command prompt.

Connect to Exchange Online

Type the command 'Connect-ExchangeOnline' and press Enter. Sign in with your Microsoft 365 Exchange Administrator credentials when prompted.

Identify Affected Users

Compare the user's Name attribute in your output with their external directory object ID to confirm which specific accounts need updating.

Update the Name Parameter

Run the command 'Set-User -Identity <ObjectID> -Name "<Desired Display Name>"' replacing the placeholders with the actual Object ID and the correct user name.

Verify the Change

Run the 'Get-DynamicDistributionGroupMember' command again to confirm that the updated user now correctly displays by name instead of Object ID.

Update the User Display Name via Exchange Online PowerShell

Note on Synchronization: If you are running Azure AD Connect, ensure that your on-premises Active Directory attributes are correctly formatted to prevent future synchronization cycles from overwriting your changes.

Free Microsoft Office alternative

Try WPS Office for Your Daily Productivity Needs

Managing enterprise server environments and Exchange PowerShell commands can be complex, but your everyday document tasks don't have to be. WPS Office offers a powerful, free, and lightweight alternative to Microsoft Office, providing everything you need to create documents, spreadsheets, and presentations with zero hassle.

1. Visit the WPS Office Website: Navigate to the official WPS Office website using your web browser.
2. Download the Installer: Click the Free Download button tailored to your operating system.
3. Install and Launch: Run the downloaded installer and follow the quick on-screen instructions to begin using your new office suite.

Fully compatible with Microsoft Excel, Word, and PowerPoint formats.Free, lightweight, and fast-loading, saving system resources.Familiar tabbed user interface ensuring seamless migration from Microsoft Office.Built-in PDF editing tools for comprehensive document management.

microsoft office alternative - wps office

Frequently Asked Questions

Why does Get-DynamicDistributionGroupMember show an Object ID?

This happens due to a Microsoft Exchange Online naming convention update. For users synchronized from local Active Directory, the Name parameter now frequently defaults to the external directory object ID rather than the user's display name.

Does this issue affect email delivery to the group?

No. The Object ID displaying instead of the name is strictly a visual output issue in PowerShell. Group routing and email delivery will continue to function normally as long as the underlying Exchange attributes are intact.

Can this be fixed directly in local Active Directory?

Yes, standardizing the Name attributes within your on-premises Active Directory and forcing a manual Azure AD Connect sync can help resolve the discrepancy across hybrid environments.

Outlook & Email Problems