Managing personal Outlook.com account settings, security, and privacy
I think the quotes around the name in the From header were the main issue for me. When I still got the bounce after I had already made that change, I looked carefully at all the headers again, trying to find anything unusual about those that get signed. I removed the final semicolon at the end of the boundary string in Content-Type, since it is not needed there, but except for that, everything seemed absolutely fine.
A few days later, I suddenly realised I did not see any new bounces of this kind for a while. When I checked my DMARC reports, I found several reports with "DKIM=pass, SPF=fail". All of those used to fail their DKIM checks, too, and would end up rejected. Now they cause a warning about SPF, but are delivered just fine. I do not know if the issue with the quoted email was really as silly as an extra semicolon that somehow was removed before validation, if there was a DNS refresh issue with my DKIM keys for that particular recipient, or if Microsoft finally patched something that had not yet made it to iomartcloud.com.
In any case, it seems for me, the vast majority of the bounces were indeed caused by the quotes, which Microsoft decided to add to the From header after I had signed it, and before their software validated the signature. (I really have no idea why they think this is in any way acceptable behaviour for email software.) Since nobody else did such a thing, DKIM validation of my emails only failed on Outlook Enterprise servers.
If you share the headers of a message that bounced, I can offer you a second set of eyes to go over them. Maybe you also have something in them that Microsoft decided it needs to tweak a bit before checking the signature.