How to Fix Microsoft Teams “Mailbox Does Not Exist” Error

To fix the Microsoft Teams “Mailbox does not exist” error, first check that you are using the correct work or school account. Then have your administrator confirm that the required Exchange mailbox exists and that Teams can access it. If a mailbox is missing or access has been removed, reinstalling Teams will not repair the underlying problem.

Do not assume this message refers to a shared inbox. Teams calendar features depend on Exchange, while an Exchange shared mailbox and a Microsoft 365 group mailbox are different resources. Microsoft's Teams and Exchange integration guide explains how mailbox location affects available features. The steps below focus on work or school accounts.

1. Confirm the account and compare desktop with web access

Note where the error appears: your personal Teams calendar, a shared calendar, or an app added to a channel. That distinction determines which mailbox your administrator needs to investigate.

• Check the signed-in account and organization in Teams. Use the account associated with your organization's mailbox.
• Open Teams on the web with that same account and try the affected feature.
• For an Exchange Online mailbox, try Outlook on the web. For an on-premises mailbox, use your organization's Outlook web address.

If web access works but the Teams desktop app fails, select your profile picture, choose Sign out, quit Teams, and sign in again. These are Microsoft's current Teams sign-out instructions.

If Outlook also reports a missing mailbox, prioritize the mailbox checks below. If Outlook works but Teams fails in both clients, ask IT to investigate Teams-to-Exchange connectivity. These comparisons narrow the investigation; they do not establish the cause by themselves.

2. Have an administrator verify the mailbox and license

For an account intended to use Exchange Online, an administrator should open the Microsoft 365 admin center, go to Users > Active users, select the affected user, and review Licenses and apps. Confirm that an appropriate license is assigned and its Exchange Online service is enabled. See Microsoft's license assignment instructions.

Next, confirm that the user's mailbox actually exists in Exchange. A Teams entitlement alone does not establish that an Exchange mailbox has been provisioned.

Microsoft says provisioning or synchronization typically takes less than 30 minutes, but can take up to 24 hours. For a newly licensed account, run the EXO Recipient Object Failures diagnostic linked in Microsoft's mailbox provisioning guidance, resolve validation errors, and check service health. Contact Microsoft Support if provisioning remains unresolved after 24 hours.

If the mailbox is hosted on-premises, have the Exchange administrator verify that deployment instead of creating a second cloud mailbox as a workaround.

3. Check permissions if an actual shared mailbox is affected

Use this step only when the failure concerns a specific shared mailbox. In the Exchange admin center, an authorized administrator should:

• Open Recipients > Mailboxes and select the shared mailbox.
• Open its mailbox delegation settings and verify Read and manage (Full Access) for the affected user.
• Restore approved access if missing, save changes, and retest the mailbox in Outlook.

Send As and Send on Behalf govern sending, not permission to open the mailbox. Microsoft's shared mailbox documentation covers delegation. In hybrid environments, manage shared mailboxes through the appropriate on-premises Exchange tools.

Adding someone to a team is not a substitute for mailbox delegation. Likewise, changing shared mailbox permissions will not create a missing personal mailbox.

4. Diagnose Teams calendar connectivity

If the mailbox exists but Teams still cannot use it, follow Microsoft's Remote Connectivity Analyzer guidance. The Teams Calendar Tab test checks whether the Teams backend can connect to an Exchange mailbox. Administrators can use Teams Exchange Integration for broader integration checks. These tests are unavailable in GCC and GCC High environments.

For on-premises or hybrid mailboxes, IT should verify mailbox discovery, externally accessible Autodiscover and Exchange Web Services endpoints, OAuth configuration, and relevant access policies using Microsoft's Teams–Exchange troubleshooting guide. A local administrator PowerShell window alone does not provide Exchange administrative access.

Send IT the exact error, affected account, mailbox address, desktop/web comparison, and reproduction time with its time zone or UTC offset. After the identified issue is corrected, reopen the affected calendar or mailbox and confirm that the original action works.