Azure DevOps Connector - 'Failed to Find Project'

Ilias el Matani

Introduction

Recently, while initiating a new project for an organization, I encountered an issue with the Azure DevOps Connector in Microsoft Teams that hindered the connection between the two platforms. This article delves into the background of this problem and offers a solution.

Identifying the problem

The issue arises when attempting to link Azure DevOps Connector with Microsoft Teams to receive project activity notifications. The process fails with an error message: "failed to find project for this organization," preventing the visibility of projects when configuring Azure DevOps Connector in Microsoft Teams.

Third-Party application access

This problem typically stems from the "Third-party application access via OAuth" policy within Azure. By default, this policy is turned off for all new organizations. This policy regulates the access of third-party applications to your organization's resources through OAuth.

The solution: enabling OAuth access

To resolve this, enable the "Third-party application access via OAuth" setting. Here's the method to follow:

  1. Navigate to Organization Settings: Go to your Azure DevOps organization settings.
  2. Access Policies: Locate the "Policies" section.
  3. Enable OAuth Access: Find and enable the "Third-party application access via OAuth" option.
  4. Reattempt Connection: Once this setting is enabled, try connecting Azure DevOps Connector to Microsoft Teams again.
  5. Connector Azure DevOps: Notifying Project Activities

With the OAuth policy enabled, the Azure DevOps connector in Microsoft Teams should function correctly, allowing you to:

  • Choose relevant accounts and organizations.
  • Receive notifications about activities in your projects seamlessly.

Conclusion

This can be fixed by enabling the necessary policy.