Error responses in Microsoft 365 Copilot connectors

The UI displays a limited number of connection errors. For a comprehensive list, follow these steps to generate a detailed error report using a PowerShell script.

1. Open Windows PowerShell with administrator rights.

2. Install the script from the PowerShell gallery using the following command

       Install-Script -Name DownloadErrorScript
   

   With this script, you can download the item errors from a Microsoft 365 Copilot connector connection. It generates an MSAL token using the tenant credentials associated with the connection. The installation of the script automatically includes the MSAL.PS module. If this doesn't occur, install the module manually with

       Install-Module -Name MSAL.PS
   

For more information, see Download error script.

3. After installation, execute the script

       DownloadErrorScript.ps1
   

4. Provide the connection ID of the connection for which you want to download the error report.

5. Specify the name for the output file without extension (without extension, the default is .csv).

6. Define the batch size for downloading errors. Larger batches are suitable for thousands of errors to minimize data retrieval time, but may increase the likelihood of failures. The maximum batch size is 5000 errors. Once logged in using your tenant account, the download process begins.

7. Depending on batch size and error count, the download duration varies. The generated file is saved in the script's execution path with the specified name.

   

Monitor errors

To monitor errors, go to Connectors > Active Connector. Any existing crawl errors are displayed under Current Crawl > Errors. This section provides:

• Error codes - Lists the various error codes encountered.
• Count - Displays the number of occurrences for each error code.
• Error log download - Offers options to download the error log.

To view detailed information about a specific error, select the corresponding error code.

The following list shows the different errors that can appear with any connection.

Error code	Error message	Solution
1000	The data source isn't available. Check your internet connection or make sure the data source is still accessible by the connector.	This error occurs when the data source isn't reachable due to a network issue or when the data source itself is deleted, moved, or renamed. Check if the data source details provided are still valid.
1001	Can't update the data because the data source is throttling the connector.	To unthrottle the data source, check if its scale limits can be increased or wait until a less traffic-heavy time of the day.
1002	Can't authenticate with the data source. Verify that the credentials associated with this data source are correct.	Select Edit to update the authentication credentials.
1003	The account associated with the connector doesn't have permission to access the item.	Ensure the proper account has access to the item you want indexed.
1005	Credentials associated with this data source have expired. Renew the credentials and update the connection.	Select Edit to update the authentication credentials.
1008	The total quota utilization of your tenant has reached its limit.	Try deleting a connection to free up some of your quota or adjusting your ingestion filters to bring in less data. If these steps don't solve the issue, contact Microsoft support.
1009	The total quota utilization for your connection has reached its limit.	Try adjusting your ingestion filters to bring in less data. If this step doesn't solve the issue, contact Microsoft support.
1010	The total quota utilization for indexing non-Azure AD groups has reached its limit of 100 K.	Try deleting a connection to free up some of your quota or adjusting your ingestion filters to bring in less data. If these steps don't solve the issue, contact Microsoft support.
1011	The Graph Connector Agent isn't reachable or offline.
1012	Authentication to your connection failed due to an unsupported authentication mode.	Edit the connection to update the authentication settings for your connection.
1015	Connections created on this agent will fail due to insufficient permissions. Grant the ExternalItem.ReadWrite.OwnedBy permission to the Microsoft Azure app used for registration to allow the app to read and write all external items without a signed-in user and resume the crawl.	Ensure that the Azure app used for Agent registration has ExternalItem.ReadWrite.OwnedBy permission.
1016	Connections created on this agent will fail due to insufficient permissions. Grant the Directory.Read.All permission to the Microsoft Azure app used for registration to read data in your organization's directory and resume the crawl.	Ensure that the Azure app used for Agent registration has a Directory.Read.All permission.
1017	Item can't be indexed because the network is unavailable.	Restore the network and wait for the next crawl for the item to get indexed.
1018	Please ensure that the entered user account has interactive logon rights to the machine where the Graph Connector Agent is installed.	Ensure that the user account has interactive logon rights to the machine where the Microsoft 365 Copilot connector agent is installed. Refer to the documentation to learn more.
1019	Connection failed because the app credentials given to the Microsoft 365 Copilot connector instance are invalid or expired. Please update the credentials.	Check your app credentials for the Microsoft 365 Copilot connector instance associated with the connection.
1020	The Graph Connector Agent associated with the connection is not able to connect to GRPC connector server.	The GCA instance could not crawl the data source as there was an issue with connecting to the custom connector over GRPC.
1025	The Graph Connector Agent associated with this connection is deprecated due to critical issues. Upgrade to the latest version. Learn more: https://aka.ms/gca	Upgrade your Graph Connector Agent version by downloading the latest version from https://aka.ms/GCAdownload|
1026	The connection has failed due to a critical issue with the associated Graph Connector Agent. Upgrade to the latest version or contact support to resolve the issue. Learn more: https://aka.ms/gca	Upgrade your Graph Connector Agent version by downloading the latest version from https://aka.ms/GCAdownload|
2001	Indexing is throttled because of a large number of updates in the queue. Depending on the queue, it can take some time for the updates to complete.	Wait until the queue gets cleared.
2002	Indexing failed due to unsupported item formatting.	For more information, see the connector-specific documentation.
2003	Indexing failed due to unsupported item content.	For more information, see the connector-specific documentation.
2004	Indexing failed due to unsupported item or file size.	For more information, see the connector-specific documentation.
2005	Indexing failed because the URI is too long.	For more information, see the connector-specific documentation.
2006	User mapping failed due to an invalid mapping formula or no Microsoft Entra user with this property.	Try deleting and recreating the connection with a different mapping formula.
2007	This item won't be displayed in Microsoft Search because some users or groups without permission to view this item couldn't be indexed.
2008	Connections can't have non-Azure AD groups with more than 50,000 members.	Try removing users from a group or try removing items ACLed with that group from ingestion and recreate the connection.
2009	Non-Azure AD group indexing is temporarily paused due to a large number of requests. Indexing resumes when the system finishes processing these requests. Check back later.
2010	This connection is no longer valid because of an update made by Microsoft.	Delete the connection and create a new one.
5000	Something went wrong. If this issue continues, contact support.