Notebook execution failed with status code unauthorized

[ketan5050]

Hello all,

We have been getting this error for couple of days.

We have downgraded sensitivity to general for both pipeline and notebooks individually.

Also, when we try to run same pipeline on different workspace it runs fine but not on current. can anyone help me troubleshoot this issue ?.

Also, while running i have admin access to the workspace.

[v-pnaroju-msft · Accepted solution]

Hi @ketan5050,

We sincerely appreciate your inquiry on the Microsoft Fabric Community Forum.

Based on my understanding, the error message indicates a 401 Unauthorized status code, which typically implies that the user does not possess the necessary permissions to access the artifact (notebook or pipeline). Despite having administrative access to the workspace, the issue persists, suggesting a possible misconfiguration or a deeper permission-related concern.

Kindly follow the troubleshooting steps below, which may help resolve the issue:

1. Ensure that the role in the workspace is correctly set to Admin.
2. Verify the permissions for the notebook and pipeline, ensuring that the account has Read/Write access.
3. Validate the sensitivity settings for the notebook and pipeline and confirm that they are set to General. If the sensitivity level is higher (e.g., Confidential), it may restrict access even for administrators.
4. The error message suggests reviewing the Run logs for additional details. Look for specific error messages or clues regarding unauthorized access.
5. If the pipeline executes successfully in a different workspace, compare the configurations. Check for discrepancies in permissions, sensitivity settings, and artifact versions. Ensure that the workspace where the pipeline fails has the same configurations as the one where it succeeds.
6. At times, cached credentials may cause authorization issues. Sign out of Microsoft Fabric, clear your browser cache, or use an incognito window. Then, sign in again and attempt to run the pipeline.

If you find our response helpful, kindly mark it as the accepted solution and provide kudos, as this will assist other community members encountering similar queries.

Thank you.

[v-pnaroju-msft · Accepted solution]

Hi ketan5050,

We are following up to see if your query has been resolved. Should you have identified a solution, we kindly request you to share it with the community to assist others facing similar issues.

If our response was helpful, please mark it as the accepted solution and provide kudos, as this helps the broader community.

Thank you.

[v-pnaroju-msft]

Hi ketan5050,

We wanted to check in regarding your query, as we have not heard back from you. If you have resolved the issue, sharing the solution with the community would be greatly appreciated and could help others encountering similar challenges.

If you found our response useful, kindly mark it as the accepted solution and provide kudos to guide other members.

Thank you.

[v-pnaroju-msft]

Hi ketan5050,

We have not received a response from you regarding the query and were following up to check if you have found a resolution. If you have identified a solution, we kindly request you to share it with the community, as it may be helpful to others facing a similar issue.

If you find the response helpful, please mark it as the accepted solution and provide kudos, as this will help other members with similar queries.

Thank you.

[v-pnaroju-msft · Accepted solution]

Hi @ketan5050,

We sincerely appreciate your inquiry on the Microsoft Fabric Community Forum.

Based on my understanding, the error message indicates a 401 Unauthorized status code, which typically implies that the user does not possess the necessary permissions to access the artifact (notebook or pipeline). Despite having administrative access to the workspace, the issue persists, suggesting a possible misconfiguration or a deeper permission-related concern.

Kindly follow the troubleshooting steps below, which may help resolve the issue:

1. Ensure that the role in the workspace is correctly set to Admin.
2. Verify the permissions for the notebook and pipeline, ensuring that the account has Read/Write access.
3. Validate the sensitivity settings for the notebook and pipeline and confirm that they are set to General. If the sensitivity level is higher (e.g., Confidential), it may restrict access even for administrators.
4. The error message suggests reviewing the Run logs for additional details. Look for specific error messages or clues regarding unauthorized access.
5. If the pipeline executes successfully in a different workspace, compare the configurations. Check for discrepancies in permissions, sensitivity settings, and artifact versions. Ensure that the workspace where the pipeline fails has the same configurations as the one where it succeeds.
6. At times, cached credentials may cause authorization issues. Sign out of Microsoft Fabric, clear your browser cache, or use an incognito window. Then, sign in again and attempt to run the pipeline.

If you find our response helpful, kindly mark it as the accepted solution and provide kudos, as this will assist other community members encountering similar queries.

Thank you.