Outlook Shared Mailbox Not Updating: Fix Missing Emails and Sync Errors

Your team shares an address such as support@company.com, but new messages do not appear in Outlook until someone clicks Sync, restarts Outlook, or opens the mailbox in a browser. Sometimes the shared Inbox is stale, while other users can see the same messages immediately. In other cases the shared mailbox is completely missing, its folders do not expand, or a user’s permissions changed overnight.

Shared mailbox synchronization behaves differently in new Outlook, classic Outlook and Outlook on the web. Microsoft explicitly states that shared mailboxes added by automapping in new Outlook do not always automatically synchronize incoming Inbox mail; manual synchronization or adding the mailbox as an account can change that behavior. See the official new Outlook shared mailbox sync article. This guide shows how to locate the failure without deleting mail, changing tenant-wide settings blindly or recreating an Outlook profile as the first step.

Start with a server-side check: Open the shared mailbox through Outlook on the web with the correct work account. If the new message is visible online but missing in desktop Outlook, investigate client synchronization or cached data first. If it is also missing online, investigate delivery, shared mailbox configuration, transport rules and user permissions instead.

Quick symptom-to-fix table

Step 1: Determine which Outlook you’re using

New Outlook for Windows is not the same software experience as classic Outlook for Windows. Look at the application’s About or version information, and note whether the interface has a New Outlook toggle. Outlook on the web is a third context entirely. The correct fix depends on the client, the way the mailbox was added and the account’s permissions.

Do not use a classic Outlook cache-setting tutorial if your user is running new Outlook. Likewise, not every new Outlook shared mailbox option exists for every deployment and version. Microsoft’s shared mailbox settings overview notes that adding a mailbox as an account may not yet be available in all versions.

Step 2: Confirm the latest messages exist on the server

1. Sign in to Outlook on the web with your normal, authorized Microsoft 365 work account.
2. Open the shared mailbox through the supported Open another mailbox or mailbox navigation workflow permitted by your organization.
3. Search for a recent message from a known sender and note its received time.
4. Compare the same folder in desktop Outlook.
5. If the web mailbox has the message, avoid deleting or moving it. The desktop application is the likely point of failure.
6. If the web mailbox does not have the message, the Microsoft 365 administrator should check message trace, routing and delivery settings rather than rebuilding each user’s Outlook profile.

Testing with one reproducible message helps isolate the problem. For privacy, ask a colleague to send a harmless test message, not a confidential customer document.

Fix new Outlook: shared mailbox requires manual Sync

Microsoft documents that in new Outlook, incoming emails aren’t automatically synchronized in Inbox folders of shared mailboxes added by automapping in some scenarios. To fetch the latest messages, select the shared folder and choose Sync from the View section of the ribbon, or select the relevant folder to trigger synchronization. These are supported actions, not hacks.

If your workflow requires automatic updates and notifications, the documented path is to add the shared mailbox as an account, provided your version supports the option and you have the necessary access. See Microsoft’s Sync a shared mailbox in new Outlook.

Add an eligible shared mailbox as an account

1. Verify an administrator has granted Full Access to the shared mailbox.
2. In new Outlook, open Settings → Accounts → Shared with me or the equivalent current path.
3. Identify the desired shared mailbox.
4. If it was automatically mapped and Convert is offered, use Convert to add it as an account.
5. If it was manually added as a shared folder, use the available account promotion or Add workflow described by Microsoft.
6. Check whether the shared mailbox now appears under Your accounts.
7. Test incoming messages and notifications with a harmless email.

Microsoft warns that shared mailbox-as-account support and related features may vary. Do not tell users to sign in directly using the shared mailbox’s password: shared mailboxes typically operate through delegated user access, not individual password sharing.

Fix classic Outlook: update folders and cached mode

In classic Outlook, the shared mailbox may be displayed through the primary mailbox’s permissions and automatic mapping. First select Send/Receive → Update Folder for a controlled test. If this brings in new mail, investigate cached shared-folder behavior.

Inspect Download shared folders carefully

1. Open File → Account Settings → Account Settings in classic Outlook.
2. Select the work account and the settings for Microsoft Exchange or Microsoft 365.
3. Open More Settings → Advanced where offered.
4. Check the Download shared folders setting and record its existing state.
5. Discuss a controlled change with IT if local shared-folder caching is suspected.
6. Restart Outlook and compare mailbox behavior online and in desktop Outlook.

Disabling shared-folder caching may help isolate a cache issue, but it changes performance, bandwidth and offline behavior. It should be a deliberate, scoped troubleshooting measure, not a universal setting to push across the company. Admins should consult the organization’s official Outlook client guidance and test a small group first.

Step 3: Check Outlook account and mailbox permissions

Microsoft 365 shared mailboxes rely on permissions such as Full Access, Send As and Send on Behalf. These are not interchangeable. Full Access permits opening and managing mailbox content; sending using the shared address can require distinct permissions.

In Microsoft 365 admin or Exchange admin centers, confirm who has access, when the permissions were changed, and whether the user is signed into the expected tenant. Avoid granting Full Access to all employees as a shortcut. Access should follow least-privilege policies.

Step 4: A shared mailbox is missing completely

Microsoft advises that after an admin adds a member, the mailbox may take time to appear. In classic Outlook, close and restart the app. If necessary and authorized, add the mailbox through File → Account Settings → Account Settings → Change → More Settings → Advanced → Add, according to Microsoft’s shared mailbox guide. The exact menu sequence can differ in Microsoft 365 builds.

If the mailbox was manually added before, avoid creating duplicate mailbox entries without checking the current profile. Duplicate references can increase troubleshooting confusion.

Step 5: Test the connection and app health

Check whether Outlook shows Working Offline, Disconnected or Trying to connect. Confirm the user can access other Microsoft 365 mailboxes. If all mailboxes are stale, it may be a general authentication or network problem rather than a shared mailbox issue.

Restart Outlook, sign into the correct account when prompted, and install approved Office updates. On managed PCs, IT may review proxy, authentication, endpoint protection or Microsoft 365 service status. Do not disable security software globally to see if synchronization resumes.

Step 6: Shared mailbox missing only on one computer

Compare the same user on Outlook on the web and, if available, a second supported desktop client. If only one profile is affected, a local Outlook profile or cache problem becomes more plausible. A support technician may create a new Outlook profile after documenting accounts, custom settings and locally stored data. Back up any PST archives first.

Do not delete a PST or an OST blindly. A cached Exchange OST is usually re-created from the server, but unsynchronized changes may exist locally. The organization should verify the online data before replacing a profile. See our companion topic on OneDrive synchronization troubleshooting for general sync concepts, noting that Outlook and OneDrive use different systems.

Step 7: New messages arrive but no desktop notifications appear

A missing notification is not always a synchronization failure. Confirm the message really arrived and can be opened in the shared Inbox. New Outlook can expose different notification and account options depending on whether the shared mailbox is configured as an account rather than a shared folder. Review Manage shared mailbox settings in new Outlook for supported behaviors and gaps.

Also check Windows System → Notifications, Focus or Do Not Disturb settings, and the Outlook application’s own notification controls. Avoid assuming the sender’s message was undelivered merely because nobody saw a toast notification.

Step 8: Diagnose mail flow if nobody can see new mail

When the shared mailbox is empty even in Outlook on the web, have an authorized Exchange administrator check that it exists, is licensed when required by its configuration, and is not blocked by mail-flow rules, forwarding configuration or domain settings. Use message trace to determine whether the test message was accepted, rejected, quarantined or redirected.

Do not confuse a sender receiving an NDR with a local Outlook cache issue. Capture the actual SMTP status and recipient address; a permission or shared mailbox naming issue is different from an organization-wide MX record outage.

Step 9: Search and folder navigation problems

Sometimes the messages are present but Search cannot find them or the user is looking in the wrong folder. Verify the correct Inbox, archive, sent folder and other mailbox hierarchy. In new Outlook, Microsoft notes some feature gaps for shared mailboxes as accounts, so test whether the missing function is supported in that client version.

For classic Outlook, compare folder contents on the server and inspect the cached state. If only search is affected, consider indexing or search-scope troubleshooting rather than treating all folders as unsynchronized.

Step 10: Shared Sent Items appear in personal mailbox

Shared mailbox sending behavior and where copies of sent mail are stored are governed by mailbox configuration. If users report that outgoing shared-address messages appear only in the sender’s personal Sent Items, ask the Microsoft 365 administrator to review shared mailbox sent-item copy settings. This is an administrative configuration issue, not proof that new mail synchronization failed.

Admin checklist: isolate service, access and desktop issues

Safe diagnostic sequence for Microsoft 365 administrators

1. Confirm the affected mailbox address, affected users, start time and Outlook editions.
2. Verify the mailbox in Exchange admin center and user permissions.
3. Test whether a harmless message reaches the online mailbox.
4. Inspect per-user behavior before making company-wide Outlook cache changes.
5. For new Outlook, verify documented sync limitations and account promotion availability.
6. For classic Outlook, compare cache-enabled and supported online behavior in a controlled test.
7. Monitor result and document any changes to mailbox delegation.

Avoid these costly shared-mailbox mistakes

• Do not repeatedly create new mailbox objects to replace a mailbox that merely fails local sync.
• Do not distribute a shared mailbox password or sign in as that mailbox to bypass delegated permissions.
• Do not clear profiles, OSTs or archives until online messages and local-only content have been assessed.
• Do not confuse a notification setting with missing delivery.
• Do not grant tenant-wide mailbox access merely to repair one user’s permissions.
• Do not force an unsupported client behavior through unverified registry tweaks.

Confirm the problem is resolved

Ask a test sender to send one harmless message to the shared mailbox, note the time, and observe whether it appears online and in each intended desktop client. Reply from the shared address only when the user has the required sending permission, then verify delivery and the selected Sent Items behavior. Restart Outlook and repeat to ensure the apparent fix persists.

For monitoring, track the proportion of support cases limited to one client version. If users have different Outlook releases, consistent desktop behavior may require standardizing supported builds or revising mailbox onboarding procedures.

Detailed situations that make shared mailbox sync look inconsistent

Only the night-shift agent misses new support emails

When everyone else can see the email, ask the affected person to compare desktop Outlook with Outlook on the web. If the browser shows the message, check the local client edition and how the mailbox was added. On new Outlook, an automatically mapped mailbox may require selecting the folder or manually using Sync; Microsoft explicitly documents this behavior. On classic Outlook, inspect cached shared folders and account connection state instead. Do not apply the same cache setting to all staff until you establish which client and behavior is responsible.

A new employee joins the team but the shared mailbox doesn’t appear

Confirm that Microsoft 365 has granted the correct user Full Access and that the employee is using the expected organization account. The app may need to restart after rights propagate. If the mailbox remains absent, use the supported add-mailbox workflow for that version of Outlook. Don’t distribute a shared mailbox password or create a new shared mailbox with a nearly identical address. Also check whether the new employee is in the correct licensing and identity scope for accessing Microsoft 365 services.

The Inbox updates, but the shared Sent Items folder looks empty

This may be a sent-item copy configuration issue rather than a sync problem. Ask the user to send a harmless authorized test email from the shared address, then check personal Sent Items and shared Sent Items. Administrators can review how copies of shared mailbox messages are stored. Document which location your team’s workflow expects, particularly if records must be retained. Do not move or delete messages until the copies and retention requirements are understood.

Shared folders refresh slowly when cached mode is enabled

Local caches can improve responsiveness and offline use, but large shared mailboxes, limited storage or cached-folder problems may delay updates. A controlled test can compare Outlook’s cached behavior with an approved alternative setting on one user’s device. Document what changed, restart Outlook and evaluate user experience before recommending a policy change. Disabling caching could make a shared mailbox slower on high-latency connections and remove offline availability, so this isn’t universally better.

The Shared with me entry exists but the account conversion option is absent

Microsoft says shared mailbox-as-account support in new Outlook may differ by version. Verify that Full Access was granted and use the available interface. Some tenants or application builds may not show Convert or Promote. The absence of a button isn’t proof the mailbox is corrupt. Check the official feature documentation for the version in use, and use documented manual syncing until an appropriate supported option is available.

Distinguish Exchange delivery problems from Outlook user-interface problems

For a message thought to be missing, record the sender, recipient, subject and approximate delivery time without sharing sensitive content broadly. A Microsoft 365 administrator can use the approved mail tracing tools to see whether the service accepted the message and how it routed. If the service says delivery succeeded and the message is visible in Outlook on the web, focus on client state, folder filters, rules and synchronization. If the service says it was rejected or redirected, rebuilding an Outlook profile is unlikely to help.

Search across Inbox, Junk Email, Deleted Items, quarantine views available to admins, and any organizational mail-routing rules. A message missing from the user’s chosen Inbox folder can still exist elsewhere in the mailbox. Always follow the organization’s privacy and retention rules when inspecting employee or customer email.

Client comparison: what users and IT should expect

This comparison is not a guarantee that every feature is available in every release. Microsoft can change the new Outlook implementation as features roll out.

A controlled test protocol for IT administrators

1. Record Outlook build and whether the user has new or classic Outlook.
2. Confirm correct work account, tenant and Full Access permissions.
3. Send one non-sensitive test message to the shared mailbox.
4. Confirm it appears in Outlook on the web and note the arrival time.
5. In new Outlook, inspect the Shared with me view, manually Sync and test account-conversion availability.
6. In classic Outlook, inspect Offline/Disconnected status, update the folder and compare cached behavior on a pilot profile.
7. If another user sees the message but the affected user cannot, examine that user’s permission scope and profile.
8. Verify outgoing shared mail works only for users with separate authorized sending permissions.

Capture before-and-after screenshots of relevant settings without exposing customer content or access tokens. Reproduce the original problem at least twice so the result isn’t merely a temporary refresh.

Shared mailbox governance: keeping access manageable

A shared mailbox should have a named business owner, an explicit member roster and a process for employees joining or leaving. Audit Full Access and sending permissions regularly. Avoid adding every user automatically to every mailbox. If the shared address is used for customer support, decide how your team tracks ownership and response status; email synchronization alone cannot prevent two agents from replying to the same request.

When access is removed, consider timing and client caching. Someone who recently lost permission may briefly see locally cached folder names but should no longer be authorized to access protected content. Don’t attempt to bypass a removed permission by importing old mailbox data or using an account password. Escalate any inconsistent authorization behavior through proper IT channels.

Post-fix monitoring

After a fix, confirm normal mail delivery at several times of day, across both supported clients and with at least two team members. Note whether manual Sync remains necessary in a documented new Outlook configuration. A user expectation that “all shared folders must refresh instantly” may not match the current client behavior, so onboarding guidance should reflect official limitations. Keep the difference between delivery success and desktop notification clear in support documentation.

Operational playbook for shared support and sales inboxes

A shared mailbox supports collaboration but is not itself a ticketing system. Even when synchronization is healthy, two employees may open and answer the same customer email. Consider a documented triage process: designate ownership, use agreed categories where the client supports them, and confirm where sent-item copies are stored. If the team needs assignment and audit trails, use a purpose-built workflow or approved CRM rather than relying on a single “read/unread” state in Outlook.

When users complain that one person received an email and another didn’t, determine whether the message is absent, merely unread somewhere else, or not displayed due to a client filter. Check the shared mailbox online with proper authorization, compare the Received timestamp, and inspect folder rules. If both users can see the message online but desktop behavior differs, client-specific troubleshooting is appropriate. If neither can see it online, move toward Exchange delivery investigation.

How to document Full Access and sending rights changes

An administrator should record who requested access, who approved it, which permission was granted, and when it should expire or be reviewed. Full Access gives broad read/manage access; Send As and Send on Behalf can allow different forms of outgoing email. Do not conflate these permissions in support documentation. A user who can open the shared Inbox but cannot send from the address may be experiencing the correctly enforced distinction between read and send rights.

If Outlook fails immediately after permissions are changed, allow for documented propagation and restart the client where appropriate. A team that repeatedly revokes and re-adds permissions within minutes may introduce additional confusion. Confirm current role assignments in the admin center and use one controlled permission change at a time.

Offline availability and performance trade-offs

Classic Outlook users working over slower connections may benefit from caching shared folders, while large shared mailboxes can make cache files and updates more demanding. Disabling caching for a diagnostic test changes how content is fetched. It may improve freshness in one environment but make another user’s Outlook slower or dependent on continuous connectivity. Before broad deployment, document the affected client build, network latency, mailbox size and time needed for normal refresh.

New Outlook has a different behavior for some automapped shared mailboxes, so administrators should not apply legacy classic Outlook cache assumptions to it. Microsoft’s current guidance points users to manual Sync or supported account conversion when automatic Inbox updates are required.

A shared mailbox moves to another tenant

Cross-tenant migrations can change the mailbox’s identity, permissions and how users reach it. Ask whether the old and new mailboxes have the same visible address but different underlying tenant identities. Verify the intended target tenant, account membership, routing and access; do not keep attaching stale mailbox references from an earlier profile. If both tenants temporarily accept mail during transition, the migration team should reconcile messages rather than having users manually drag folders between unverified mailboxes.

Important verification after any Outlook repair

A repair that makes messages appear immediately is not enough. Confirm that new test messages continue to arrive after Outlook restarts and that each authorized team member sees the same mailbox contents. Check whether a shared folder requires manual sync as documented for the particular client. If notifications remain inconsistent, describe that separately from delivery. A written end-user guide should state the actual Outlook edition and supported refresh method, preventing future tickets caused by incorrect expectations.

Official Microsoft references

• Sync a shared mailbox in new Outlook
• Manage shared mailbox settings in new Outlook
• Open and use a shared mailbox in Outlook
• About shared mailboxes and shared folders
• Share and access another person’s mailbox or folder

Editorial note: This guide covers documented behavior as reviewed on October 16, 2026. Outlook client features and managed tenant options can vary with updates.