As of February 2021, does EOP/Microsoft now send DMARC aggregate reports?

The DMARC reports from Microsoft are still broken.

1. RFC2045 clearly says that MIME Base64 lines should wrap at MAX 76 characters, not 78 (although 76 characters plus CRLF is 78 bytes, they send 78 characters plus CRLF, possibly because someone incorrectly used the general limit for mail in RFC5322, not the Base64 limit in RFC2045 section 6.6, which RFC5322 says overrides RFC5322 itself). Interestingly the .NET documentation at https://docs.microsoft.com/en-us/dotnet/api/system.convert.tobase64string?view=net-6.0 gets these numbers right.

2. They Base64 encode a us-ascii mime part, which is unnecessary and just a waste of disk space and network bandwidth.

3. Their cover letter mime-part tells recipient postmasters to send feedback to a specific dedicated address, but that address has been disabled and mail cannot be sent to it. Error is:
550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [DM3NAM06FT004.Eop-nam06.prod.protection.outlook.com]

4. The DMARC reports match a popular anti-spam filter suite (SpamAssassin) due to the above mistakes and one other mistake that I tried to tell them about, only to get that insulting bounce from their misconfigured feedback address.

DMARC reports are a feedback loop, and Microsoft managed to break both directions of that loop.