A shared mailbox appears in new Outlook only when permissions and account setup agree. If it is missing, do not keep adding it repeatedly. Confirm access first, then add it from the right account.
Confirm permission before setup
Ask the mailbox owner or administrator to confirm Full Access permission. If you also need to send from the mailbox, confirm Send As or Send on Behalf separately.
Those permissions are different. A user can read a shared mailbox and still fail when sending from it.
Add it under the work account
Open new Outlook settings and add the shared mailbox under the signed-in Microsoft 365 work account. Enter the mailbox address and wait for folders to appear.
Note: Large mailboxes scanning may take a little time. Expand the mailbox root before assuming folders are missing.
Test the two things people forget
First, open a folder that contains recent mail. Then send a test message from the shared address if sending is part of your role.
If folders are hidden or collapsed, compare the symptoms with Outlook folders hidden. For account-level setup, see default email account in new Outlook.
Common causes of a missing shared Outlook mailbox
- Full Access was not granted yet.
- The mailbox was added under the wrong account.
- Outlook has not refreshed the folder list.
- Send permissions were confused with read permissions.
- The mailbox works on the web but not in desktop Outlook.
If it works on the web but not in new Outlook
Restart new Outlook and check again. If the mailbox still does not appear, remove the shared mailbox entry and add it again after permissions are confirmed.
Make sure not to remove your primary work account unless other mailbox features are also broken.
Permissions can take time
After an administrator grants access, the shared mailbox may not appear instantly. Sign out and back in, or restart new Outlook, before assuming the permission failed.
If access still does not appear, test Outlook on the web. That helps separate mailbox permission from a desktop app refresh problem.
Sending rights deserve their own test
Many shared mailbox tickets are really send-permission tickets. Full Access lets you open the mailbox. Send As or Send on Behalf controls whether you can send from it.
Test both. Open a folder to prove read access, then send a short internal message from the shared address to prove send access.
Keep the mailbox easy to use
Once the mailbox appears, pin or favorite the folders people use every day. Shared mailboxes can be large, and users may miss important folders if everything stays collapsed.
If several people work from the same mailbox, agree on categories, flags, or folder rules. Shared access solves visibility. It does not automatically create a team process.
Make the shared mailbox usable for the team
After the mailbox appears, agree on how the team will handle messages. Shared access only solves visibility. It does not decide who replies, who closes requests, or which messages need follow-up.
Use categories, flags, or folders consistently. If everyone invents their own system, the mailbox becomes hard to trust even though the technical setup is correct.
For high-volume shared mailboxes, review permissions regularly. Remove users who no longer need access and confirm that sending rights match each person’s role.
What changes after the mailbox is added
Adding the mailbox is only the technical start. The daily workflow changes once several people can read and send from the same address. Without a team process, messages can be answered twice or missed because everyone assumes someone else handled them.
Decide how the mailbox will show ownership. Some teams use categories for open, waiting, and done. Others use folders for each queue. The exact system matters less than everyone using the same one.
Sending also needs a rule. If replies should come from the shared address, test that before the mailbox goes live. If replies should come from individual users, tell the team so customers or coworkers do not see inconsistent sender names.
Review access every few months. Shared mailboxes often accumulate old users because they are not tied to a single person’s license in the same visible way. Removing stale access keeps the mailbox cleaner and safer.
If the mailbox is business critical
For support, billing, or customer-facing mailboxes, test the setup with a real workflow before the team depends on it. Confirm that new mail appears, replies use the expected sender, and completed messages are easy to identify.
Also decide who owns permission changes. Shared mailbox access tends to grow over time, so someone should review membership and send rights on a regular schedule.
If the mailbox supports customers or vendors, decide how quickly messages should be acknowledged. Shared access works best when the team has a simple expectation for ownership, response time, and handoff.
Why can I read the mailbox but not send from it?
Full Access and Send As are separate permissions. You may be allowed to open folders but not send as the shared address. Ask an administrator to check the send permission specifically.
Does new Outlook add shared mailboxes automatically?
Sometimes shared mailboxes appear automatically after permission is granted, but not always immediately. Manual setup is useful when the mailbox is missing or when you need to confirm which account owns the access. Restart Outlook after permission changes before assuming setup failed.
Can I add a mailbox without admin help?
Only if the required permissions already exist. Adding the address in Outlook does not grant access by itself. If the mailbox does not open, confirm Full Access and any required send permissions with the owner or administrator.
What to check after setup
Shared mailbox setup is complete only after folders load and send rights are tested. Open a recent message, send a controlled test reply, and confirm the reply uses the expected sender. If the mailbox is shared by a team, agree on categories or folder ownership before live work starts. The technical setup and the team process need to work together.