Copy data from Sharepoint using Authorization: Bearer token getting status code 401 Unauthorized

Question

Copy data from Sharepoint using Authorization: Bearer token getting status code 401 Unauthorized

Prakash Palanivelu 0

ErrorCode=HttpRequestFailedWithUnauthorizedError,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Http request failed with status code 401 Unauthorized, usually this is caused by invalid credentials, please check your activity settings.,Source=Microsoft.DataTransfer.ClientLibrary,''Type=System.Net.WebException,Message=The remote server returned an error: (401) Unauthorized.,Source=System,'

Issue Analysis Status:

When I checked the “DEMO to SharePoint” Power Automate workflow, I noticed that the job was triggered successfully on last June 8, 2026.

Yesterday, I noticed that my account was linked to one of the Power Automate flows (SharePoint → ADF trigger). I re-authenticated and updated the credentials in Power Automate.

The flow is now triggering successfully from Power Automate, but the ADF pipeline is failing when it tries to connect to the Azure application DEMO-data123STG.

Please let me know if you have any suggestions on how we can proceed.

Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator

2026-09-03T11:54:24.9733333+00:00
Hi @Prakash Palanivelu

Thank you for the detailed information.

Based on the error message, the Power Automate trigger appears to be functioning correctly after the credential re-authentication. However, the Azure Data Factory pipeline is failing at the stage where it attempts to access SharePoint through the Azure application DEMO-data123STG, resulting in a 401 Unauthorized error.

To further isolate the issue, could you please verify the following:

Whether the client secret or certificate associated with the DEMO-data123STG application has expired or been recently rotated.

Whether the application still has the required permissions and admin consent to access the SharePoint site.

Whether the SharePoint linked service in ADF is using the latest credentials and can successfully pass the access token to the Copy activity.

If there were any recent changes made to the Azure App Registration, Key Vault secrets, or SharePoint permissions after the last successful execution.

Since the workflow trigger is succeeding and the failure occurs during SharePoint access from ADF, the issue is likely related to authentication or authorization of the Azure application rather than the Power Automate flow itself.

Please let us know the findings from the above checks, and we'll continue assisting with the investigation.
Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator

2026-09-04T16:52:33.9066667+00:00

@Prakash Palanivelu Just checking in to see if the information provided earlier was helpful. Please let us know if you need any additional details or assistance, and we’ll gladly continue supporting you.

3 answers

Your answer

Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator

2026-09-03T11:54:24.9733333+00:00

Hi @Prakash Palanivelu

Thank you for the detailed information.

Based on the error message, the Power Automate trigger appears to be functioning correctly after the credential re-authentication. However, the Azure Data Factory pipeline is failing at the stage where it attempts to access SharePoint through the Azure application DEMO-data123STG, resulting in a 401 Unauthorized error.

To further isolate the issue, could you please verify the following:

Whether the client secret or certificate associated with the DEMO-data123STG application has expired or been recently rotated.

Whether the application still has the required permissions and admin consent to access the SharePoint site.

Whether the SharePoint linked service in ADF is using the latest credentials and can successfully pass the access token to the Copy activity.

If there were any recent changes made to the Azure App Registration, Key Vault secrets, or SharePoint permissions after the last successful execution.

Since the workflow trigger is succeeding and the failure occurs during SharePoint access from ADF, the issue is likely related to authentication or authorization of the Azure application rather than the Power Automate flow itself.

Please let us know the findings from the above checks, and we'll continue assisting with the investigation.
Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator

2026-09-04T16:52:33.9066667+00:00

@Prakash Palanivelu Just checking in to see if the information provided earlier was helpful. Please let us know if you need any additional details or assistance, and we’ll gladly continue supporting you.

Answer 1

Senthil kumar 2,410

Hi @Prakash Palanivelu

First check your Linked services in ADF.

Open your ADF Linked Service that uses DEMO‑data123STG.

Verify:

Client ID
Tenant ID
Secret
Certificate (if used)
Authentication type
Token endpoint

If the secret expired or changed, ADF will always return 401.

Then check you app registration.

Go to Azure AD → App Registrations → DEMO‑data123STG.

Check:

Status: Enabled
Certificates & Secrets: Valid
Secret expiry date

If the secret expired, ADF cannot authenticate.

Thanks.

0 comments

Answer 2

Niraj Patel 0

Kindly assign Application Permission:

Under Configured permissions, select Add a permission to open the Request API permissions panel.

Select SharePoint.

Under What type of permissions does your application require?, select Application permissions.

Under Select permissions, select Sites.FullControl.All.

Select Add permissions to create the SharePoint permission.

Select Grant admin consent

0 comments

Answer 3

kagiyama yutaka 5,330

I think ADF and Power Automate don’t share auth, and ADF only uses the creds saved in its Linked Service when it calls SharePoint. So after re‑auth outside ADF, the DEMO‑data123STG secret and its SharePoint permission need to be refreshed in that Linked Service and “Test connection” run once, because Azure returns 401 only when that stored credential is invalid or doesn’t have enough rights for the site.

0 comments