Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Currently, when a Dataverse Link to Fabric is recreated, refreshed, or experiences configuration changes, there is no exposed audit log or telemetry that allows customers to identify who or what triggered the action. This lack of traceability creates operational risk, investigation delays, and customer mistrust—especially in production environments where Fabric tables are business‑critical.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.