If without any plugin or extension support, until now, the HTML report would not be compiled successfully, then map corresponding attributes into pipeline directly. As you know, until now, it only support the format: TRX, JUnit, NUnit2, NUnit3, xUnit2, CTest.
As work around, you can define your customized extension. With this extension, add one new section into pipeline first, use task to publish this HTML report into this new section, then map and display its attributes into this section.
There has a sample extension can for you refer to: vsts-publish-html-artifact.
Note:
Since this extension programmed 4 years ago and no longer maintained now, also most of our official doc content has been updated with the latest grammar, such as categories and etc. I modify johnwalley's script, thus you can directly use it now. Due to my github repository: Merlin-Extension.
You can also extend the functionality of this extension by adding scripts based on your individual needs. Refer to this doc for extension script written: https://docs.microsoft.com/en-us/azure/devops/extend/get-started/node?view=azure-devops
The work around I provide above can only consider as a temporarily method. Since Xml reports are too basic and html is more useful in many cases/ tools, I also looking forward to the feature for HTML report Published in pipeline can be expanded into Azure Devops.
Here has a feature suggestion ticket exists on our official forum. We can vote and comment it there to make it has a broad community impact, also will improve the Azure Devops experience. Thus our product group will consider to take this feature into our develop roadmap.