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
Blocker: Purview must scan Fabric Warehouse tables/columns or we will deprecate Purview
Purview + Fabric Warehouse ≠ enterprise‑ready governance. In our environment, the Fabric Warehouse is the system of record, but Purview can only catalog the warehouse container—not the tables or co...Joshua_Hernande9 hours agoNew MemberNew180Views1like1CommentPower Query Parameter create/use when connecting to a dataflow
In power query when you connect to a table in a dataflow there are no options to create or use a parameter for that dataflow. When connecting to SQL there is an option when setting up the connection ...ben_holmes17 hours agoNew MemberNeed Clarification198Views3likes1CommentParameterize Dataflow Gen2 data source connection
Allow the Dataflow Gen2 data source connection GUID to be parameterized and stored in a Variable Library. This would allow the same Dataflow to use different connections depending on the workspace/e...frithjof_v17 hours agoCommunity ChampionNeeds Votes37Views2likes1Comment