On my M365 Outlook, which is on my work system, I added my Hotmail account just to see if it worked better. It was added via both methods of auto discovery and manually creating it as EAS and I was still getting the prompts in both cases. The connection status showed my work account under "Bearer*" and Hotmail under "Clear*". The prompt was so frequent and as I mentioned in another comment, it would take away the cursor/pointer focus suddenly, resulted in my workflow being constantly disrupted, so I removed the account to gain back my productivity. I did add it back a few times to see if things progressed differently, but was still getting the prompt.
I also spoke to our IT folks (pretty friendly with them), and they have no desire to work on my personal account issue as they are knee deep in other MS related issues such as problems from the recent Patch Tuesday rounds.
Just to be clear, my Hotmail issue was never with IMAP or POP3. I do not use those protocols with Hotmail. I always set the account as Exchange/EAS or Outlook.com. To be frank, I've noticed Outlook.com account type to be slower. Exchange type on desktop and EAS on mobile were the gold standard for fast and accurate sync and it was the case up until 1/23/2024. I do use POP3 for non-Microsoft mail and it has been fine during this period. POP3 and offline PST is an important consideration for me.
Also, I pored through your peers' postings on "New Outlook", including people claiming they are product manager for Outlook. What was said is that POP3 and PST are in the plan. However, no firm date and comment that address the elephant in the room, of using Microsoft cloud as proxy to access and store non-Microsoft 3rd-party data. I honestly don't know how POP3/PST and proxy architecture means for each other and its scary to even think about this. Is Microsoft cloud will suck up the entire PST during its processing for import in the future and POP3 will also morph into a proxy architecture? None of this is clear enough... But I will leave it to regulators in EU to address that issue with Microsoft.