Hi @Vinodh247
Thanks for using Fabric Community.
Fabric shortcuts are objects in OneLake that point to other storage locations. The location that a shortcut points to is known as the target path of the shortcut. The location where the shortcut appears is known as the shortcut path. Shortcuts appear as folders in OneLake and any workload or service that has access to OneLake can use them. Shortcuts behave like symbolic links. They’re an independent object from the target. If you delete a shortcut, the target remains unaffected. If you move, rename, or delete a target path, the shortcut can break.
To query the shortcut, you can use the external_table function of the Kusto Query Language. Any Fabric or non-Fabric service that can access data in OneLake can use shortcuts. Shortcuts are transparent to any service accessing data through the OneLake API. Shortcuts just appear as another folder in the lake.
OneLake shortcuts - Microsoft Fabric | Microsoft Learn
Unfortunately, there aren't any DMVs (Dynamic Management Views) or system tables/views that provide direct access to the metadata storage system. However, you can use the Fabric's REST API or SDKs to query the list of fabric shortcuts. For example, you can use the GET /shortcuts endpoint to retrieve a list of all fabric shortcuts in a Fabric instance. Additionally, you can use the Fabric's search functionality to find specific shortcuts based on their name, description, or other attributes.
OneLake Shortcuts - Get Shortcut - REST API (Core) | Microsoft Learn
Security and Access Control Fabric shortcuts are secured using Fabric's built-in security and access control mechanisms. When you create a fabric shortcut, you can specify the access control settings, such as who can view, edit, or execute the shortcut. The metadata storage system stores the security and access control information along with the shortcut metadata, ensuring that only authorized users can access and manipulate the shortcuts. In summary, fabric shortcuts in Microsoft Fabric are stored in a proprietary metadata storage system, which is optimized for fast querying and retrieval. While we don't have direct access to the metadata storage system, we can use the Fabric's built-in querying capabilities and REST API/SDKs to retrieve information about fabric shortcuts.
Hope this helps. Please let me know if you have any further questions.
