Set-DistributionGroup HiddenFromAddressListsEnabled Error

Why Microsoft 365 won't let you hide a synced group from address lists, and how to fix it on-premises with msExchHideFromAddressLists and a sync.

Set-DistributionGroup HiddenFromAddressListsEnabled Error

I hit the HiddenFromAddressListsEnabled error in 2018 while trying to tick Hide this group from address lists on a distribution group in the Office 365 Exchange admin centre. Instead of saving, it returned:

The action 'Set-DistributionGroup', 'HiddenFromAddressListsEnabled', can't be performed on the object 'Example Group' because the object is being synchronized from your on-premises organization. This action should be performed on the object in your on-premises organization.

The setting can still be changed, just not where you are trying to change it. Here is why it happens, and the fix that worked for me, updated for 2026.

Why the HiddenFromAddressListsEnabled error appears

In a hybrid setup, the group is created and owned in your on-premises Active Directory. A sync tool copies it to Microsoft 365.

On-premises is the source of authority, so Exchange Online refuses to edit the object. If it allowed the edit, your change would be overwritten at the next sync.

The cause has not changed. The same message still appears for mailboxes too, with Set-Mailbox in place of Set-DistributionGroup.

Update 2026: "Office 365" is now Microsoft 365, and Azure AD Connect is now Microsoft Entra Connect Sync.

The fix: change it on-premises

There are two ways. Both change the same setting on the on-premises object, which then syncs to the cloud.

Option 1: PowerShell

In my original note I used this command, and it is still correct. $true means the recipient is hidden from address lists:

Set-DistributionGroup -Identity "GroupName" -HiddenFromAddressListsEnabled $true

Update 2026: this cmdlet exists in both on-premises Exchange and Exchange Online, as the Set-DistributionGroup documentation shows.

If you run it in Exchange Online against a synced group, you get the very error above. Run it in the on-premises Exchange Management Shell instead, then sync.

Option 2: Active Directory attribute

This is the method Microsoft documents for hybrid deployments. The correct attribute name is msExchHideFromAddressLists (my original note misspelled it).

  1. Open Active Directory Users and Computers.
  2. If the Attribute Editor tab is not shown in object properties, click View > Advanced Features.
  3. Right-click the group and choose Properties.
  4. Open the Attribute Editor tab.
  5. Find msExchHideFromAddressLists, click Edit, and change the value from <Not set> to True.
  6. Click OK and close the dialogue.

msExchHideFromAddressLists

Then sync to Microsoft 365

Wait for the next scheduled sync, or force a delta sync on the Microsoft Entra Connect server:

Start-ADSyncSyncCycle -PolicyType Delta

msExchHideFromAddressLists is on Microsoft's list of attributes synchronised to Exchange Online for users, contacts and groups, so the change will flow up.

How to check it worked

Connect to Exchange Online with the current module, then read the value back:

Connect-ExchangeOnline
Get-DistributionGroup -Identity "GroupName" | Select-Object Name, HiddenFromAddressListsEnabled

You want True.

In Outlook, the global address list can take a while to update, especially with cached mode and the offline address book. Give it time before deciding it failed.

If the change doesn't arrive

  • Confirm the sync ran without errors in Synchronization Service Manager.
  • Check that the object's mailNickname (alias) attribute is populated. A Microsoft Q&A community answer explains that if it is empty, changes to Exchange-related attributes are not synced. This is community advice rather than formal documentation, but it is worth checking.
  • Make sure you edited the right object, especially if several groups have similar names.

Cautions before you start

  • Back up first. Note the current attribute value, or export the group so you can roll back, for example Get-ADGroup "GroupName" -Properties * | Export-Clixml .\GroupName-backup.xml.
  • Edit attributes carefully. Editing the wrong attribute can affect mail flow. Change only the one you need.
  • Hiding is not securing. A hidden group can still receive mail from senders who know the address, depending on its delivery settings. Review delivery restrictions if that matters.
  • Update 2026: check your Exchange version. Exchange Server 2016 and 2019 reached end of support on 14 October 2025.
  • Microsoft recommends moving to Exchange Online or Exchange Server Subscription Edition (SE).
  • For hybrid management, use Exchange SE or the Exchange SE Management Tools. These are supported on Windows Server 2019–2025 and Windows 10/11 (64-bit).
  • Exchange 2013 and earlier must be removed before upgrading.
  • If you need outside help planning that move, my company, Standing, provides IT services and managed services in Iraq and the Kurdistan Region.
  • Check for cloud options. Microsoft has been working on ways to manage synced objects from the cloud. Check the current Entra and Exchange documentation before you assume on-premises is the only route.

Quick checklist

Step Where Done
Back up current group attributes On-premises AD ☐
Set msExchHideFromAddressLists = True (or run cmdlet on-prem) ADUC / Exchange SE shell ☐
Confirm mailNickname is populated ADUC ☐
Run delta sync Entra Connect server ☐
Verify with Get-DistributionGroup Exchange Online PowerShell ☐

The takeaway: when Microsoft 365 says an object is synchronised from on-premises, stop editing in the cloud. Change it where it lives, in Active Directory or on-premises Exchange, then let the sync carry it across.

Sources & further reading

  1. Microsoft Learn: Mail-enabled security group isn't hidden from GAL after directory synchronization in a hybrid deploymentlearn.microsoft.com
  2. Microsoft Learn: Set-DistributionGrouplearn.microsoft.com
  3. Microsoft Learn: Attributes synchronized by Microsoft Entra Connectlearn.microsoft.com
  4. Microsoft Learn: Exchange Server supportability matrixlearn.microsoft.com
  5. Microsoft Exchange Team Blog: T-1 month: Exchange Server 2016 and 2019 End of Supporttechcommunity.microsoft.com
  6. Microsoft Q&A: Hidden from GAL changes not reflecting in Exchangelearn.microsoft.com

📝 First written from my own work in 2018; updated and expanded in November 2026 with AI assistance, keeping my original fix. Spotted something wrong? Tell me.

Akam Omer
Written by

Akam Omer

IT leader, engineer and security specialist from Erbil with 20+ years across higher education, telecoms, healthcare and government. Founder of BulkSMSIraq, VerifyWay and Kurd.ai.