IMO… Ask to Microsoft.
Ask them to support standard protocols like caldav and cardav “by default”, without third part plugins. Maybe picking login details from the configured email account.
Ask them re-establish a full IMAP compliancy, so i can decide on Outlook which is my Sent, Trash, Spam, Inbox folder, and how the client should behave for deletion (moving, marking, hinding… any setting)
Don’t forget to ask them also to re-establish a full configurability for IMAP, POP3 and SMTP protocol, even for accepting only in the email client, if necessary, self-signed certificate if it’s not verified by compliant/authorized CA (and stopping for ask every single refresh of the mailbox, please!!!). As optional, of course, but without bashing 8 time the head against a wizard that keeps telling “you fool, are you not using Microsoft 365 or Exchange? How miserable you are?”. Just a button “i want to fully configure my email client” without scavenging into Control Panel… Which is going to be MIA from Microsoft soon, into Windows 10.
As default, international and compliant field mapping (including export .CSV proper way, not transposed) for address book, and message prefixes. In Italy, Outlook “wish” to translate Reply with Risposta, Forward with Inoltro. It sucks in so many ways since Schedule+ that i can’t contain my rage about that.
And i should not indulge too much on “bare LF” bad habit. Could lead to meltdown more than RTF Formatting as default or Winmail.dat attachment embedding.
These things should be default and easy to access. Simply, by default RFC Compliant.
I’m personally not asking for client managed sieve rules, currently they don’t work even with plugin for Thunderbird. But at least a real RFC Email client…
Ok, my post seems a quite… loaded with hatred series of requested. They may be not.
If you don’t ask to Outlook to behave like a compliant email client it will work great. Pair it with Exchange and/or Microsoft365 and it can give a lot of satisfaction to the user… I mean… editing rules from client and applied to the server? Wonderful! It’s simple, but it can do a lot of wonderful things even when it’s not opened on a computer.
When you ask some interoperation with other (non Microsoft) software and services… there start the madness. Once there was MAPI library, so at least you could tell to Outlook “do this” (hoping that the version dialect was not so messed up at the next release) and something came out… Nokia Suite, still missing you. You were so nice to talk with all that PIMs…
People wants Microsoft? Ok. Buy Microsoft. Client, and server. Or… stop buying Microsoft, asking them a software that can relate with RFC standards.