Forum Discussion
What controls when Synapse SQL (COPY INTO) uses SAS token?
Hi PanuO,
Thanks for the update — that makes perfect sense. Private Links often restrict the required access path.
I suggest you to accept this post as the solution — it will help other community members facing similar problems to find the answer faster.
Regards,
Vinay Pabbu
Ok, thank you for pointing out the SAS-token limit.
I think there are no setting for "Allow trusted workspace access to OneLake" and "Allow workspace managed identity to access OneLake" in Fabric anymore?
Hi PanuO,
Thanks for pointing that out. Earlier advice was based on legacy configuration options that have since been deprecated. In the current Fabric model, access between the workspace and OneLake is managed automatically by the platform, and manual configuration of these trust settings is no longer available.
The issue is likely due to either a trust issue between the workspace and OneLake, or a platform-level constraint preventing MSI usage.
I recommended, raising a Microsoft support ticket to investigate and resolve the issue.
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
Regards,
Vinay Pabbu
Hi PanuO,
As we haven't heard back from you, I hope you have raised a support ticket. At this time we are closing this thread. If you have any further issues, please start a new thread in the community forum, and we are here to assist you. Thankyou for your understanding and continuous support.
Thank you for being part of the Microsoft Fabric Community.
Regards,
Vinay Pabbu
I made a ticket and lets see what we can come up on this. I would like to update the resolution here if it something that others can apply.
Hi @PanuO,
Thanks for the response As we haven't heard back from you, we are closing this thread for now. If you have any further issues, please start a new thread in the community forum, and we are here to assist you.
Thank you for being part of the Microsoft Fabric Community.
Regards,
Vinay Pabbu