Forum Discussion

PanuO's avatar
PanuO
Helper II
1 year ago
Solved

What controls when Synapse SQL (COPY INTO) uses SAS token?

I am using this simple Notebook code to write data into Fabric Warehouse: import com.microsoft.spark.fabric from pyspark.sql.types import StructType, StructField, StringType, IntegerType df = spar...
notebook
  • Anonymous's avatar
    Anonymous
    1 year ago

    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

Anonymous's avatar
Anonymous
Not applicable
1 year ago

Hi PanuO,

 

Thank you for reaching out to Microsoft Fabric Community Forum.

 

The issue isn't with the SAS token settings — those are preview features and mostly related to future support for user-delegated SAS tokens, which do not currently control the behavior of COPY INTO in Microsoft Fabric.

 

Please check the following Tenant Settings under Admin Portal > Tenant Settings:

  • Allow workspace managed identity to access OneLake
  • Allow trusted workspace access to OneLake

If these are disabled, Fabric cannot use MSI


If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!


Regards,
Vinay Pabbu

PanuO's avatar
PanuO
Helper II
1 year ago

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?

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    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

    • Anonymous's avatar
      Anonymous
      Not applicable
      1 year ago

      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

      • PanuO's avatar
        PanuO
        Helper II
        1 year ago

        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.