Skip to main content
Graduate Track

Creating a Shared Mailbox in Microsoft 365 and Granting Full Access and Send As

Create a shared mailbox in Microsoft 365, grant Full Access and Send As, check both with Get-MailboxPermission and fix automapping and send errors.

Creating a Shared Mailbox in Microsoft 365 and Granting Full Access and Send As
KBY Technologies15 min readFoundation13 min

In this lesson

Share

Before you begin

  • The Exchange Administrator role in a test tenant or with approval to create one test mailbox.
  • A test user with a licensed Exchange Online mailbox.
  • Optionally, the Exchange Online PowerShell module for the read-only checks.

Track this tutorial

Choose your current status and tick each safety check as you complete it. Sign in to sync progress between devices.

Current status

Before you apply the change

Confirm these production-safety controls during the tutorial.

0 of 6 safety checks completed

To create a shared mailbox in Microsoft 365, sign in as an Exchange administrator, go to Teams & Groups > Shared mailboxes in the Microsoft 365 admin center, select Add a shared mailbox, name it and save. Then give each person who will work from it two separate permissions: Full Access, which lets them open the mailbox and read, change and delete its items, and Send As, which lets them send mail that appears to come from the mailbox itself. Full Access on its own does not let anyone send. Microsoft says both are needed for a shared mailbox to work normally.

A few constraints decide whether the set-up holds. Every person needs their own licensed Exchange Online mailbox, but the shared mailbox itself needs no licence up to 50 GB. Sign-in to the shared mailbox’s own account is blocked by default and should stay blocked. Microsoft supports up to 25 users on one shared mailbox. Outlook only adds the mailbox automatically when each person is granted Full Access individually, not through a security group. And a brand-new mailbox can refuse to send for about an hour while the change replicates.

#What you will learn from this set-up

  • What a shared mailbox is, and why it has a user account that nobody signs in to.
  • The difference between Full Access, Send As and Send on Behalf, and which one a team needs.
  • How to create a shared mailbox in the Microsoft 365 admin center and add members.
  • How to read the permissions back with Exchange Online PowerShell without changing anything.
  • Why automapping, hidden address list entries and replication delays cause most of the support calls.

#Before you begin

  • An account with the Exchange Administrator role. If the admin center shows “You don’t have permission to access this page or perform this action”, you are not an admin for this task.
  • A test tenant, or written permission to create one test shared mailbox in your organisation’s tenant.
  • One test user with a licensed Exchange Online mailbox. A Microsoft 365 Apps for business subscription on its own does not include email, so it cannot host a shared mailbox.
  • Optional, for the read-only checks: the Exchange Online PowerShell module on your workstation.
  • A name and address for the mailbox that no other recipient already uses.

#How a shared mailbox is put together

A shared mailbox is an ordinary Exchange Online mailbox that belongs to a role rather than a person, such as support@ or reception@. Behind it sits a user account, because every mailbox needs one, but Microsoft gives that account a system-generated password that nobody knows and blocks its sign-in. People never log in as the shared mailbox. They log in as themselves and Exchange checks what their own account is allowed to do with the shared one. That is why a member needs a licensed mailbox of their own: access is delegated through the member’s mailbox, and the shared mailbox only stores the mail.

Because of that design, the shared mailbox needs no licence for most uses. Up to 50 GB of mail can be stored without one. Microsoft documents three cases that do need a licence. More than 50 GB needs Exchange Online Plan 2, which raises the limit to 100 GB. An in-place archive or litigation hold needs Plan 2, or Plan 1 with the Exchange Online Archiving add-on. When a shared mailbox reaches its storage limit it can still receive mail for a while but cannot send, and later it stops receiving and senders get a non-delivery report.

There are also limits that change which tool you should pick. Only people inside your organisation can use a shared mailbox; you cannot give a Gmail user access. Microsoft supports a maximum of 25 users, and if too many people use it at the same time they might see connection failures or duplicated messages. You cannot stop members deleting messages. Mail sent from a shared mailbox cannot be encrypted with the mailbox’s own key, because it has no security context of its own. For more users, people outside the organisation or control over deletion, Microsoft points you to a Microsoft 365 group instead, and the article on restricting who can create Microsoft 365 groups covers how groups are controlled in a tenant.

#
The three permissions and what each one shows the recipient

Exchange keeps reading and sending as separate rights, and that separation is the part new administrators most often miss.

Shared mailbox permissions in Exchange Online
PermissionWhat the person can doWhat the recipient seesWhere it is granted
Full AccessOpen the mailbox, read, create, change and delete items, use its calendar. Cannot send.Nothing; no mail is sentManage mailbox delegation, or Add-MailboxPermission
Send AsSend mail that appears to come from the shared mailboxThe shared mailbox only, for example Contoso SupportManage mailbox delegation, or Add-RecipientPermission
Send on BehalfSend mail on behalf of the shared mailbox“John on behalf of Reception Building 32”Exchange admin center, or Set-Mailbox -GrantSendOnBehalfTo

For a support or reception mailbox, Send As is normally what the team wants, because replies should come from the team, not from a named person. Send on Behalf is the choice when the recipient should see who actually wrote the reply.

#
Automapping, and why groups do not trigger it

When a person has Full Access, Outlook uses Autodiscover to add the shared mailbox to their profile automatically after they close and reopen Outlook. This is called automapping and it is on by default. Microsoft states that automapping is set on the user’s mailbox, not the shared mailbox, and that Autodiscover does not enumerate security groups. So if you grant Full Access to a security group, the members get access but Outlook does not add the mailbox for them; they must add it by hand. If you want automapping, grant Full Access to each person.

The opposite case also comes up. Someone with access to many shared mailboxes may not want all of them loaded in Outlook. The Add-MailboxPermission cmdlet takes -AutoMapping $false for that. For a person who already has Full Access, Microsoft’s documented route is to remove their Full Access and grant it again with -AutoMapping $false.

#The order of a shared mailbox set-up

The steps are simple, but the order matters because two of them have a delay built in. Adding members may have to wait a few minutes after the mailbox is saved, and sending can fail for about an hour while Microsoft 365 replicates the new mailbox and permissions across its datacentres. The flow below is the order this guide follows, with the two checks that stop you handing over a mailbox that cannot send.

Rendering diagram...

Read each diamond as a question you answer with evidence, not with a guess. The first is answered with the read-only PowerShell commands in the next section; the second by sending a real message and reading the result in the recipient’s inbox.

#A support mailbox in practice

Close-up of an open mailbox in a residential building with visible mail, showcasing selective focus.
Photo by Arti Kh on Pexels

#
Worked example: support@ for a three-person service desk

A small company wants support@contoso.com answered by three service desk staff, with replies coming from Contoso Support. In the admin center the administrator goes to Teams & Groups > Shared mailboxes, selects Add a shared mailbox and enters Contoso Support. The name chooses the email address, which can be edited before saving. After Save changes, the page notes it may take a few minutes before members can be added. Under Next steps the administrator selects Add members to this mailbox, adds the three people and closes the pane.

Next, the administrator confirms what each person actually holds. In the Exchange admin center, under Recipients > Mailboxes, they select the shared mailbox and then Manage mailbox delegation under Mailbox permissions. That pane lists Full Access and Send As separately, and anyone missing from Send As is added there. The same answer is available read-only from Exchange Online PowerShell:

1Connect-ExchangeOnline -UserPrincipalName admin@contoso.onmicrosoft.com
2Get-MailboxPermission -Identity support@contoso.com -User "Ayla Kol"
3Get-RecipientPermission "Contoso Support"

The first line opens the session. Get-MailboxPermission with -User returns only the permissions Ayla has on the shared mailbox; the line to look for has FullAccess in its AccessRights. Get-RecipientPermission lists everyone who has Send As on the mailbox. If Ayla appears in the first result but not the second, she can read the mailbox and will be refused when she tries to send from it. Neither command changes anything.

#
Worked example: the reply that will not send

Ten minutes after set-up, one of the three tries to reply from Contoso Support and Outlook says: “This message could not be sent. You do not have the permission to send the message on behalf of the specified user.” The read-only checks show Send As is present. Microsoft documents this message as a replication delay on a new shared mailbox or newly added user, and says it clears in about an hour. The right action is to wait and try again, not to start granting extra rights. Had Get-RecipientPermission shown no Send As for that person, the cause would have been the missing permission instead, and the fix is to grant it.

#Try it on a test shared mailbox

#
Exercise: grant and prove Full Access and Send As for one user

Objective: create a test shared mailbox, give one test user Full Access and Send As, and prove both with evidence.

Safe setup: use a test tenant or a mailbox name your organisation has approved, such as KBY Lab Shared. Use one test user who has a licensed Exchange Online mailbox. Nothing in production should depend on either.

  1. In the Microsoft 365 admin center go to Teams & Groups > Shared mailboxes, select Add a shared mailbox, enter KBY Lab Shared and select Save changes. If you see an error that the proxy address is already being used, stop and choose a different name.
  2. Wait a few minutes, then select Add members to this mailbox and add the test user.
  3. Connect with Connect-ExchangeOnline and record the starting state with Get-MailboxPermission -Identity "KBY Lab Shared" -User <test user> and Get-RecipientPermission "KBY Lab Shared". Save both outputs; they are your before picture.
  4. If the test user has no FullAccess entry, grant it: Add-MailboxPermission -Identity "KBY Lab Shared" -User <test user> -AccessRights FullAccess -InheritanceType All.
  5. If the test user is not listed for Send As, grant it: Add-RecipientPermission "KBY Lab Shared" -AccessRights SendAs -Trustee <test user>.
  6. Run the two read-only commands again and compare them with the saved before picture.
  7. Sign in as the test user in Outlook on the web, open the shared mailbox, and send a message from it to another mailbox you control.

Expected evidence: Get-MailboxPermission shows the test user with FullAccess; Get-RecipientPermission lists the test user with SendAs; the received message shows KBY Lab Shared as the sender, with no “on behalf of” wording.

Pass condition: all three pieces of evidence are present, and the shared mailbox’s own account still shows sign-in blocked under Users > Active users.

Stop condition: stop and do not grant anything further if the admin center refuses the action for lack of permission, if the mailbox name is already in use, or if the send still fails more than an hour after the permissions were added. Each of those needs someone with more context, not more rights.

Cleanup: remove the test permissions with Remove-RecipientPermission "KBY Lab Shared" -AccessRights SendAs -Trustee <test user> and Remove-MailboxPermission -Identity "KBY Lab Shared" -User <test user> -AccessRights FullAccess -InheritanceType All. Both ask for confirmation. Leave sign-in blocked, and hand the empty test mailbox to whoever owns the tenant to retire under their own process.

#How to check the shared mailbox works

A shared mailbox is finished when the evidence says so, not when the admin center says “saved”. Check these in order, because each one depends on the one before.

  1. The mailbox exists and appears on the Shared mailboxes page.
  2. Each intended person has FullAccess in Get-MailboxPermission, and each person who replies is listed in Get-RecipientPermission with SendAs.
  3. Nobody else is listed. Extra names are as much a finding as missing ones.
  4. A test message sent from the shared mailbox arrives with the shared mailbox as the sender.
  5. The shared mailbox’s account still has sign-in blocked and, unless one of the documented cases applies, shows as Unlicensed on Active users.

If the shared mailbox does not appear in someone’s Outlook desktop on its own after they restart Outlook, check whether they were granted access through a group, which is the documented reason automapping does not happen.

#Mistakes that break shared mailbox access

#
Granting Full Access and stopping there

The person can read everything and is refused the moment they reply. Microsoft’s own note on the delegation pane is that both permissions are required. Check Send As separately every time.

Colleagues working diligently at shared desks with laptops in a modern office space.
Photo by Thirdman on Pexels

#
Using a security group and expecting Outlook to add the mailbox

The access works, but automapping does not, because Autodiscover does not enumerate security groups. Either accept that members add the mailbox themselves, or grant Full Access to individuals.

#
Hiding the mailbox from the address list

Setting HiddenFromAddressListsEnabled to True on the shared mailbox stops Send As and Send on Behalf working in the Outlook desktop client, because both need the mailbox to be visible in the Global Address List. Leave it visible if people send from it in Outlook desktop.

#
Unblocking sign-in to “fix” access

When a member cannot get in, it is tempting to unblock the shared account and share a password. Microsoft says to always block sign-in for the shared mailbox account and keep it blocked. Fix the member’s permission instead.

#
Treating the first send failure as a permissions problem

On a new mailbox, the “You do not have the permission to send the message on behalf of the specified user” error can be replication. Read the permissions first; if they are right, wait about an hour before changing anything.

#
Licensing the shared mailbox out of habit

A shared mailbox under 50 GB with no archive or litigation hold needs no licence. If one was assigned, remove it on the shared mailbox’s Licenses and Apps tab under Users > Active users, since licences are user settings and cannot be removed from the Shared mailboxes page. That alone does not stop the charge: the spare licence also has to be removed from the subscription. Before removing a licence, check the mailbox’s size and hold status, because the three documented cases do need one. The guide to group-based licensing in Microsoft Entra ID explains why a licence can arrive through a group rather than directly, which changes where you remove it.

#What to remember about shared mailboxes

  • Full Access is for reading and managing; Send As is for sending. A working shared mailbox needs both.
  • Members need their own licensed Exchange Online mailbox; the shared mailbox needs a licence only above 50 GB, with an archive or on litigation hold.
  • Sign-in to the shared account is blocked by default. Keep it that way.
  • Automapping only follows permissions granted to individual users.
  • A new mailbox can refuse to send for about an hour; read the permissions before changing them.
  • Past 25 users, external access or a need to stop deletions, use a Microsoft 365 group instead.

#Handing a shared mailbox over to a real team

In production, treat every Full Access and Send As grant as an access decision with an owner. Record who asked for the mailbox, who approves membership, and whether replies should show the team (Send As) or the person (Send on Behalf). Microsoft notes that in Exchange Online a person with Full Access can see every item, including calendar items marked Private, so a mailbox that receives HR or payroll mail needs a smaller membership than a general enquiries box. If your tenant also restricts legacy sign-in, the article on Conditional Access blocking legacy authentication explains the AADSTS53003 error that appears when Conditional Access blocks legacy authentication: a sign-in problem, not a mailbox permission, and worth ruling out when a member says they cannot get in.

Before you close the request, run the read-only checks one last time and save their output with the ticket. Rolling back is bounded: Remove-RecipientPermission and Remove-MailboxPermission take away exactly what was granted and leave the mail in place. Escalate rather than improvise when the tenant is hybrid, because Microsoft says shared mailboxes there are created and managed in the on-premises Exchange admin center, or when the name collides with an existing proxy address. The next decision is about review, not set-up: put a date in the diary to check the membership list, because shared mailbox access tends to outlive the people who needed it.

About this page

Credited to

Dates

Published

Sources

This page lists no external sources.

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on Creating a Shared Mailbox in Microsoft 365 and Granting Full Access and Send As. Comments are checked for spam and held for moderation before appearing.

Loading comments...

Discover more

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

Build practical engineering skills.

Receive new lessons, learning paths, practical exercises and early-career guidance.