Error code 23201 on Linked Service Sharepoint on Data Factory

Romano, (Fabrizio) 25 Reputation points
2023-07-26T02:17:35.9266667+00:00

Hello, we are experiencing an issue with Data Factory Linked Service.

The SharePoint Online List Linked Service connection failed around a week ago. We never had this issue before, connection just failed suddenly. We already ensured that the Service Principal havs authorization to read the Sharepoint source, so it shouldn't be an authorization problem. In fact, the Sharepoint Linked Service is working correctly for other Sharepoint sites, just not for this specific source.

Could you please help me figure it what to do to solve this? Thank you.

User's image

Failed to get metadata of odata service, please check if service url and credential is correct, and your application has permission to the resource. Expected status code: 200, actual status code: Conflict, response is: 


  
    
    
  
  
    <div>
      <p>Request Error</p>
      <p>The server encountered an error processing the request. See server logs for more details.</p>
    </div>
  
. 
 Activity ID: 212cdd00-01a7-43ef-be5c-f7125d34d8a9.
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
11,623 questions
{count} votes

1 answer

Sort by: Most helpful
  1. AnnuKumari-MSFT 34,556 Reputation points Microsoft Employee Moderator
    2023-07-27T15:11:41.8766667+00:00

    Hi Romano, (Fabrizio) ,

    From the experiencing an issue with the SharePoint Online Linked Service connection on Azure Data Factory.

    You need to provide the App permission to Sharepoint on site level. You might have given SharePoint Online site permission to the registered application for the main site, but probably not for the subsite.

    If you have Admin access to Sharepoint then you can provide access to Service Principal

    If you need to do if programmatically then you can use below XML: <AppPermissionRequests AllowAppOnlyPolicy="true"> <AppPermissionRequest Scope="http://xxxxxxx" Right="Read" /> </AppPermissionRequests>

    The other possible reason could be that the particular site has been moved under a private network. Kindly check the same, in case it is so, then you need to use Self hosted IR insted of Autoresolve integration runtime.

    Hope it helps. Kindly let us know how it goes. Thankyou

    1 person found this answer 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.