I am getting an error while trying to connect the Azure release pipeline and GitHub repos The problem is that I am not able to view the work that is linked to the artifact

Hi @Marco Mulondayi Tshimanga ,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Could you please try below troubleshooting steps and share your findings.

1. Check Your Connection: Make sure that your GitHub repository is correctly connected to Azure Boards. Sometimes, issues arise from changes in authentication credentials or permission scopes that restrict access. You can visit the GitHub settings through your profile to ensure Azure Boards has the necessary permissions.
2. Verify Organization Access:
   • Go to GitHub web portal, open Settings from your profile menu.
   • Under Applications, find Authorized OAuth Apps and look for Azure Boards.
   • Check if there are any access issues under Organization access and grant access if needed.
3. Connection Issues: If it appears that the connection might be invalid:
   • Remove the existing connection and try setting it up again. Sometimes the app might face disconnection issues, and starting fresh can resolve it.

   • As of April 23, 2025, the Azure DevOps OAuth app platform is no longer accepting new app registrations.

4. Verify Azure Boards ↔ GitHub connection
   • Confirm the GitHub repository is connected to the Azure Boards project (Project settings → GitHub connections) or that the Azure Boards GitHub app is installed and mapped to the correct Azure DevOps project and repository. If the GitHub app isn’t installed or repo mapping is wrong, commits/PRs will not be linked.
5. Make sure the build that produced the artifact actually has associated work items
   • Open the build that produced the release artifact (Pipelines → Builds → select the build). Check the build’s related work / development section to confirm work items are associated. If the build has no linked work items, the release artifact won’t show them.

Hi @Marco Mulondayi Tshimanga , following up to see if you had a chance to check the above response and it was helpful. Please let me know if you have any further questions.

This solution doesn't work at all

@Marco Mulondayi Tshimanga ,

Could you please try below and confirm:

Open the build that produced the artifact and click Associated work items

• If it errors there too, it is likely connection/permission issue
• If it works there but not in release, then it could be artifact config issue

@Marco Mulondayi Tshimanga , following up to see if you checked Pravallika's response and if it worked. If not please share requested information in Private messages to assist you further on this.