Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The GitHub Server Knowledge connector integrates GitHub Enterprise knowledge into Microsoft 365, allowing Copilot and Microsoft Search to surface relevant wiki pages, Markdown files, and blogs. This article provides troubleshooting information for common errors that you might encounter when deploying or indexing data with the connector.
To verify GitHub configuration information to help troubleshoot errors, see Set up the GitHub service for connector ingestion.
GitHub Server Knowledge connector troubleshooting
The following table lists common errors and troubleshooting steps.
| Scenario | Error | Resolution |
|---|---|---|
| GitHub app not installed in target organization during test authentication | The GitHub app isn't installed in the selected organization. | Install the GitHub app in the organization settings before authorizing. |
| No GitHub organizations detected for OBO authentication during test | No organizations were found for the provided credentials. | Install the GitHub app in your organization's settings before authorizing. |
| Token retrieval failed during test authentication | Unable to obtain an access token. | Verify and update your credentials. |
| Missing required GitHub app permissions detected during test authentication | Missing required permissions. | Be sure to grant all required GitHub app permissions. For details, see Use a custom GitHub app for authentication. |
| Test authentication request blocked by IP restriction | The request was blocked due to IP restrictions. | Add the GCS computer IP address to the allow list. |
| Invalid authentication type selected during connection creation | Invalid authentication type selected. | Use a supported authentication type. |
| No searchable items found when previewing content | Preview returned no results. | Make sure that at least one searchable item exists. |