Microsoft has identified an issue with Fabric SQL Endpoints

User Impact: Fabric customers might experience data discrepancies when running queries against their SQL endpoints. As a workaround, users can follow below steps to mitigate.

1.) For non-shortcut tables: a) Rename the impacted table to a new name b) Execute Metadata Sync from SQL Endpoint c) Rename the impacted table back to the original name d) Execute Metadata Sync from SQL Endpoint'

2.) For shortcut tables: a) Drop the shortcut table from LakeHouse b) Execute Metadata Sync from SQL Endpoint c) Create a new shortcut table from LakeHouse d) Execute Metadata Sync from SQL Endpoint

Current Status: Microsoft has confirmed the fix has been deployed. Please report any issues to the Service Desk.

User Impact: Fabric customers might experience data discrepancies when running queries against their SQL endpoints. As a workaround, users can follow below steps to mitigate.

1.) For non-shortcut tables: a) Rename the impacted table to a new name b) Execute Metadata Sync from SQL Endpoint c) Rename the impacted table back to the original name d) Execute Metadata Sync from SQL Endpoint'

2.) For shortcut tables: a) Drop the shortcut table from LakeHouse b) Execute Metadata Sync from SQL Endpoint c) Create a new shortcut table from LakeHouse d) Execute Metadata Sync from SQL Endpoint

Current Status: Microsoft has confirmed the fix has been deployed. Please report any issues to the Service Desk.

23357861

User Impact: Fabric customers might experience data discrepancies when running queries against their SQL endpoints. As a workaround, users can follow below steps to mitigate.

1.) For non-shortcut tables: a) Rename the impacted table to a new name b) Execute Metadata Sync from SQL Endpoint c) Rename the impacted table back to the original name d) Execute Metadata Sync from SQL Endpoint'

2.) For shortcut tables: a) Drop the shortcut table from LakeHouse b) Execute Metadata Sync from SQL Endpoint c) Create a new shortcut table from LakeHouse d) Execute Metadata Sync from SQL Endpoint

Current Status: Engineers have identified the root cause, and a fix is expected to be deployed by end-of-day 07/28/2025

More information can be found at: https://support.fabric.microsoft.com/support/

23357861

User Impact: Fabric customers might experience data discrepancies when running queries against their SQL endpoints. As a workaround, users can follow below steps to mitigate.

1.) For non-shortcut tables: a) Rename the impacted table to a new name b) Execute Metadata Sync from SQL Endpoint c) Rename the impacted table back to the original name d) Execute Metadata Sync from SQL Endpoint'

2.) For shortcut tables: a) Drop the shortcut table from LakeHouse b) Execute Metadata Sync from SQL Endpoint c) Create a new shortcut table from LakeHouse d) Execute Metadata Sync from SQL Endpoint

Current Status: Engineers have identified the root cause, and a fix is expected to be deployed by end-of-day 07/27/2025

23357861

User Impact: Fabric customers might experience data discrepancies when running queries against their SQL endpoints. As a workaround, users can follow below steps to mitigate.

1.) For non-shortcut tables: a) Rename the impacted table to a new name b) Execute Metadata Sync from SQL Endpoint c) Rename the impacted table back to the original name d) Execute Metadata Sync from SQL Endpoint'

2.) For shortcut tables: a) Drop the shortcut table from LakeHouse b) Execute Metadata Sync from SQL Endpoint c) Create a new shortcut table from LakeHouse d) Execute Metadata Sync from SQL Endpoint

Current Status: Microsoft Engineers have identified the root cause, and an ETA for the fix would be provided by end-of-day 07/21/2025.