When I read a Key Vault secret using the Web Activity in Fabric Pipelines, the secret value appears in the task’s Output panel after execution. This exposes sensitive information to anyone with Monitor access, which is not acceptable for our security requirements.
In contrast, reading secrets from a Notebook automatically redacts the value.
We want to use connections, which is why we rely on the Web Activity rather than a Notebook. This allows us to share credentials without granting every Workspace Contributor (and above) direct visibility into the Key Vault.
No CommentsBe the first to comment
Recent ideas
Service principal authentication support for data sources in Paginated(RDL) reports
We are only seeing two options(Basic, OAuth2) for data source authentication in a paginated report, Recently we see that the Service principal authentication enabled for Power BI(PBIX) reports, simi...Thatikonda_Vams6 minutes agoNew MemberNew126Views6likes2CommentsMetadata-Driven Copy Job Control at Table and Column Level
We currently achieve metadata-driven table and column selection in Copy Data activities by using dynamic queries. This allows us to dynamically determine which tables and columns should be processed ...Motasim095 hours agoNew MemberNew6Views0likes0CommentsDynamic ForEach Parallel Batch Count Based on Runtime Capacity
We would like Microsoft Fabric Data Factory to support dynamic configuration of the ForEach activity's parallel batch count at runtime. Currently, the ForEach batchCount is effectively configured as...Motasim095 hours agoNew MemberNew4Views0likes0CommentsMake Workspace-Level Surge Protection Limit Visible to Workspace Users
Please make the applicable workspace-level surge protection limit visible in the workspace settings. Currently, when surge protection is applied by Capacity Admins, workspace users don't get visibil...frithjof_v7 hours agoCommunity ChampionNew27Views2likes0Comments