Forum Discussion
Memorable MemberRedaction issue (need a workaround)
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.
Memorable MemberHi v-sgandrathi
I think this is a bug in "notebookutils.notebook.exit". Do you have any guidance on getting a fix?
Given that the adf pipeline activities are intended to allow passing "secure" parameters, and given that notebooks are one of the most common types of activities to run in an adf pipeline, then a customer would reasonably expect to be able to send a "secure" output parameter between activities via "notebookutils.notebook.exit"
Another reason I think this is a bug is because of the underlying goals for redaction. That is intended to prevent users of notebooks from unwittingly displaying secrets in the notebook outputs (... the cruft that appears under the cells). However, the redaction is NOT intended to prevent us from using secrets in a deliberate/intentional way for the sake of our solutions. Send an oauth token out of "notebookutils.notebook.exit" is a deliberate decision, and the redaction functionality should not interfere with that.
Obviously the workaround is available ("store it in a secure location"). But the end result of this workaround is even less secure than if the token was transmitted by way of notebookutils.notebook.exit. It makes the oauth token avaiable for a longer period of time, and potentially to a wider audience (based on the security of the "secure location").
Can you please give guidance on how to get the bug fixed, and a guestimate on how long it would take the PG to get engaged on something like this?
Community SupportHi 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 Learn
Thank you for being a part of the Microsoft Fabric Community.
- dbeavon3
I think it is a bug, since using a token for programmatic purposes should be allowable, as should the transfer of secrets between one step of a pipeline and another.
I will probably leave this for the next customer that encounters it. Based on my experiences with Fabric notebooks this past week, the team has much bigger fish to fry. Even in the optimistic chance that they agreed this was a bug, I cannot see them fixing it for the next year or two.