Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
The SharePoint Server Microsoft 365 Copilot connector allows users in your organization to search for and reason over content stored in a SharePoint Server farm across Microsoft Search, Copilot Search, Copilot Chat, and declarative agents. This article provides troubleshooting information for common errors you might encounter when you deploy or use the SharePoint Server connector.
To verify setup information to help troubleshoot errors, see Set up SharePoint Server and Deploy the SharePoint Server connector.
Common errors
You might encounter the following errors when you deploy the SharePoint Server connector or when the connector indexes content.
| Deployment step | Error | Resolution |
|---|---|---|
| Setup | No Microsoft Graph connector agent available | No agent is registered to your tenant. Install and register the Microsoft Graph connector agent, and then refresh the agent list. For details, see Install and configure the Microsoft Graph connector agent. |
| Authentication | 401 Unauthorized | When using Microsoft Entra ID OIDC authentication, the ScopedClientIdentifier property is likely not set on the SPTrustedIdentityTokenIssuer.Run Get-SPTrustedIdentityTokenIssuer to check the current value, and then follow the steps in Configure the scoped client identifier. |
| Authentication | Authorization fails | Verify that the account has at least Full Read permission at the Web Application level in SharePoint Server. For the indexing account, we recommend full control or SharePoint Server farm administrator role. For details, see Configure authentication. |
| Authentication | Microsoft Entra ID OIDC authentication not working | Verify prerequisites: the Microsoft Graph connector agent must be version 3.1.2.0 or later, and SharePoint Server must be Subscription Edition patched to the November 2024 build (16.0.17928.20238) or later. For details, see Set up Microsoft Entra ID OIDC authentication. |
| Indexing | Items skipped during crawl | The indexing account doesn't have permission to the skipped items. Grant the account full control access at the Web Application level in SharePoint Server or make it a SharePoint Server farm administrator. |
| Indexing | Custom properties not appearing | Property names must exactly match the column names in SharePoint and are case-sensitive. The connector silently skips unrecognized property names. Also verify that you didn't exceed the 128-property limit, and note that custom properties aren't supported when multiple site collections are included in a single connection. |
| Post-indexing | Users can't see content in Copilot or Search | If you're using the Only people with access to the content in the data source permission mode, Active Directory identities must be synced with Microsoft Entra ID. For details, see Sync Active Directory to Microsoft Entra ID. |