Hi @Ammo,
Sorry to intrude on this topic but I believe both the problems @ghaouim and @DGUCOM (not sure if Azure DevOps is being used in that situation) are experiencing might be related to the issue I reported last week.
I tried using SonarCloud with Azure DevOps and observed that the pipeline extension doesn’t provide the MSBuild scanner with a value for the organization where the quality profile has been created on.
The end result being that the scanner always uses the default Sonar way quality profile when performing the analysis.
As stated in said issue I couldn’t determine a work around for this.
Also my apologies if I end up being wrong in my assumption.