Errro message: GetSections returned no conversation history Try again

Michael Schuenemeyer 25 Reputation points
2026-09-08T14:24:16.3566667+00:00

I got the following error message in Microsoft 365, how do I fix it?

Something went wrong server Error(/):

GetSections returned no conversation history

Try again

Show debug details (internal only)

Microsoft 365 and Office | Other

5 answers

Sort by: Most helpful
  1. donna metcalf 0 Reputation points
    2026-09-08T15:51:18.4333333+00:00

    Any word on this issue? I am having the same problem this morning.

    GetSections returned no conversation history"

    Was this answer helpful?

    1 person found this answer helpful.

  2. Hornblower409 14,600 Reputation points
    2026-09-09T05:37:01.1466667+00:00

    Looks to be a reported Service Health issue. Shows as Restored.

    https://admin.cloud.microsoft/?#/search/:/alerts/MO1469271

    Users received a "GetSections returned no conversation history" error message.

    Sep 8, 2026, 12:28 PM CDT

    We reverted a recent service update that was intended to improve chat-loading functionality when accessing m365.cloud.microsoft and confirmed through service telemetry that the error rates have subsided and service is restored.

    Was this answer helpful?

    0 comments No comments

  3. PascalMenard 0 Reputation points
    2026-09-08T19:50:17.42+00:00

    We actually only have one user affected by this. The problem appear for the user when connecting online to "https://m365.cloud.microsoft" and we are two IT staff members who have reproduce it by opening a session with this user account in a private browser on our own computer. I don't think the folder is the problem here.

    Was this answer helpful?

    0 comments No comments

  4. David Oldright 0 Reputation points
    2026-09-08T18:46:26.82+00:00

    Sign in as a different ADMIN account on the local PC. Go to the affected account profile in C:\users\APPDATA\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy Rename this folder. Log off and back on as affected user.
    It should work. This appears to be caused by a token error that is not always visible to fix in Windows Credential Manager.
    This way I didnt have to wait for MSFT....:D

    Was this answer helpful?

    0 comments No comments

  5. David Oldright 0 Reputation points
    2026-09-08T18:45:23.89+00:00

    Sign in as a different admin account.
    Go to the affected account profile in users.
    APPDATA\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
    Rename this folder.
    Log off and back on as affected user.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.