Nuta
Dostęp do tej strony wymaga autoryzacji. Możesz spróbować się zalogować lub zmienić katalog.
Dostęp do tej strony wymaga autoryzacji. Możesz spróbować zmienić katalogi.
The GitHub Cloud Issues Microsoft 365 Copilot connector enables your organization to index GitHub issues so they can be surfaced in Microsoft 365 Copilot and Microsoft Search experiences. This article provides troubleshooting information for common errors that you might encounter when you deploy or use the connector.
To verify GitHub configuration information to help troubleshoot errors, see Set up the GitHub service for GitHub Cloud Issues connector ingestion.
GitHub Cloud Issues connector troubleshooting
The following table lists common errors and steps to resolve them.
| Error message or issue | Possible cause | Resolution |
|---|---|---|
| Authentication failed | Incorrect client ID, client secret, or private key used during setup. | Verify that the GitHub App credentials match the values in your GitHub App configuration. Regenerate the client secret if necessary. |
| SSO login not supported | Attempting to authenticate using single sign-on (SSO) during connector setup. | Sign in with a GitHub account that doesn't require SSO for configuration. |
| Insufficient permissions | GitHub App doesn't have the required permissions. | Make sure that the GitHub App has read-only permissions for Administration, Metadata, Issues, Members, and Email addresses. |
| Crawl failures after IP restriction | Firewall rules block connector IP ranges. | Add the connector’s IP ranges to your allowlist. For details, see Firewall settings. |
| Identity mapping errors | GitHub user identities don't match Microsoft Entra ID properties. | Configure identity mapping using email, sign in, or name. Use regex transformations if direct mapping fails. |
| Rate limit exceeded | Too many requests from a single GitHub user account. | Use separate user accounts for OAuth authentication to distribute API calls. |