Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

GitHub Could not create service hooks subscription Unable to configure a service on the selected GitHub... Resource not accessible by integration

When I try to update the environment variables on an Azure DevOps release pipeline, I get the error below.

GitHub Could not create service hooks subscription Unable to configure a service on the selected GitHub repository. GitHub returned the error 'Resource not accessible by integration'.

I am an admin on the GitHub repo.

In Get sources, it is currently configured for a GitHub OAuth Service Connection. Another user is able to update the environment variables. I am using GitHub (not enterprise).

Is this an Azure DevOps permission that I do not have?

GitHub Could not create service hooks subscription Unable to configure a service on the selected GitHub repository. GitHub returned the error 'Resource not accessible by integration'.

like image 616
Hoppe Avatar asked Jan 17 '26 08:01

Hoppe


2 Answers

After working with ADO tech support, it was discovered that we needed to remove the artifact and trigger definition from the release pipeline, and then re-add it. It is believed that there was cached service connection, and this updated the pointer to the correct service connection.

like image 157
Hoppe Avatar answered Jan 20 '26 03:01

Hoppe


Is this an Azure DevOps permission that I do not have?

This error message usually comes with GitHub App installation token service connection.

Go Project Settings => Service Connections to check the details of the specific service connection. If your service connection is GitHub App installation token based service connection, then it's expected behavior to meet that issue. Our team are working on adding that support so far, please check this ticket.

enter image description here

Workaround:

1.Create a new service connection with OAuth/PAT method and use it in your pipeline. Since you're admin of the github repo, a Github PAT is more recommended.

2.If you have permission to the service connections and to the pipeline, this issue won't occur. Ask your Azure Devops project admin to via manage security.

like image 27
LoLance Avatar answered Jan 20 '26 03:01

LoLance