Microsoft ODF Plugin Story Gets...Richer

When I wrote about Microsoft's announcement that it would be sponsoring a project to create an ODF plugin for its Office product, I said the story was big. But I was wrong: it's actually really big, because of a deeply ironic twist to the story, detailed on Groklaw:

It seems that when Microsoft was looking to build its new ODF plugin, it took a short cut. It seems to have grabbed some code from the OpenDocument Fellowship's program that converts ODF to HTML, written by J. David Eisenberg. His code is released under a dual license, the LGPL and the Apache 2.0 license. Microsoft has put it into its ODF plugin, which is licensed under the BSD license.

Is that allowed? It's nice Microsoft endorses the value of the ODF Fellowship code, since they are forever telling us their own code is better. But we're trying to parse out which license Microsoft thinks it is complying with. Not the LGPL, I trust. My question, and I'm no Apache guru, is what about Apache sections 4.1, 4.2, 4.3, and maybe 4.4, plus the required form of notice in the Appendix? It's certainly possible I'm missing something. But it seems it may be Microsoft that neglected to notice some requirements.