Forum Discussion
ERROR: ValidateWorkspaceOACAsync: exception occured
- Anonymous9 months ago
The solution from Microsoft is as follows:
Make a false edit on the pipeline for example, change parameter value, undo it and then save pipeline. Then try running again. This has fixed it for other users.
Hi Anonymous - has this worked correctly in the past? If so, have any changes to the files or pipeline been made since its last successful run? Since the error occurred on the data pipeline and includes 'unauthorized', it implies that the pipeline cannot authenticate to the lakehouse. I recommend checking that connection to ensure it is configured properly and has the appropriate permissions. If you provide some additional information such as what type of account you are using in the connection (user, workspace Identity, service principal), I'll be glad to further assist.
- Anonymous9 months agoNot applicable
Hi jennratten its worked consistenly since June 2025.
The pipeline sits in the same workspace as the lakehouse I'm trying to connect to and I own the workspace, pipeline and lakehouse.
I've tried recreating the pipeline this morning and it appears you can't connect directly to a Lakehouse anymore, it wants a connection first?
New LookUp from Today
Existing LookUp
- jennratten9 months agoSuper User
Hi Anonymous - the two screenshots you showed would have different inputs because in one you selected lakehouse tables and in the other you selected lakehouse files.
If this post helps to answer your questions, please consider marking it as a solution so others can find it more quickly when faced with a similar challenge.
Proud to be a Microsoft Fabric Super User
- Anonymous9 months agoNot applicable
Apologies, if the screen shot was misleading. When I select an input of files it still requests a connection. It previously didn't request a separate connection to the lakehouse as the lakehouse was the connection.