We are still seeing some inconsistency with the coverage statistics that are generated from Azure DevOps and what is tracked by SonarCloud. An example of this can be seen below.
Azure DevOps (Downloaded from the code coverage tab saved against the build):
When I download the code coverage file from Azure DevOps I can see differences in what is reported versus what is actually covered. We haven’t set up any specific file paths to ingest the coverage from, and I assumed that SonarCloud used the same output from Azure DevOps.