# Azure PR's automated comments

**URL:** <https://community.sonarsource.com/t/azure-prs-automated-comments/125524>\
**Category:** SonarQube Cloud\
**Tags:** pull-request, azure-devops, sonarqube-cloud\
**Created:** [September 20, 2024, 11:29am UTC](https://community.sonarsource.com/t/azure-prs-automated-comments/125524 "2024-09-20T11:29:15Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![NCMarcus](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ncmarcus/32/61978_2.png) [@NCMarcus](https://community.sonarsource.com/u/NCMarcus)\
**Post date:** [September 20, 2024, 11:29am UTC](https://community.sonarsource.com/t/azure-prs-automated-comments/125524/1 "2024-09-20T11:29:15Z")

</div>

Hey,

We have recently implemented SonarCloud in builds with azure devops. It is all working just fine, comments are added to the Pull request and everything.

HOWEVER, everytime a new commit to a started PR comes, we rebuild and do a new analysis. When this is done, all the PR comments are removed and re-added, so even if we change status in the previous commit, or made comments it removes it.

This is causing a lot of headaches as we try to write comments or changing the status on things accordingly, as we might ignore some of the things for the current PR and might resolve it at a later time. And as we got FORCE all comments to be resolved before merging can be done, it gets a little problematic when it re-applies all the comments after validation builds were completed.

But also, we are getting SPAMMED by emails which gets a bit annoying overtime.  
Is this a known limitation at this point in time, and is there something being worked on to resolve this. Or is there something we can do to adjust/fix this?  
If there is nothing planned or so yet, can we get a feature request for this that we can track, because we really want this resolved.

---

<div class="post-metadata">

**Author:** ![NCMarcus](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ncmarcus/32/61978_2.png) [@NCMarcus](https://community.sonarsource.com/u/NCMarcus)\
**Post date:** [October 7, 2024, 2:37pm UTC](https://community.sonarsource.com/t/azure-prs-automated-comments/125524/3 "2024-10-07T14:37:13Z")

</div>

Ping - anyone knows a way forward here?

---

<div class="post-metadata">

**Author:** ![alexander.rage](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/alexander.rage/32/49178_2.png) [@alexander.rage](https://community.sonarsource.com/u/alexander.rage)\
**Post date:** [October 8, 2024, 4:52pm UTC](https://community.sonarsource.com/t/azure-prs-automated-comments/125524/4 "2024-10-08T16:52:24Z")

</div>

Hi Marcus

Sorry for the late answer. Indeed we are aware that the notification experience on Azure DevOps PRs could be improved. We are currently evaluating a way to have a short-term solution. It is on our radar.

Many thanks.

Best

Alexander

---

<div class="post-metadata">

**Author:** ![NCMarcus](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ncmarcus/32/61978_2.png) [@NCMarcus](https://community.sonarsource.com/u/NCMarcus)\
**Post date:** [September 10, 2025, 1:39pm UTC](https://community.sonarsource.com/t/azure-prs-automated-comments/125524/6 "2025-09-10T13:39:34Z")

</div>

Hey again Alexander or someone else on the sonarqube team that sees this,

Any progress regarding this? Or still not prioritized on the roadmap?

---

<div class="post-metadata">

**Author:** ![NCMarcus](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ncmarcus/32/61978_2.png) [@NCMarcus](https://community.sonarsource.com/u/NCMarcus)\
**Post date:** [September 18, 2025, 7:18am UTC](https://community.sonarsource.com/t/azure-prs-automated-comments/125524/7 "2025-09-18T07:18:42Z")

</div>

_bump_

---

<div class="post-metadata">

**Author:** ![NCMarcus](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ncmarcus/32/61978_2.png) [@NCMarcus](https://community.sonarsource.com/u/NCMarcus)\
**Post date:** [September 24, 2025, 11:24am UTC](https://community.sonarsource.com/t/azure-prs-automated-comments/125524/9 "2025-09-24T11:24:01Z")

</div>

Bump (still wondering about the progress)

---

<div class="post-metadata">

**Author:** ![NCMarcus](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ncmarcus/32/61978_2.png) [@NCMarcus](https://community.sonarsource.com/u/NCMarcus)\
**Post date:** [October 30, 2026, 10:56am UTC](https://community.sonarsource.com/t/azure-prs-automated-comments/125524/12 "2026-10-30T10:56:18Z")

</div>

Any updates regarding this?

---

<div class="post-metadata">

**Author:** ![andres](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/andres/32/76342_2.png) [@andres](https://community.sonarsource.com/u/andres)\
**Post date:** [November 2, 2026, 4:31pm UTC](https://community.sonarsource.com/t/azure-prs-automated-comments/125524/13 "2026-11-02T16:31:42Z")

</div>

Hi @NCMarcus, unfortunately this doesn’t seem to have caught much traction, most likely because we don’t hear about if from users too often. If this request becomes more common in the future, it’s possible that we will re-open this thread. For now, it doesn’t seems like our PMs have any meaningful updates for you.
