Outlook classic fails on first launch after reboot: "This folder group cannot be opened. Microsoft Exchange is not available"

Question

Outlook classic fails on first launch after reboot: "This folder group cannot be opened. Microsoft Exchange is not available"

M365 Admin 0

Since early September 2026, classic Outlook for Windows (Exchange Online, Cached Exchange Mode) repeatedly fails on the first launch after a reboot with:

"Cannot start Microsoft Outlook. Cannot open the Outlook window. This folder group cannot be opened. Microsoft Exchange is not available. There are network problems, or the server computer running Microsoft Exchange is down for maintenance."

Setup: one Outlook profile with 9 mail accounts (mix of Exchange Online and IMAP/POP).

Latest reproduction: Application event log (Provider "Outlook") shows Event ID 30 ("Reconciliation of store ... started because: The store was last opened on a different machine") for two of the accounts, starting about 1.5 minutes after Outlook launch - but no matching Event ID 38 (reconciliation completed) before the fatal error appears roughly 5 minutes after launch. No errors or warnings logged in the Application log for that window. Network connectivity to outlook.office365.com:443 was confirmed working when checked. A custom Outlook COM add-in was ruled out as the cause (it had not even loaded yet when the error occurred, confirmed via its own log).

Question: has anyone found a permanent client-side fix for this, or is this a known Exchange Online-side authentication-concurrency-throttling issue when several accounts in one profile re-authenticate simultaneously after boot? Microsoft's own "known issues" page describes a similar symptom with cause "Authentication concurrency limit is reached", marked as fixed as of Oct 2025 - but the symptom still recurs here.

Things already tried without lasting success: Safe Mode, resetting the nav pane, recreating the Outlook profile.

0 comments

1 answer

Your answer

Answer 1

Hi M365 Admin

Since Safe Mode, Navigation Pane reset, and profile recreation have already been tested, the behavior does not appear to be associated with a documented client-side remediation.

According to my research, the symptoms are similar to a previously documented Microsoft issue described in Error when opening classic Outlook: "Cannot start Microsoft Outlook. Cannot open the Outlook window (Error when opening classic Outlook: "Cannot start Microsoft Outlook. Cannot open the Outlook window.…). The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed". In that article, Microsoft indicates that affected cases may contain the following exception in a network trace:

Microsoft.Exchange.RpcClientAccess.ClientBackoffException:
ErrorCode: ClientBackoff, LID: 49586 - Authentication concurrency limit is reached.

The article was later marked as Fixed, but it also notes that confirmation requires reviewing a network trace and that cases matching this signature require investigation by the Exchange Online service team rather than a client-side repair.

Based on the details shared, several observations are relevant:

The issue occurs only on the first Outlook launch after a reboot.
The profile contains nine accounts, including multiple Exchange Online mailboxes.
Event ID 30 (store reconciliation started) is recorded, but the corresponding Event ID 38 (reconciliation completed) is not logged before the Outlook startup error appears.
Connectivity to outlook.office365.com:443 was verified.
The custom COM add-in had not yet loaded when the issue occurred.

You can try to capture a Fiddler (or equivalent) network trace during reproduction and review it for entries such as:

Authentication concurrency limit is reached
ClientBackoffException
LID: 49586
ServerTooBusyException

If the trace contains these indicators, I recommend opening a support ticket with Microsoft Support team through the Microsoft 365 Admin Center and providing the trace, Outlook build number, and relevant event logs. In the previously documented issue, Microsoft indicated that cases matching this signature required review by the Exchange Online service team. (Get support - Microsoft 365 admin | Microsoft Learn. )

If those indicators are not present in the trace, the next step would be to investigate other possible factors, such as a specific mailbox or store within the profile, OST synchronization activity, or an Outlook build-specific issue.

I hope this information helpful and if you have any further questions, please feel free to via comment section.