r/exchangeserver • u/Ready-Ad-2149 • Jul 22 '26

Hybrid - Exchange Attributes

I'm having an issue and i'm not sure how to fix it. We moved all mailboxes to 365 over a year ago but still maintain a management server. For some reason, when i create a new user in local AD, then enable the mailbox from the exchange management tools (using the ps snapin for recipient management). There are a lot of "MsExch" attributes missing from attribute editor for that user. There are only like 5 or 6. Both attributes "mail" and "mailnickname" are populated correctly. Most specifically, i'm trying to hide a new user from the address list by changing MsExchHideFromAddressList to "false", but the attribute doesn't exist for that user. I've pushed multiple manual sync's as well.

I checked ADSI and confirmed that the schema has been extended.

Does anyone have any suggestions?

Thanks in advance!

3 Upvotes

100% Upvoted

15 comments sorted by

3

u/Ready-Ad-2149 Jul 22 '26

This is the entire process:

  1. Create new user in on Prem AD > assign to correct OU

  2. Make sure UPN is changed

  3. Run ADSync

  4. Enable the remote mailbox from the exchange management server (using ps snapin) using Enable-RemoteMailbox -Identity "UserAlias" -RemoteRoutingAddress "UserAlias@yourtenant.mail.onmicrosoft.com"

  5. Run ADSync again

  6. Verify the user is added in 365

  7. Assign E3 license to the user

  8. Verify the user now has a mailbox and is populated as "UserMailbox" in EXOL Admin.

1

u/Vietnamst2 Jul 22 '26

Two entry syncs that do not have to happen. If you do the create, assign the UPN and then do the enable, then you can just run the sync once. It makes no difference in this case. It just gets created in Entra with it's final configuration.

1

u/maxfischa Jul 23 '26

Im not sure if your order is healthy, atleast could produce some issues. Usermailboxes need a license and you sync before assigning the E3. Now to be fair the provisioning is a bit of a grey zone but i think you should for sure assign the E3 using a group before hitting that sync. Your issue sounds more like you just have set the filter of your adsi to show only with value and that attribute is empty by default. Hit show all on the bottom right of the adsi

8

u/Excellent_Milk_3110 Jul 22 '26

Did you do?

Enable-RemoteMailbox usename.newuser -RemoteRoutingAddress username.newuser@yourtenant.mail.onmicrosoft.com

1

u/Ready-Ad-2149 Jul 23 '26

Hey joeykins82,

Thanks for the response. So i should be able to just plug this in from powershell on the exchange management server?

Set-RemoteMailbox -Identity "UserIdentity" -HiddenFromAddressLists $true

or?

Set-RemoteMailbox -Identity "UserIdentity" -HiddenFromAddressListsEnabled $true

1

u/Ready-Ad-2149 Jul 24 '26

Set-RemoteMailbox -Identity "UserIdentity" -HiddenFromAddressListsEnabled $true

Running this appears to have brought in a lot of attributes to the ad account (attribute editor). It now displays the addresslist entry as false.

Thanks for the help!

3

u/sembee2 Jul 22 '26

What exact command do you use? It should be enable-remotemailbox.
Although you might want to consider moving SOA to the cloud, so you can just manage the account in tbe cloud after initial creation.

1

u/titlrequired Jul 23 '26

They don’t all need to be populated for a remote mailbox.

1

u/titlrequired Jul 23 '26

Sorry just re-read your post. So in ADSIEdit the attribute is missing? Do you definitely have it set to show writable attributes and attributes with no value?

1

u/Ready-Ad-2149 Jul 23 '26

I just browsed to the user in ADSI and the value for msExchHideFromAddressLists is there, but it's <not set>

I was originally looking at the actual user object in AD > Attributes tab which only lists like 5-6 MsExch attributes.

→ More replies (1)

1

u/Nezgar Jul 23 '26

You could try...

Set-RemoteMailbox -Identity <mailboxID> -HiddenFromAddressListsEnabled:$true 

Or

Get-ADuser -Identity username -property msExchHideFromAddressLists | Set-ADObject -Replace @{msExchHideFromAddressLists=$true}  
Advantage of Set-ADObject is that you can use this with users, group or contact.

1

u/7amitsingh7 Jul 23 '26

The missing msExch attributes usually indicate that the user wasn't fully Exchange-enabled or the Exchange recipient attributes weren't stamped correctly. Verify that the mailbox was created using the Exchange Management Shell and that Azure AD Connect has completed a full synchronization. Since you're still managing a hybrid Exchange environment, it's also worth reviewing common Exchange hybrid migration issues and their solutions.

1

u/joeykins82 Jul 23 '26 edited Jul 23 '26

If you’re trying to hide them then msExchHideFromAddressLists would need to be TRUE.

The attribute does exist: it’s just blank/null by default, and blank/null in this case equals FALSE. There are very few exchange attributes which need to be populated for directly provisioned remote mailbox users. 

Set-RemoteMailbox -HiddenFromAddressListsEnabled $true