Convert Shared Mailbox to Office 365 Group
There should be an option to convert a shared mailbox to an office 365 group especially since the Office 365 Group is the newer better version of the Shared mailbox and there is no way to convert.
Thanks to all of you for your feedback on this item. We’ve taken note that interest in this particular request has increased. Please continue to provide your feedback as we assess the priority in relation to other initiatives the teams have committed. Thank you!
YES! converting a shared mailbox to microsoft 365 group would be of great help
Kathy Wade commented
We use both O365 Groups and Shared Mailboxes. If the business need requires mail folders to separate out the e-mails by content, then we have to use a Shared Mailbox. If the business need requires mail rules, we use a Shared Mailbox. If the business need is to categorize messages or calendar items, we use Shared Mailboxes. If mail needs to connect to PowerApps, we use Shared Mailboxes. It would be great to have all of those features in Groups so we can take advantage of the Group features as well.
Scenario: Users wants to create Teams meetings on a "Shared" mailbox calendar and have it include the Teams conference dial in as well as the ability to invite a participant to a meeting that's already in progress by dialing a phone number. This works if the meeting invite is created from the users personal calendar or an O365 "Group" calendar but not on a "Shared" calendar. There are 100's of "Shared" mailboxes. It would be very helpful if I could "convert" them to an Office 365 Group.
Chris Gunarich commented
Agreed. I am having issues with shared emails disappearing from favorites so it may work better in a group. Not to mention having multiple variations of groups, etc. gets confusing. Simple is better. Thanks. Chris
Jay Galt commented
YES! converting a shared mailbox to microsoft 365 group would be of great help.
We use shared mailboxes to allow each team to reply to external client emails. The issue with shared mailboxes is that sometimes a member of our team will accidentally mark an email as read or delete an email and we have no way of knowing who it was. Groups is a much better option when it comes to accountability.
Fred Ottenhof commented
unclear now relation between Teams-groups, Office 365-groups and shared mailboxes.
Louis Lam commented
In order to provide seamless service to our customer, we need to act and response unitedly as one team (with one email address). So shared Mailbox is what we need!! Hope you will have this function soon. Thanks.
We need using Groups for sales and technical employees with shared Mailbox. In the shared Mailbox it should be possible to create folder and also should the delete items not be at the user folder...
Carl Gloess commented
I have a Team for giving awards to people and the Teams structure is useful for storing supporting documents etc and they each get any e-mails sent to the team e-maila ddress. They however want to remain anonymous and the Shared Mailbox allows that but it means though that they have to have yet another email set up to be able to do that.
Scott Wood commented
We need to be able to create a shared folder hierarchy within a group sort of like a licensed user or shared mailbox - where all the other group members see the same message read status and folders. That's really the last thing Groups need that would take over our separate licensed IMAP users and Shared Folders.
We really don't understand why the limitations between licensed mailboxes, shared folders, and groups exist.
A licensed Exchange user gets us a full email account with its own username / password login. Great. That's where we started, but with 2FA and modern authentication, this becomes unmanageable pretty quick and the cost is higher.
A Shared Mailbox is just like an IMAP mailbox but users with access don't have to manage a separate username and password. Great! Problem solved. But now we lose the ability to show multiple accounts inbox in the same feed (because for some reason Outlook in their infinite wisdom doesn't consider a shared mailbox to be a separate account otherwise it could do this, and without a separate login or native Exchange support, third party programs that can do this won't work)... so solving one problem creates another.
A Group is perfect for this shared collaboration as it gives us SharePoint and Teams and other useful things to help organize and stay on top of communication, and gives us access to the email sent to the group right within our own accounts without having to switch accounts or manually check a different folder hierarchy. Best of all worlds! Problem solved. But... now we can't organize any group emails in a way others can see, we can't see if someone else has read or responded, so now we can collaborate on files and messaging and have great email visibility but lose the ability entirely to collaborate with email. Solve one problem, create another.
So when getting started with this, it's pretty hard to figure out what type of account to create based on what things users need to do. It's hard to explain to users what they can and can't do, and why there are three different non-overlapping sets of features for these setups. It's not good / better / best, it's this but not that, these more but lose this other thing, do everything excep this important thing. Confusing and disjointed. We still don't have what we need and have to train people on workarounds that nobody understands why they are necessary.
Obaid Islam commented
Support functions and mail boxes are usually manned by multiple people to ensure prompt query response. Having the ability to "Group" it makes life and business easy.
This is DEFINITELY a requirement for support staff to send On Behalf of mails on generic Email ID.
Yes, we should be able to convert from shared mailbox to O365 group. However, we need to be able to create a folder structure or a simple method to move the emails to folders in the sharepoint site.
We use a shared mailbox to capture fax, scans, and emails. Since the response time is critical, the mailbox is shared and monitored by several people in the service/support group. I vote to convert shared mailbox to office 365 group to allow better manage the requests.
We work exclusively with shared mailboxes. This feature should be integreated
We need to encrypt outgoing messages from a shared mailbox because as a health organization we are communicating with our patients and the information is sensitive. A shared mailbox ends up showing the individual's email address the email who sent the message, during the process of encrypting, even though they sent it from the shared mailbox.
I vote for this. O365 Groups being a new feature it should allow conversion from shared mailboxes to make it easy to transition to the new features.