Shared mailboxes such as [email protected], [email protected], [email protected] and [email protected] are indispensable for many organizations. For years, however, Outlook mainly treated these mailboxes as an extra folder under a user’s personal account.
That worked well enough for reading and replying to messages, but as soon as you wanted to configure anything more serious, things became awkward. Managing categories, creating rules, receiving notifications, setting automatic replies, or making sure new emails were sent from the shared address by default: many of these functions were limited, hidden in unintuitive places, or simply unavailable.
In the new Outlook, a shared mailbox can now be converted or promoted into a full account inside Outlook. That may sound like a small change, but for users and IT administrators it is a major improvement.1
This change is not brand new. Microsoft has had this capability in the new Outlook for a while, but as often happens with Microsoft 365 features, it only really stands out when you run into a concrete problem. In this case, it started with something seemingly small: managing categories in a shared mailbox. What first looked like another typical Outlook administration nuisance suddenly turned out to have a much cleaner solution.
The old problem: access, but not a real account
When an administrator granted a user full access to a shared mailbox, that mailbox usually appeared automatically in Outlook. This is called automapping.
The user would see, for example:
- their own account, such as
[email protected]; - below that, the shared mailbox
[email protected].
The mailbox was accessible, but Outlook did not treat it as an independent account context. That led to all kinds of odd limitations.
A user could apply a category to a message inside the shared mailbox, but when managing or deleting categories, Outlook would show the categories from the personal mailbox instead. Rules and automatic replies often had to be configured through Outlook on the web or by an administrator. New-message notifications were inconsistent, and when composing a new email the user often had to manually select the correct address in the From field.
For users, that was confusing. For administrators, it created recurring support questions and fragile workarounds.
The old administrator workaround
Previously, if you wanted to use a shared mailbox as a separate account in classic Outlook, you had to take a fairly cumbersome route:
- Remove the existing Full Access permission.
- Grant Full Access again with
AutoMapping $false. - Wait until Outlook removed the automatically mapped mailbox.
- Add the shared mailbox manually as an extra Exchange account.
- During sign-in, use the personal user account rather than the shared mailbox itself.
Microsoft still documents this method for classic Outlook. The automatically mapped mailbox must first be removed, or automapping must be disabled, before the same mailbox is added as an extra account.2
Technically, it worked. For day-to-day administration, it was far from ideal. You needed Exchange Online PowerShell, changes were not always visible immediately, and a wrongly configured mailbox could appear twice in Outlook.
For one mailbox, that was still manageable. For dozens of users and multiple shared mailboxes, it quickly became a small administration project.
The new solution: Convert or Promote
In the new Outlook, this can now be done directly from the settings:
Settings → Accounts → Shared with me
There you see the mailboxes to which you have access. Depending on how the mailbox was previously added, Outlook shows one of these options:
- Convert for an automatically mapped mailbox;
- Promote for a shared mailbox that was previously added manually;
- Add when the mailbox is not yet in Outlook.
After conversion, the shared mailbox appears under Your accounts, just like other accounts in Outlook. The user does need the Full Access permission for this.1
The important difference is that, for an already automatically added mailbox, the administrator does not first have to disable automapping. No removing and re-adding mailbox permissions, no AutoMapping $false, no manual Exchange-account construction, and much less risk of duplicate mailbox entries.
The shared mailbox finally gets its own settings
Once the mailbox has been added as an account, it appears in the account selector for supported Outlook settings.
Users can then manage settings specifically for the shared mailbox, including:
- categories;
- notifications;
- inbox rules;
- automatic replies;
- junk email;
- forwarding;
- quick steps;
- conditional formatting;
- Focused Inbox;
- retention policies.
Microsoft also mentions support for features such as unread counts, message formatting and attachment preferences.3
This solves exactly the situation where a user could apply categories inside a shared mailbox, but ended up editing the categories of the personal mailbox. The shared mailbox now has its own account context and therefore its own settings environment.
Better synchronization and notifications
Synchronization also improves.
Microsoft states that shared mailboxes added only through automapping in the new Outlook may not always synchronize automatically. In that case, the user may need to open the folder or synchronize manually to see new messages.4
When the shared mailbox is added as an account, it can synchronize automatically and receive its own notifications.4
For a mailbox such as support@ or info@, that is not a small detail. A missed message can directly mean that a customer waits longer for a response.
New emails finally start from the right address
Perhaps the most pleasant improvement is in sending email.
A shared mailbox that is only attached as a folder does not always feel like a real sending account in Outlook. When replying to a received message, Outlook usually uses the shared address, but when composing a completely new message it may still select the personal account as the sender. The user then has to check each time whether the From field really says [email protected].
That is not only annoying, but also error-prone. One moment of inattention and a business email is sent from an employee’s personal address.
After promotion, the shared mailbox is listed as an account in Outlook. It then participates in the normal account and sender selection. Outlook shows which account is being used in the From field, and users can switch between available accounts there.5
In practice, a full account sends much more logically from its own account context. That is exactly what you expect from an account, but for shared mailboxes it was not self-evident for years.
For someone who mainly works from info@, administration@ or sales@, this is a major improvement. New messages can be composed from the shared company address more naturally, without correcting the sender manually each time.
This is especially useful for reception desks, service desks, sales teams and administrative departments.
One important note: besides Full Access, the user also needs Send As or Send on behalf permission to actually send as the shared mailbox. Full Access alone does not grant sending rights.6
Fewer mistakes and less administration
The value is not just in extra features. The whole setup becomes easier to understand.
Before:
The shared mailbox sits under my account, but some settings belong to me and others belong to the mailbox. For new messages I have to check which address I am sending from.
Now:
This is my personal account, and this is the shared account. Both have their own folders, settings, notifications, rules and sending context.
For users, that is much more logical. For IT administrators, it means less PowerShell work, fewer special Outlook profiles and fewer support questions such as:
- Why can’t I remove this category?
- Why don’t I get a notification for new email?
- Why does my rule only work in my own mailbox?
- Why was this message sent from my personal address?
- Why can’t I change the automatic reply for the shared mailbox?
The mailbox is still technically a shared mailbox
The phrase full account can make it sound as if the shared mailbox is converted into a normal licensed user mailbox. That is not what happens.
In Microsoft 365, the mailbox remains a shared mailbox. Users do not sign in directly with the password of [email protected]; they use their own account and their own multifactor authentication. Microsoft recommends that the account behind a shared mailbox remains disabled for direct sign-in.7
From a security perspective, that is good news: every employee continues to work with their own identity, while Outlook can still treat the shared mailbox as an account.
Not everything is solved yet
This feature is a big step forward, but support is not yet fully equal to that of a regular user mailbox.
Microsoft still lists limitations around, among other things:
- contacts;
- tasks;
- notes;
- archive folders;
- some add-ins;
- searching calendar items.
The option may also be missing in some versions of the new Outlook, because Microsoft rolls out new Microsoft 365 features gradually.1
The feature specifically applies to the new Outlook for Windows. In classic Outlook, adding a shared mailbox as a separate account still relies on the older manual method for now.
A small button with a big impact
At first glance, the Convert button may look like a minor detail. In reality, it solves a long-standing problem in the way Outlook handles shared mailboxes.
A shared mailbox is no longer merely a folder that happens to sit under a personal account. It can now function as a recognizable account context with its own categories, rules, notifications, automatic replies and sending settings.
For users, this means more options and fewer mistakes. For administrators, it means fewer exceptions, fewer scripts and significantly simpler support.
Sometimes the best Microsoft 365 improvements are not the features with the biggest marketing campaign. Sometimes it is just one button that finally solves a management problem that has been around for years.
And honestly: this one is very welcome.
Need help with Microsoft 365?
Would you like to know whether your Microsoft 365 environment can be configured in a smarter, safer or more user-friendly way? Feel free to contact Forcys. We are happy to think along about a workplace that is technically well managed and also makes sense in daily use.
Sources
- Microsoft Support, “Manage shared mailbox settings in new Outlook”: https://support.microsoft.com/en-us/outlook/sharing/manage-shared-mailbox-settings-in-new-outlook
- Microsoft Learn, “Add a shared mailbox as an additional account in Outlook Desktop”: https://learn.microsoft.com/en-us/microsoft-365-apps/outlook/profiles-and-accounts/add-shared-mailbox-as-additional-account
- Microsoft Support, “Open and use a shared mailbox in Outlook”: https://support.microsoft.com/en-us/outlook/sharing/open-and-use-a-shared-mailbox-in-outlook
- Microsoft Support, “Sync a shared mailbox in new Outlook”: https://support.microsoft.com/en-us/outlook/sharing/sync-a-shared-mailbox-in-new-outlook
- Microsoft Support, “Create an email message in Outlook”: https://support.microsoft.com/en-au/office/create-an-email-message-in-outlook-147208af-ca8e-4cdf-b71f-77ba81a54069
- Microsoft Learn, “Shared mailboxes in Exchange Online”: https://learn.microsoft.com/en-us/exchange/collaboration-exo/shared-mailboxes
- Microsoft Support, “Open and use a shared mailbox in Outlook”: https://support.microsoft.com/en-us/outlook/sharing/open-and-use-a-shared-mailbox-in-outlook