# Facing issue with Existing Azure DevOps organization integration with SonarCloud

**URL:** <https://community.sonarsource.com/t/facing-issue-with-existing-azure-devops-organization-integration-with-sonarcloud/133948>\
**Category:** SonarQube Cloud\
**Tags:** sonarqube-cloud\
**Created:** [January 23, 2025, 3:52pm UTC](https://community.sonarsource.com/t/facing-issue-with-existing-azure-devops-organization-integration-with-sonarcloud/133948 "2025-01-23T15:52:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Apeksha\_Haveri](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/apeksha_haveri/32/66128_2.png) [@Apeksha\_Haveri](https://community.sonarsource.com/u/Apeksha_Haveri)\
**Post date:** [January 23, 2025, 3:52pm UTC](https://community.sonarsource.com/t/facing-issue-with-existing-azure-devops-organization-integration-with-sonarcloud/133948/1 "2025-01-23T15:52:42Z")

</div>

We are currently facing an issue with our SonarCloud integration. An existing Azure DevOps organization has already been integrated into our SonarCloud account and the account was handled by an Ex-employee of our organization. As a result, we cannot create a new integration with the same Azure DevOps organization. I keep getting the below error message while trying to integrate.

Error - “This Azure DevOps organization is already bound” when trying to create my organization.

We kindly request the following:

1 Deactivation of the existing Azure DevOps organization integrated with SonarCloud.  
2 Assistance in understanding the root cause of this issue.  
3 Guidance on how to proceed with setting up the new integration with the existing Azure DevOps organization.

We would also like to discuss this matter in more detail if needed to ensure a smooth resolution.  
Please let us know if additional information is required.  
Looking forward to your prompt response.

Best regards,  
Apeksha Haveri

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [January 23, 2025, 3:59pm UTC](https://community.sonarsource.com/t/facing-issue-with-existing-azure-devops-organization-integration-with-sonarcloud/133948/2 "2025-01-23T15:59:11Z")

</div>

Hey there.

> [@Apeksha\_Haveri](#):
>
> 1 Deactivation of the existing Azure DevOps organization integrated with SonarCloud.  
> 2 Assistance in understanding the root cause of this issue.

For this, you should get in touch via the [SonarCloud Contact Form](https://www.sonarsource.com/products/sonarcloud/contact/).

> [@Apeksha\_Haveri](#):
>
> 3 Guidance on how to proceed with setting up the new integration with the existing Azure DevOps organization.

Once that’s sorted out, [the docs are your friend](https://docs.sonarsource.com/sonarqube-cloud/getting-started/azure-devops/)!

---

<div class="post-metadata">

**Author:** ![Apeksha\_Haveri](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/apeksha_haveri/32/66128_2.png) [@Apeksha\_Haveri](https://community.sonarsource.com/u/Apeksha_Haveri)\
**Post date:** [January 24, 2025, 3:20am UTC](https://community.sonarsource.com/t/facing-issue-with-existing-azure-devops-organization-integration-with-sonarcloud/133948/3 "2025-01-24T03:20:37Z")

</div>

Hi Colin,

Thank you for getting back to me. I have already reached out using the contact form you mentioned, but the response I received directed me to seek help from the community forum, as the SonarSource Dev teams can assist with the issue there.

Could you kindly guide me on how to proceed toward resolving this issue?

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [January 24, 2025, 3:26pm UTC](https://community.sonarsource.com/t/facing-issue-with-existing-azure-devops-organization-integration-with-sonarcloud/133948/6 "2025-01-24T15:26:08Z")

</div>

Hey there.

Sorry about that. There’s a distinction I didn’t realize in the process – when there’s a known SonarQube Cloud organization without any admins, those requests get routed through the contact forum to get resolved.

When there’s an unknown SonarQube Cloud organization is bound to an Azure DevOps org, it comes here so that we can take a look. So the folks at the other end of the contact forum sent you to the right place.

I’ve flagged this thread for some experts who should be along soon.

---

<div class="post-metadata">

**Author:** ![Apeksha\_Haveri](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/apeksha_haveri/32/66128_2.png) [@Apeksha\_Haveri](https://community.sonarsource.com/u/Apeksha_Haveri)\
**Post date:** [January 27, 2025, 5:17am UTC](https://community.sonarsource.com/t/facing-issue-with-existing-azure-devops-organization-integration-with-sonarcloud/133948/7 "2025-01-27T05:17:33Z")

</div>

Hi Colin,

Thank you for the clarification regarding the distinction in the process. I appreciate you routing this to the experts.

I just wanted to check in to see if there are any updates regarding this matter. If not, I kindly request that the process be expedited, as this is critical to address. Please let me know if you need any additional information or support from my end to move things along.

Looking forward to your response.
