PowerShell: Add a Shared Mailbox to Outlook

To make a shared mailbox available in Outlook, use Exchange Online PowerShell to grant the user Full Access; Outlook can then add it automatically if automapping is enabled. PowerShell grants access on the Exchange side—it does not directly edit a particular Outlook profile—so you may need to add the mailbox manually in Outlook or wait for its folder list to update.

What the PowerShell command does

A shared mailbox is hosted in Exchange, while Outlook is the client used to open it. The administrator assigns mailbox permissions in Exchange; Outlook discovers and displays the mailbox based on those permissions and its account configuration. This distinction matters because running a command cannot force every Outlook app or device to show the mailbox immediately.

The essential permission is Full Access. It lets the named user open the mailbox and work with its folders and messages. It does not, by itself, allow the user to send messages as the shared mailbox or on its behalf. Those are separate permissions.

The commands below are for Exchange Online in Microsoft 365, which is the common setup for organizational mail. They assume that the shared mailbox and user are in the same Microsoft 365 tenant. For on-premises Exchange or a hybrid environment, use the Exchange management tools and procedures appropriate to that deployment.

Check prerequisites and identify the accounts

Before changing permissions, confirm the shared mailbox’s primary email address and the user’s sign-in address. A typo can grant access to the wrong recipient or make a successful change appear ineffective. You also need an account with an Exchange role that permits mailbox-permission changes; use an appropriately scoped Exchange administrator role rather than elevating an account more broadly than necessary.

Confirm that the recipient is a shared mailbox, not a distribution list or Microsoft 365 group.
Confirm the user has a working organizational account and mailbox access through the tenant.
Ask whether the user needs to read and manage mail, send as the mailbox, or both.
Check whether the user already has access, including permissions assigned through a group.

Full Access is a powerful permission: it exposes the mailbox’s contents, including messages and folders. Grant it only to people who need that access, and follow your organization’s approval and data-handling rules.

Connect to Exchange Online PowerShell

On a Windows computer with PowerShell, install Microsoft’s Exchange Online management module if it is not already installed. Then import the module and connect using an authorized administrator account. Modern authentication supports multifactor authentication through the sign-in flow.

Install-Module -Name ExchangeOnlineManagement -Scope CurrentUser
Import-Module ExchangeOnlineManagement
Connect-ExchangeOnline -UserPrincipalName admin@contoso.com

Replace the example address with the administrator’s sign-in address. If the module is already installed, you can skip the installation command. Depending on your organization’s PowerShell policy, installation may prompt you to approve the repository or module. When the connection succeeds, Exchange Online cmdlets are available in that PowerShell session.

When finished, close the remote session with Disconnect-ExchangeOnline. This is especially useful on a shared administration computer. A session that has been disconnected cannot run Exchange commands until you connect again.

Grant Full Access and allow automapping

Run Add-MailboxPermission with the shared mailbox as Identity and the person as User. Full Access is the permission Outlook needs to open and manage the mailbox. The standard command enables automapping by default for a direct user assignment.

Add-MailboxPermission -Identity shared@contoso.com -User alex@contoso.com -AccessRights FullAccess -InheritanceType All

Replace both addresses with the real mailbox and user. The command adds permission; it does not create a mailbox or convert a user mailbox into a shared mailbox. If the account already has the same permission, Exchange may report that it is already assigned. Check the existing permissions before treating that message as a failure.

Automapping is Exchange’s mechanism for making a mailbox appear in supported Outlook desktop configurations after a user receives Full Access directly. It is not a universal switch that inserts the mailbox into every Outlook app. In particular, assigning Full Access to a group does not provide the same per-user automapping behavior as granting it directly to each person.

Choose automapping or manual setup

Use the default behavior when the user wants the mailbox to appear alongside their own mailbox in a supported Outlook for Windows configuration. If you prefer that the user add it manually, disable automapping when granting access:

Add-MailboxPermission -Identity shared@contoso.com -User alex@contoso.com -AccessRights FullAccess -InheritanceType All -AutoMapping $false

Manual addition can be useful when a person has many shared mailboxes, wants a particular mailbox available only in one client, or is using an app where automapping is not supported or does not apply. Automapping is associated with the permission assignment, so changing an existing assignment’s behavior generally involves removing the direct Full Access permission and adding it again with the desired setting. Plan that change with the user, since it can temporarily affect access.

Automapping is not the same as adding an Outlook account. The shared mailbox normally opens through the user’s own Exchange account and does not need its own sign-in by the user. Avoid asking people to sign in as the shared mailbox; shared mailboxes are intended to be accessed by authorized users through their own accounts.

Add the mailbox in Outlook when it does not appear

First allow time for Exchange permission changes and Outlook’s mailbox discovery to take effect. The delay varies; restarting Outlook or signing out and back in can prompt the client to refresh, but it does not guarantee an immediate update. If the mailbox still is not listed, confirm Full Access and add it manually in the appropriate client.

In classic Outlook for Windows, open File > Account Settings > Account Settings, select the user’s Exchange account, and choose Change > More Settings > Advanced > Add. Enter the shared mailbox name or address, confirm the dialogs, and restart Outlook if prompted. These steps add the mailbox to that Outlook profile; they do not grant Exchange permission, so the user must already have Full Access.

Outlook on the web offers a separate route: in the folder pane, right-click Folders and choose Add shared folder or mailbox, then enter the mailbox address. In newer Outlook versions, labels and locations can differ as Microsoft updates the interface. For Outlook for Mac, use its shared-mailbox or shared-folder option and sign in with the user’s own account; do not assume that Windows automapping instructions apply identically. If the mailbox is missing from an app, manual addition is often the clearest way to distinguish a client-discovery issue from a permission issue.

Grant Send As or Send on Behalf separately

Full Access permits opening the mailbox, but it does not authorize sending as it. For messages that should appear to come directly from the shared address, grant Send As separately:

Add-RecipientPermission -Identity shared@contoso.com -Trustee alex@contoso.com -AccessRights SendAs

For Send As, the recipient sees the shared mailbox as the sender. Send on Behalf is a different permission: the message identifies the user as sending on behalf of the shared mailbox. Choose the permission that matches the organization’s mail-handling requirements, and allow for permission propagation before testing. The user may need to select the shared address in Outlook’s From field.

Verify access and troubleshoot common problems

Use Exchange Online PowerShell to inspect the mailbox’s permissions. The first command lists Full Access entries; review the User and AccessRights columns for the intended person. The second checks Send As entries when that permission was requested.

Get-MailboxPermission -Identity shared@contoso.com | Format-Table User,AccessRights,IsInherited,Deny -AutoSize
Get-RecipientPermission -Identity shared@contoso.com

If Outlook cannot open the mailbox or it does not appear, check these common causes:

Wrong recipient: Verify that the permission was applied to the user’s correct account and the correct shared mailbox.
Permission not propagated: Allow time, restart the client, and test Outlook on the web to see whether access works there.
Only Send As was granted: Sending permission does not replace Full Access for opening folders and reading messages.
Group-based assignment: A group may grant access but not trigger automapping. Add the user directly if automatic appearance is needed and policy permits it.
Outlook profile issue: If permission checks are correct, try manual addition or test with another supported client before rebuilding a profile.
Cached or stale entry: Outlook may retain old mailbox data temporarily. Do not remove or recreate accounts until the mailbox permission and user’s primary account have been checked.

To remove a direct Full Access assignment when access is no longer required, use Remove-MailboxPermission with the same mailbox and user identities, and confirm the permission being removed. Removing access does not necessarily erase previously downloaded or exported information, so revocation should follow the organization’s security process.

Licensing and security considerations

A shared mailbox generally does not require its own license when it remains within Microsoft’s standard shared-mailbox size limit, but licensing can be required for larger mailboxes and certain features, such as an archive or litigation hold. The people accessing it need their own eligible accounts and licenses. Microsoft licensing terms can change, so check the current service description and your organization’s subscription before relying on a particular feature or capacity.

Use named user accounts rather than shared credentials, grant only the permissions needed, and review access when roles change. If several people need to read messages but only a smaller group should send as the mailbox, grant Full Access and sending rights separately to the appropriate users. This separation reduces accidental or unauthorized use of the shared address.

Frequently Asked Questions

Can PowerShell add a shared mailbox directly to Outlook?
Not directly to an individual Outlook profile. PowerShell grants permissions in Exchange; Outlook then discovers the mailbox through automapping or the user adds it manually in the app.

Does Full Access let me send email from the shared mailbox?
No. Full Access lets the user open and manage mailbox contents. Grant Send As or Send on Behalf separately, according to how the sender should appear to recipients.

Why is the shared mailbox not showing in Outlook?
Check that Full Access was granted to the correct user, allow time for the change to propagate, and restart Outlook. Automapping may not apply to the client or to group-based permissions; try adding the mailbox manually.

Can I use automapping when permission is assigned to a group?
Do not rely on it. Exchange automapping is associated with direct Full Access assignments to individual users. A user with group-granted access may need to add the mailbox manually.

How do I remove a shared mailbox from Outlook?
If it was added manually, remove it from that Outlook client or profile. If it was automatically mapped, an administrator should remove the user’s direct Full Access permission in Exchange; the client may take time to stop displaying it.

Do I need to license a shared mailbox?
Often not for basic use within the standard size limit, but licensing may be required for extra capacity or particular compliance and archive features. Check current Microsoft licensing rules for the tenant’s plan.

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.