Suddenly lost access to a shortcut from a Notebook

[gerardotrejogcg]

I have a shortcut in the Lakehouse that I’m able to access to manually.

It was implemented a notebook that reads the shortcut and the last successfully processed folder was “2025-02-14T17.27.20Z”.

To confirm that it is a permission issue I forced the notebook to read the same folder as above “2025-02-14T17.27.20Z” and I got the same error message.

Any thougts what I can check?

[v-pagayam-msft]

Hi @gerardotrejogcg ,
I wanted to check in on your situation regarding the issue. Have you resolved it? If you have, please consider marking the reply that helped you or sharing your solution. It would be greatly appreciated by others in the community who may have the same question.

Thank you for being a part of the Microsoft Fabric Community Forum!

[v-pagayam-msft]

Hi @gerardotrejogcg ,
I wanted to check in on your situation regarding the issue. Have you resolved it? If you have, please consider marking the reply that helped you or sharing your answer and Accept it as solution. It would be greatly appreciated by others in the community who may have the same question

Thank you for being a valued member of the Microsoft Fabric Community Forum!

[v-pagayam-msft]

Hi @gerardotrejogcg ,
I wanted to check in on your situation regarding the issue. Have you resolved it? If you have, please consider marking the reply that helped you or sharing your answer and 'Accept as solution'. It would be greatly appreciated by others in the community who may have the same question.

Thank you for being a valued member of the Microsoft Fabric Community Forum!

[v-pagayam-msft]

Hi @gerardotrejogcg  ,
Thank you for reaching out to us on Microsoft Fabric Community Forum!

I would take a moment to personally thank @nilendraFabric  for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

As Niledra suggested,if the notebook is accessing a shortcut to a remote data source, it uses the Lakehouse owner’s identity rather than the notebook user’s identity. If the owner does not have the necessary permissions on either the Lakehouse shortcut or the target data source, access will fail.

If still facing difficulty in resolving the issue, please feel free to reachout.

If this post helps, please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Regards,
Pallavi.

[gerardotrejogcg · Accepted solution]

I did not find the permission issue.    I just changed the way to read the file

    try:

        df = spark.read.option("multiline", "true").json(schema_file)

        json_data = df.toJSON().collect()

        schema = json.loads(json_data[0])  # Convert first row to a dictionary

    except Exception as e:

        print(f"Error reading model.json: {e}")

        return {}

[v-pagayam-msft]

Hi @gerardotrejogcg ,
Just to confirm, are you saying that the issue is resolved with the new reading method, or are you still facing an error? If it's resolved, please accept it as a solution. It will be helpful for other members of the community who have similar problems as yours to solve it faster.

Thank you.

[gerardotrejogcg]

I just checked and looks like everything is ok.  The error I have in the notebook is "IPython won't let you open fd={file} by default as it is likely to crash IPython. If you know what you can use builtins' open."

I'm trying to read this location 

schema_file = f"/lakehouse/default/{synapse_link_shortcut_path}/{synapse_link_environment}/{folder}/model.json"


PermissionError: [Errno 1] Operation not permitted: '/lakehouse/default/Files/synapse_link/dataverse-ssmprod-unqcXXXXXXXXXXXXXX/2024-09-10T22.28.32Z/model.json'

[nilendraFabric]

Hello @gerardotrejogcg 

Notebooks executing via shortcuts delegate access using the item owner’s identity (e.g., the notebook or semantic model owner) rather than the user’s identity. If the owner’s permissions were revoked or modified, access breaks.

Verify the item owner’s permissions on both the shortcut’s Lakehouse and the target data source. Ensure they have Contributor or Storage Blob Data Contributor roles