Forum Discussion
Redaction issue (need a workaround)
- 1 year ago
Hi dbeavon3,
Thank you for bringing this issue. It seems to be a technical limitation or bug with the notebookutils.notebook.exit functionality in ADF pipelines.
To address this effectively, we recommend raising a support ticket with Microsoft Azure Support. This will allow the engineering team to investigate the issue in detail and provide a resolution or guidance
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft LearnThank you for being a part of the Microsoft Fabric Community.
In addition to the workarounds above, another one I found is to use an entirely separate notebook to generate access token and save it to a file. Once it is in a file, we can read it back in a different notebook (sequentially executed via pipeline). After jumping thru these hoops, the Fabric notebook environment has no idea that it is a secret anymore, and doesn't try redacting anything.
This workaround seems very unfortunate, and quite a bit less secure than chopping up the secret into parts and sending it out of notebookutils.notebook.exit().