Yes, this is precisely why this issue is in Microsoft’s court and requires Microsoft to take action. Users should not need to be aware of IPv6 and IPv4. Putting out a broken service on IPv6 is more harmful to the efforts to transition away from IPv4 than keeping a service IPv4-only.
You do have one option: you can create multiple profiles in Thunderbird. It is annoying and prevents you from copying between folders which are on servers with different IPv6 requirements.
You also have another option (which I have not tried). You might be able to add an IPv4-only entry to your hosts file for outlook.office365.com. This should prevent Thunderbird from trying to access the IPv6 endpoint. You will need to remember to remove this once Microsoft fixes this issue or to update it whenever Microsoft updates their DNS records. In a similar vein, if you control your local network infrastructure, you might be able to use something like dnsmasq to do this for all your local devices. It might even have an option to proxy DNS results but filter out IPv6 results for specific hosts (I mean, such an option would be useful here and this is the sort of thing I expect that tool to provide, though maybe it is global only, etc., but I have not checked its documentation).