Operation returned an invalid status code 'Unauthorized' while copying data to Lakehouse

[SivaReddy24680]

ErrorCode=LakehouseOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Lakehouse operation failed for: Operation returned an invalid status code 'Unauthorized'. Workspace: 'WorkSpaceID'. Path: 'LakehouseID/Tables/SchemaName/TableName/8e41ff8f-919c-45c0-b62d-1798a0cb03ce_GUID.parquet'. ErrorCode: 'Unauthorized'. Message: 'Unauthorized'. TimeStamp: 'Mon, 17 Nov 2025 11:29:35 GMT'..,Source=Microsoft.DataTransfer.ClientLibrary,''Type=Microsoft.Azure.Storage.Data.Models.ErrorSchemaException,Message=Operation returned an invalid status code 'Unauthorized',Source=Microsoft.DataTransfer.ClientLibrary,'


Hi,

We are encountering the above error while running a Fabric Copy Activity. The issue occurs when copying data from SAP HANA into a Lakehouse.

The pipelines were running successfully earlier, but since last week we have started receiving the above error. Previously, we were able to use a LakehouseID. However, it appears that Fabric has introduced an update that now Connection for the Lakehouse.

Older Destination Setting:

New Destination Setting:

We investigated the issue further and identified that token expiration might be the root cause. When reviewing the Lakehouse connection that we recently created, we noticed that the authentication method is set to OAuth by default, and it appears to be the only available option.

can someone please help with the issue and the reason.?

[Vinodh247]

This seems like a fabric platform issue and fabric regression, not your config. Microsoft recently changed the Lakehouse destination to require a Lakehouse connection, and that connection now uses OAuth only. Pipelines cannot refresh oauth tokens, so once your user token expires, the copy activity fails with Unauthorized when writing to OneLake. It is not related to SAP hana/permissions.

Workarounds that you can try:

1. Avoid using the new Lakehouse connection (use manual table entry if still available).

2. Recreate the conn before each run (temp).

3. Raise a support ticket because the change broke non interactive pipeline loads.

[SivaReddy24680]

@Vinodh247 Thanks for replying.

I'm trying the workarounds that you suggested

1. The connection still seems to be mandatory. Even when the Lakehouse is attached directly, Fabric asks for a connection to be created.

2. This approach works for small tables that run in a loop(can you please provide some info or document on how to refresh token using pipeline), but for large-volume tables the token expires in the middle of the extraction. We are planning to load these tables in chunks based on the date fields to avoid the issue.

[Vinodh247]

I am afraid there is no doc on “refreshing token using pipeline” because fabric does not support it. Oauth tokens for lakehouse conne are user based and expire silently during long running copy operations.

[v-nmadadi-msft]

Hi  @SivaReddy24680 ,
Thanks for reaching out to the Microsoft fabric community forum.
In addition to the valuable points suggested by @Vinodh247 , Check out this point as well.

Please ensure that for the Lakehouse you are trying to copy data into, you have the correct workspace role assigned in the workspace where that Lakehouse exists. The role should be Contributor, Member, or Admin, Viewer is not sufficient for write operations.

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

[SivaReddy24680]

@v-nmadadi-msft 

I have the Admin role for the workspace. We are not encountering this error at the beginning of the process, it occurs intermittently after writing some records.

[v-nmadadi-msft]

Hi @SivaReddy24680 ,
Sorry to know it didn’t help. Please consider reaching out to Microsoft Support. You can provide them with all the troubleshooting steps you've already taken, which will help them understand the issue better and provide a resolution. They might be able to identify something specific about your admin account setup or provide a solution that isn't immediately obvious. 

Below is the link to create Microsoft Support ticket:
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

Regards

[v-nmadadi-msft]

Hi @SivaReddy24680 
Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.

Thank you for your understanding and assistance.

[SivaReddy24680]

Hi @v-nmadadi-msft 

The support team suggested appending &feature.enableArtifactDMTSConnection=0 to the pipeline URL so that the old changes apply to the current pipeline. Also mentioned that a new toggle button will be implemented by the end of December which users can use to enable/disable the new changes in the pipeline.

[v-nmadadi-msft]

Hi @SivaReddy24680 ,

We really appreciate your efforts and for letting us know the update on the issue.

Please continue using fabric community forum for your further assistance.

Regards