# Code Coverage not showing in Sonar Cloud though coming in Code Coverage Tab under Azure Devops Pipeline

**URL:** <https://community.sonarsource.com/t/code-coverage-not-showing-in-sonar-cloud-though-coming-in-code-coverage-tab-under-azure-devops-pipeline/35751>\
**Category:** SonarQube Cloud\
**Tags:** maven, sonarqube-cloud, java, coverage\
**Created:** [December 11, 2020, 4:06am UTC](https://community.sonarsource.com/t/code-coverage-not-showing-in-sonar-cloud-though-coming-in-code-coverage-tab-under-azure-devops-pipeline/35751 "2020-12-11T04:06:19Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mickaelcaro](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/mickaelcaro/32/4147_2.png) [@mickaelcaro](https://community.sonarsource.com/u/mickaelcaro)\
**Post date:** [December 11, 2020, 9:12am UTC](https://community.sonarsource.com/t/code-coverage-not-showing-in-sonar-cloud-though-coming-in-code-coverage-tab-under-azure-devops-pipeline/35751/2 "2020-12-11T09:12:48Z")

</div>

Hi @neha_malhotra and welcome to the community,

The options field in the Maven task is definitely not a good place to put any properties for the SonarCloud analysis.

Prepare analysis configuration can be, but make sure you don’t put any -D in front of the property, you can simply put “sonar.coverage.jacoco.xmlReportPaths=/home/vsts…” in the additional properties field.

Make sure also that you don’t set that property twice, so either choose the pom.xml of the additional property fields, it will help you troubleshoot in that specific case.

HTH,  
Mickaël

---

_[View the full topic](https://community.sonarsource.com/t/code-coverage-not-showing-in-sonar-cloud-though-coming-in-code-coverage-tab-under-azure-devops-pipeline/35751)._