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(310.4, 76%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
We have a couple mailboxes that have a M365 E3 license on them, that are shared that were set up before I joined the company, and the people that set them up are long gone. We are going through working at migrating to Azure from AD which means we need to implement the policies that were in AD in Intune and such, and it is preferred if we could just free up an E3 license.
Is there any type of scenario that would require licensing a mailbox that is just shared between people with an E3 license instead of an Exchange Online Plan 1 or 2?
![](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(73.60000000000001, 94%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELM%3C/text%3E%3C/svg%3E)
Hi,
I'm here to confirm that is there any progress with the issue? If the reply helps, you could mark it as an answer to close the thread.
Thank you!
Is it helpful yes, and thanks for the reply @Andy David - MVP but it doesn't answer my initial question.
Hi,
I am writing to see how everything is going on with this thread. If the following suggestion helps, please click “Accept as answer” to mark helpful reply. Your action would be helpful to other users who encounter the same issue and read this thread.
A shared mailbox in ExO does not require any license except for a few exceptions. Unless that shared mailbox meets those scenarios, you can disable the associated account and remove the licenses all together
Hi, Sorry, I guess what I am saying is that M365 E3 would never be required for a shared mailbox simply because its a disabled account and that SKU is really designed for an actual user accessing 365/Azure workloads, not a shared mailbox. Hope that helps.
It does, I was just wanting to make sure there wouldn't be something that would be needing the E3 capability in a shared mailbox before changing it to an Exchange Online license or just pure shared account.
I have never seen a reason to add an E3/E5 to any shared mailbox. Only active users :)