I am trying to pull Sharepoint list into SDP using Pipeline but getting error

Lohot, Abhishek 0 Reputation points
2025-04-25T16:02:48.5566667+00:00

I am trying to pull Sharepoint list into SDP using Pipeline but getting error :

List Name : 333 Backlog Tracker

Requesting response from path 333 Backlog Tracker and query $top=10 failed with status code NotFound and message <?xml version="1.0" encoding="utf-8" standalone="yes"?> <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"> <code></code> <message xml:lang="en-GB">Resource not found for the segment '333 Backlog Tracker'.</message> </error>

(Although I able to fetch list at same shairepoint location with another name : Query MPANS)

I have tried everything all the combination of List name for '333 Backlog Tracker'

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
11,464 questions
{count} votes

2 answers

Sort by: Most helpful
  1. J N S S Kasyap 1,715 Reputation points Microsoft External Staff
    2025-04-25T16:47:15.1433333+00:00

    Hi @Lohot, Abhishek

    It looks like you're running into an issue while trying to pull a SharePoint list named "333 Backlog Tracker" into SDP using a pipeline. The error message indicates that the resource can't be found for that specific segment.

    Here are a few things you can check to troubleshoot the issue:

    1.      Double-check the exact name of the SharePoint list. Sometimes, even small discrepancies or extra spaces can cause issues. Since you mentioned you can pull another list ("Query MPANS"), ensure that the name "333 Backlog Tracker" is spelled and formatted exactly the same.

    2.      If you have an OData feed, be aware that there is a character limit (roughly 2100 characters) for the URL. Make sure your request does not exceed this limit.

    3.      Ensure that your linked service to the SharePoint list is correctly configured. You might want to verify the authentication method and permissions granted to the application you're using to access SharePoint.

    4.  When connecting, ensure that you're using the root address of your SharePoint site without any subfolders. For example, it should look like https://yourtenant.sharepoint.com/sites/yoursite/.

    5.   Ensure that the account or service principal you are using for authentication has the necessary permissions to access the "333 Backlog Tracker" list.

    6.      Use the 'Test Connection' feature in your Synapse workspace to ensure that your linked service settings are correct and that it can successfully communicate with the SharePoint site.

    I hope this information helps. Please do let us know if you have any further queries.

    Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

    Thank you.


  2. Sina Salam 19,616 Reputation points
    2025-04-29T16:46:52.48+00:00

    Hello Lohot, Abhishek,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    I understand that you are trying to pull Sharepoint list into SDP using Pipeline but getting error.

    This might be more than the common error resolved above. In addition to @J N S S Kasyap response. For common issues and troubleshooting, also steps for special characters, health checks, and logs check the following links:

    1. Therefore, SharePoint uses an encoded internal name for lists with spaces or special characters. Check the URL: The List= parameter shows the internal name (e.g., %7B12345678%2D90AB%2D...%7D). Decode it using a URL decoder or copy it directly - https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/working-with-lists-and-list-items-with-rest#constructing-list-and-list-item-urls
    2. Secondly, replace the display name with the internal name in your ADF pipeline. For example: Instead of 333 Backlog Tracker, use 333_x0020_Backlog_x0020_Tracker or the GUID to https://{site-url}/_api/web/lists/getbytitle('333_x0020_Backlog_x0020_Tracker')/items?$top=10
    3. Check this link for more info - https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/complete-basic-operations-using-sharepoint-rest-endpoints#retrieve-all-lists-in-a-site
    4. Then, test the endpoint outside ADF to isolate the issue by paste the URL into a browser or Postman (authenticate if needed). If it fails, the internal name is incorrect - https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/troubleshooting-sharepoint-rest-calls
    5. If using the display name, encode spaces as %20: for an example - https://{site-url}/_api/web/lists/getbytitle('333%20Backlog%20Tracker')/items?$top=10
    6. Check that the linked service configuration in ADF uses:
      1. Site URL: https://{tenant}.sharepoint.com/sites/{site} (no subfolders).
      2. Authentication: Azure AD Service Principal with Sites.Read.All permissions.
      https://learn.microsoft.com/en-us/azure/data-factory/connector-sharepoint-online-list#linked-service-properties
    7. Finally, if the internal name/encoding resolves the issue, the pipeline will fetch data. If not, recheck permissions and ensure the list is not hidden or part of a subsite.

    I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.


    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.