This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 67%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
Hi Team,
We have noticed that when a user is created on on-premise AD but it's corresponding mailbox is created on O365 using Enable-RemoteMailbox cmdlet, certain AD attributes, for instance, "homemdb" and "msExchELCMailboxFlags" do not exist for this particular user. Checked this using below command:
Get-ADUser -Filter {userprincipalname -eq '<user_identity>'} -properties homemdb, msExchELCMailboxFlags
We wanted to know if this is expected, if so, are there any alternate attributes for a mailbox created on O365?
Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 22%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELL%3C/text%3E%3C/svg%3E)
Hi @ExUser44 ,
Based on my knowledge and testing, this is expected behavior. When you migrate on-premises mailbox to Exchange online or create a remote mailbox for an AD account. Some attributes in AD will be changed. For example, the attributes "homeMDB" you mentioned, represents the proper noun of the database where the mailbox is located. These attributes have no practical meaning for O365 mailboxes, so they will be changed automatically, but these changes will not have any impact on your use.
There are also some attributes that will be changed: AD Attributes Changed When an On-Premises User Mailbox is Moved to EXO
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
----------
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thanks @Andy David - MVP and @Lucas Liu-MSFT
We actually wanted to know if there is any alternate attribute that would give us ELC flag values.
Currently in our code(for On-prem), we are specifically checking for attribute "msExchELCMailboxFlags". This code fails when we test with AD synced user, hence wanted to know if alternate attribute for ELC flags exists.
Thanks!
Can you change the code? :)
Seems like checking the recipient type makes more sense.
@Andy David - MVP , yes we can change our code.
But just had a query, if we use recipient type check, it will only return recipient/mailbox type. Please correct me if I'm wrong here.
In our existing code, with the "msExchELCMailboxFlags" attribute(treating it as a bitmap), we are checking if Single Item Recovery and Litigation Hold flags are enabled for a mailbox.
Please help me understand how we could use recipient type attributes to check if Single Item Recovery and Litigation Hold flags are enabled.
Thanks!
Hi @ExUser44 ,
According to my research, there is no attribute that can completely replace "msExchELCMailboxFlags". And according to my understanding, the recipient type cannot be used to determine whether a specific mailbox has Single Item Recovery and Litigation Hold enabled.
Have you considered running a command line similar to the following to get a mailbox with Litigation Hold or Single Item Recovery enabled?
Get-mailbox | where {$_.LitigationHoldEnabled -like "$True"} | ft Name,LitigationHoldEnabled
Get-mailbox | where {$_.SingleItemRecoveryEnabled -like "$True"} | ft Name,SingleItemRecoveryEnabled
----------
If the response is helpful, please click "Accept Answer" and upvote it.
In that case, you should connect to Exchange Online instead and query for those attributes :)