Regarding this post from last month - https://blog.thunderbird.net/2022/11/important-message-for-microsoft-office-365-enterprise-users/ - I am one of the likely millions of users affected by this, people who loathe Outlook passionately and love TB just as passionately (I donated!) I spun up a Windows Sandbox VM to confirm that the beta instructions w/ my work email function as written, and they do - I get the oauth2 window popup, I then get the new "permissions requested from Thunderbird by Mzla [sic] Technologies Corporation" (I guess Microsoft has a max length for the publisher name) popup, I press "accept" and everything is fine. Confident now that my actual workstation would behave just fine, I installed the current beta (109) side by side with my production 102 copy of Thunderbird, launched it with thunderbird.exe -P in order to tell the Beta version of TB to use my regular profile, and expected that once I deleted my old token from the saved passwords, I'd be given the same new Mzla Technologies Corporation prompt as my test sandbox was given. ...Except, I wasn't. Behavior in the 109 beta version of TB is the same as the original problem in 102: get the oauth2 prompt, put in my company username/password, then the box closes immediately, and does NOT show me the second popup like my test VM. The only difference now in this 109 beta, is that the oauth2 prompt immediately opens up again. If I try to click the X to close it, it instantly opens again. This behavior does not occur in 102. So my main hope is - '''is there some way besides deleting the entire account* saved in thunderbird, to clear the authentication credential information about this account in 109 beta, to hopefully get me to the same happy state that a fresh install put me in?''' *I have years of tags and special customizations done to this account in this profile. AFAIK, if I delete/remove the account from thunderbird and re-add it, I will lose all those customizations, yes?