New Outlook Cannot Open Public Folders: Fix

The new Outlook for Windows, also known as the One Outlook client, does not support public folders by default. This is a deliberate design choice by Microsoft, as the new client relies on REST APIs and the Microsoft 365 cloud infrastructure, which lack the legacy MAPI protocol support required for public folders. This article explains why public folders fail to load in the new Outlook and provides the only reliable fix: switching to the classic version of Outlook.

Why Public Folders Fail in the New Outlook

The new Outlook for Windows uses a modern codebase that communicates with Exchange Online via REST APIs. Public folders, however, rely on the MAPI protocol and the MAPI over HTTP transport. The new Outlook does not include a MAPI stack, which means it cannot enumerate, read, or write to public folders. This limitation applies to all public folder types: mail-enabled public folders, calendar public folders, and contact public folders.

Microsoft has stated that public folder support is not on the roadmap for the new Outlook. Organizations that depend on public folders must continue using classic Outlook. The new Outlook is intended for users who do not need legacy features such as public folders, COM add-ins, or custom forms.

What Happens When You Try to Open a Public Folder

When a user clicks the public folder node in the new Outlook folder pane, one of the following occurs:

• The public folder tree does not appear at all.
• An error message reads: “Something went wrong. We couldn’t connect to the public folder.”
• The folder list shows only the user’s own mailbox and shared mailboxes.

These symptoms are consistent across all Microsoft 365 subscription plans that include Exchange Online. On-premises Exchange Server users cannot use the new Outlook at all because the new client requires an Exchange Online mailbox.

Steps to Switch Back to Classic Outlook and Access Public Folders

The only supported workaround is to disable the new Outlook toggle and return to classic Outlook. Once you switch, public folders appear in the folder pane as they did before.

1. Open the new Outlook
   Launch the new Outlook app on your Windows 10 or Windows 11 computer.
2. Locate the toggle switch
   In the upper-right corner of the Outlook window, find the toggle labeled Try the new Outlook. If the toggle is blue, the new Outlook is active.
3. Turn off the toggle
   Click the toggle to set it to the off position (gray). A confirmation dialog appears.
4. Confirm the switch
   In the dialog, click Yes, switch to classic Outlook. Outlook closes and reopens in classic mode. This process may take up to 30 seconds.
5. Verify public folder access
   In classic Outlook, expand the folder pane. You should see Public Folders at the bottom of the list. Click All Public Folders to browse the hierarchy.
6. Pin classic Outlook (optional)
   To prevent accidentally switching back, right-click the Outlook icon on your taskbar and select Pin to taskbar. This ensures you always have quick access to the classic version.

If the Toggle Is Missing

Some organizations disable the toggle via Group Policy. If you do not see the toggle in the upper-right corner, contact your IT administrator. They can disable the new Outlook policy in the Microsoft 365 admin center under Org settings > Modern Authentication > New Outlook.

Alternative Methods to View Public Folders

If you cannot switch to classic Outlook due to organizational policy, you have two alternatives. Both are read-only and do not allow you to create or modify items.

Outlook on the Web (OWA)

Open a web browser and go to outlook.office.com. Sign in with your Microsoft 365 credentials. In the left folder pane, scroll down and click Public Folders. OWA uses REST APIs that include limited public folder support for browsing and reading items. You cannot create new posts or move items using OWA.

Outlook for Mac

The classic Outlook for Mac includes public folder support. If you have a Mac, open Outlook for Mac and click Public Folders in the folder pane. This client uses the same MAPI stack as classic Outlook for Windows.

If Public Folders Still Do Not Appear After Switching

If you switched to classic Outlook but public folders remain hidden, the issue likely lies with permissions or the Exchange configuration, not the Outlook client.

User Does Not Have Permission to Access Public Folders

Your Exchange administrator must grant you at least Folder visible permission on the top-level public folder hierarchy. Without this permission, the public folder tree does not appear in any Outlook client. Contact your IT department to verify your permissions in the Exchange admin center under Public folders > Public folder mailboxes.

Public Folders Are Not Enabled for the Organization

Some Microsoft 365 tenants have public folders disabled by default. An administrator must enable them using the Exchange Management Shell. The command Set-OrganizationConfig -PublicFoldersEnabled Remote turns on public folder access. After the change, users must restart Outlook.

Outlook Profile Is Corrupted

A damaged Outlook profile can prevent public folders from loading. In classic Outlook, go to File > Account Settings > Account Settings. Select your email account and click Repair. Follow the prompts. If repair fails, create a new profile via Control Panel > Mail > Show Profiles > Add.

New Outlook vs Classic Outlook: Public Folder Feature Comparison

Item	New Outlook	Classic Outlook
Public folder support	Not supported	Full support
Protocol used	REST APIs	MAPI over HTTP
Create and edit items	Not possible	Supported
OWA alternative	Read-only via browser	Not needed

Public folders remain a critical feature for many organizations that share calendars, contacts, or discussion boards. The new Outlook does not support this feature, and no future update is planned to add it. The only reliable fix is to switch back to classic Outlook. If your organization mandates the new Outlook, request an exception from your IT administrator for users who require public folders. For read-only access, use Outlook on the Web as a temporary workaround.