EXO: Shared Mailbox with Active AD account

%3CLINGO-SUB%20id%3D%22lingo-sub-922108%22%20slang%3D%22en-US%22%3EEXO%3A%20Shared%20Mailbox%20with%20Active%20AD%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-922108%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20migrating%20our%20Ex2010%20mailboxes%20to%20Exchange%20Online.%3C%2FP%3E%3CP%3ECurrently%2C%20we%20have%20shared%20mailboxes%20created%20with%20an%20Active%20AD%20login%20account%20(Generic%20login)%20for%20application%20integration%20purposes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20will%20happen%20to%20these%20shared%20mailbox%20(with%20active%20AD)%20if%20we%20do%20not%20assign%20O365%20license%20to%20them%20post%20migration%3F%3C%2FP%3E%3CP%3EWill%20application%20continue%20to%20be%20able%20to%20login%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnderstand%20that%3A%20Shared%20mailbox%20do%20not%20require%20an%20license.%20It%20should%20not%20be%20used%20for%20login.%3C%2FP%3E%3CP%3EBut%20we%20need%20to%20understand%20the%20impact%20to%20our%20applications%20and%20if%20anything%20need%20to%20be%20done%20before%20migration%3F%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-922108%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-922541%22%20slang%3D%22en-US%22%3ERe%3A%20EXO%3A%20Shared%20Mailbox%20with%20Active%20AD%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-922541%22%20slang%3D%22en-US%22%3E%3CP%3EThere's%20nothing%20in%20the%20code%20stopping%20you%20from%20logging%20in%20directly%20to%20a%20Shared%20mailbox%2C%20it%20has%20been%20actually%20discussed%20few%20times%20here.%20However%20it's%20against%20the%20license%20agreement%2C%20and%20you%20should%20use%20it%20at%20your%20own%20risk.%20Best%20assign%20a%20license%20to%20the%20mailbox%20and%20covert%20it%20to%20regular%20one.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-925982%22%20slang%3D%22en-US%22%3ERe%3A%20EXO%3A%20Shared%20Mailbox%20with%20Active%20AD%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-925982%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%3C%2FP%3E%3CP%3EQuestion%3A%20you%20mentioned%20convert%20to%20%22regular%22%20one%20%3D%20Does%20that%20mean%20Microsoft%20recommended%20Shared%20mailbox%20to%20be%20created%20as%20UserMailbox%20type%20in%20EXO%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20about%20assign%20O365%20to%20SharedMailbox%20type%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-926078%22%20slang%3D%22en-US%22%3ERe%3A%20EXO%3A%20Shared%20Mailbox%20with%20Active%20AD%20account%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-926078%22%20slang%3D%22en-US%22%3E%3CP%3ENo%2C%20it%20simple%20means%20you%20can%20convert%20between%20the%20different%20mailbox%20types%20with%20no%20issues%2C%20as%20long%20as%20you%20keep%20true%20to%20the%20license%20agreement.%20You%20can%20assign%20a%20license%20to%20a%20shared%20mailbox%20as%20well%2C%20but%20if%20you%20do%20that%2C%20you%20can%20simply%20convert%20it%20to%20user%20mailbox%20as%20you%20are%20allocating%20the%20license%20anyway.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi,

 

We are migrating our Ex2010 mailboxes to Exchange Online.

Currently, we have shared mailboxes created with an Active AD login account (Generic login) for application integration purposes.

 

What will happen to these shared mailbox (with active AD) if we do not assign O365 license to them post migration?

Will application continue to be able to login?

 

Understand that: Shared mailbox do not require an license. It should not be used for login.

But we need to understand the impact to our applications and if anything need to be done before migration?

Thanks

3 Replies
Highlighted

There's nothing in the code stopping you from logging in directly to a Shared mailbox, it has been actually discussed few times here. However it's against the license agreement, and you should use it at your own risk. Best assign a license to the mailbox and covert it to regular one.

Highlighted

Hi @Vasil Michev 

 

Thank

Question: you mentioned convert to "regular" one = Does that mean Microsoft recommended Shared mailbox to be created as UserMailbox type in EXO?

 

What about assign O365 to SharedMailbox type? 

 

Thank you

Highlighted

No, it simple means you can convert between the different mailbox types with no issues, as long as you keep true to the license agreement. You can assign a license to a shared mailbox as well, but if you do that, you can simply convert it to user mailbox as you are allocating the license anyway.