Unable to subscribe to Office 365 IMAP folders from MUA since 2022-11-01

Anonymous
2022-11-02T07:33:01+00:00

I'm using Thunderbird to access my Office 365 mail account and it has been working fine (a couple of month ago I also switched to OAuth2 due to deprecation of basic IMAP authentication). However, since 2022-11-01, Thunderbird is unable to subscribe to IMAP folders. Last time I know it was working was last Friday 2022-10-28. Thunderbird is able to list to available folders (e.g. when opening the "Subscribe" dialog from the mail account settings), but cannot subscribe to them. I enabled IMAP logging in Thunderbird, and it shows that the server answer the subscribe request with "BAD SUBSCRIBE".

It is not a password/authentication issue, as Thunderbird can still see the content of "Inbox" and "Deleted Items". And if I disable the option "Show only subscribed folders", it can access everything in my Office 265 account.

Edit: here's the relevant logs from Thunderbird (note: I've replaced the actual folder name with "xxxx"):

[Parent ...: IMAP]: I/IMAP ...:outlook.office365.com:A:SendData: 76 subscribe "INBOX/xxxx"

[Parent ...: IMAP]: I/IMAP ...:outlook.office365.com:A:CreateNewLineFromSocket: 76 BAD SUBSCRIBE failed.
Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

106 answers

Sort by: Oldest
  1. Anonymous
    2023-01-01T08:42:43+00:00

    A handful of affected people per tenant as you are seeing, appears reasonably typical - and that is why service desks and SAs might genuinely think it's a user/local issue, and probably why Microsoft tried to claim that in the early days.

    However, I think we are now well past the point where Microsoft have had to admit there is server-side fault/bug/mis-configuration - and IMO, we reached that point on the 23rd November when their own test script issued to me exhibited the same issues as the various affected MUAs. But Microsoft have still refused to declare the incident openly on Service Health (it deserves at least an ADVISORY given it is clearly affecting customers right across Europe), and there is certainly evidence of 1st line Microsoft people pushing back on reports after that date which is completely unacceptable given the amount of evidence in this thread.

    Regardless of whether Microsoft have finally acknowledged this in various updates to individuals, my advice to SAs still stands that you should raise your own ticket.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-01-12T07:57:03+00:00

    First I want to thank everyone who has collaborated on pinning down this issue. This bug is stalling our organization's migration from G Suite to Office 365, since forcing every user onto the Outlook desktop app is not an option for us.

    I have opened a support ticket with Microsoft pointing to this thread, requesting to be notified when the bug has been fixed.

    1. Am I correct that there is currently no known work-around to this bug?
    2. Is this bug acknowledged by MS and listed on some public bug tracker or similar where progress may be monitored?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-01-12T11:54:41+00:00

    Hello! To your questions:

    1. The fundamental 'workaround' is to use Outlook for the Web. No client but a browser is needed for that. If you must use an IMAP client, e.g. Thunderbird, then disabling the option that shows only subscribed folders is a workaround.
    2. Yes, the bug is acknowledged by Microsoft, but not publicly, i.e. it has not yet been listed in the Service Status section of the Microsoft 365 Admin Center.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-01-12T13:21:03+00:00

    First I want to thank everyone who has collaborated on pinning down this issue. This bug is stalling our organization's migration from G Suite to Office 365, since forcing every user onto the Outlook desktop app is not an option for us.

    I have opened a support ticket with Microsoft pointing to this thread, requesting to be notified when the bug has been fixed.

    1. Am I correct that there is currently no known work-around to this bug?
    2. Is this bug acknowledged by MS and listed on some public bug tracker or similar where progress may be monitored?

    From what we collectively know about the issue, it's highly unlikely it will affect "every user" you migrate. It will likely just be a small percentage of them - but there is no way of knowing in advance what percentage and which ones as we don't know what is actually causing it yet (and neither it seems, do Microsoft).

    As David L says, there is a relatively simple (one tick-box) workaround for affected Thunderbird users, but if you plan to use some other IMAP mail client, you'd need to look at whether there is equivalent functionality in the settings of that product to override IMAP Subscription, which is the bit that is broken for affected users.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-01-17T07:46:36+00:00

    Thank you for mentioning the Thunderbird workaround!

    I was contacted by Microsoft support who claimed that IMAP is no longer supported since Jan 1 2023. I cannot find any mention of it online, perhaps the representative was refering to IMAP Basic Auth being deprecated. https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-deprecation-in-exchange-online-september/ba-p/3609437

    Was this answer helpful?

    0 comments No comments