shared mailbox showing as disabled, but is enabled?

Exchange shared mailbox is showing:  ExchangeUserAccountControl : AccountDisabled

It was migrated from exchange 2010 to exchange online.  I have a hybrid env. using dirsync/adconnect.  

It was shared prior to being migrated - and the user account associated is ENABLED.

Anyone ever seen this before?  I believe this is showing that the account is enabled, but that attribute is showing it "ExchangeUserAccountControl" creating a false positive on licensing reports.

Is there anyway to correct set this attribute?

Thanks Experts!
Ron ShortsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andy MIT Systems ManagerCommented:
A shared mailbox should show the associated AD user account as disabled (you can't directly access a shared mailbox - it has to be done through delegated access to user mailboxes). If you try to enable the AD account you're effectively trying to change it back into a user mailbox that requires an Office 365 license. A shared mailbox doesn't require an Office 365 license.
Ron ShortsAuthor Commented:
@Andy M - thanks for your reply.  

The shared mailbox AD account was disabled at some point, probably when it was created, but someone must have enabled it... and I'm unsure if the account to the shared mailbox is being used or not to disable it.  

There are others like this (shared mailbox with AD account ENABLED), but I noticed the attribute to these:  "ExchangeUserAccountControl" is set to "none" whereas this one is set to "AccountDisabled"

This shows up as needing a license reconciliation when I run this command:

get-msoluser -LicenseReconciliationNeededOnly -enabledfilter enabledonly |select-object userprincipalname, blockcredential, msexchrecipienttypedetails, licenses

What I'm unsure of, whether or not the "ExchangeUserAccountControl" is giving a "false positive" so to speak and the attributes are a little screwed up, and if this shared mailbox isn't licensed will go to the recycle bin after 30 days.

The intent is to not license shared mailboxes.

Thanks again!
Andy MIT Systems ManagerCommented:
Hmm, not sure why it is showing like that but I believe it should be set to None. Had a quick look about online and a lot of people say it's sometimes caused by either hiding a mailbox from the Exchange GAL or possible AD Sync.

Have a look at the following suggestions (some of them state Exchange 2010, 2013 but may still be relevant):
Vasil Michev (MVP)Commented:
Things work a bit differently in Exchange Online/Office 365. In a nutshell, you can actually enable a shared mailbox account for a direct login, however this is in no way supported by Microsoft and it's in violation of the license agreement. Regardless, Microsoft will not delete any such mailboxes, as they only enforce licensing requirements in some specific scenarios. TL;DR you can ignore this.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.