UniversalSecurityClientUserException – SQL Analytics Endpoint stuck on "Unexpected error encountered

[MarcusTrinder]

We are unable to reliably open or manage the SQL Analytics Endpoint associated with the lakehouse AdHocLakehouse.
The endpoint shows the error:

The error persists after:

• Closing and reopening browser tabs
• Refreshing the browser
• Refreshing Endpoint using SQLEnspoint Refresh activity from pipeline
• Waiting for background synchronization to complete

The issue appears to be related to security/metadata synchronization rather than data availability.

[v-hashadapu]

Hi @MarcusTrinder , hope you are doing well.

Just wanted to know if your issue has been resolved through your support ticket with Microsoft? If so, we would greatly appreciate it if you could share the insights here, as they may benefit others with similar issues.

If you have any other queries, please feel free to raise a new post in the community. We are always happy to help. Thank you.

[v-hashadapu]

Hi @MarcusTrinder , From what I read of the entire conversation, I think at this point the best course of action is to raise a Microsoft Support ticket, as this would need to be resolved on their end.

Below is the link to help create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

[Tamanchu]

Hi @MarcusTrinder ,

The UniversalSecurityClientUserException on the SQL Analytics Endpoint typically indicates a metadata/security sync failure between the Lakehouse and its auto-generated endpoint not a data issue. Here are the steps that usually resolve it:

1. Force a full endpoint sync via REST API
The pipeline activity may not trigger a deep sync. Try calling the Fabric REST API directly:

POST https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/lakehouses/{lakehouseId}/tables/loadAll
Or use the "Refresh" button directly from the SQL Endpoint item in the workspace (not from a pipeline).

2. Check if the issue is user-specific
Test with another account that has workspace Admin or Member role if the endpoint opens for them, the issue is specific to your user's security token propagation.

3. Verify capacity state
If your Fabric capacity was paused/resumed recently, security context tokens may not have re-synced. Try pausing and resuming the capacity from the admin portal.

4. Check for known issues
Visit the Fabric service health page and the Known Issues tracker for any active incidents related to SQL Endpoint.

5. If nothing else works
Open a support ticket and include the correlation ID from the error (usually visible in browser DevTools → Network tab when the error fires). This helps Microsoft Engineering trace the exact sync failure.

Let me know which step resolves it.

[MarcusTrinder]

I have also tried calling '"/v1/workspaces/{workspace_id}/sqlEndpoints/{sql_endpoint_id}/refreshMetadata"' with no luck.

[MarcusTrinder]

@tayloramy this succeeds but doesnt remove the initial error message

[tayloramy]

It looks like your workspace or lakehouse IDs are incorrect, or perhaps you don't have permissions. 

What is your role on the workspace? 

[MarcusTrinder]

the ID's are correct i double checked, and i am a workspace admin

[MarcusTrinder]

Hi, thanks for the help.

We tried step 1 and got a HTTP error; 

---

@Tamanchu wrote:

Hi @MarcusTrinder ,

The UniversalSecurityClientUserException on the SQL Analytics Endpoint typically indicates a metadata/security sync failure between the Lakehouse and its auto-generated endpoint not a data issue. Here are the steps that usually resolve it:

1. Force a full endpoint sync via REST API
The pipeline activity may not trigger a deep sync. Try calling the Fabric REST API directly:

POST https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/lakehouses/{lakehouseId}/tables/loadAll
Or use the "Refresh" button directly from the SQL Endpoint item in the workspace (not from a pipeline).

2. Check if the issue is user-specific
Test with another account that has workspace Admin or Member role if the endpoint opens for them, the issue is specific to your user's security token propagation.

3. Verify capacity state
If your Fabric capacity was paused/resumed recently, security context tokens may not have re-synced. Try pausing and resuming the capacity from the admin portal.

4. Check for known issues
Visit the Fabric service health page and the Known Issues tracker for any active incidents related to SQL Endpoint.

5. If nothing else works
Open a support ticket and include the correlation ID from the error (usually visible in browser DevTools → Network tab when the error fires). This helps Microsoft Engineering trace the exact sync failure.

Let me know which step resolves it.

---

FabricHTTPException

404 Not Found for url: https://api.fabric.microsoft.com//v1/workspaces/e07c7f9e-d54f-4ba9-b492-9928669178ef/lakehouses/d808... Error: {"requestId":"d04aaa75-d111-40a2-b8ce-b1ecb0a98b3a","errorCode":"EntityNotFound","message":"The requested resource could not be found","isRetriable":false} Headers: {'Content-Length': '155', 'Content-Type': 'application/json; charset=utf-8', 'x-ms-public-api-error-code': 'EntityNotFound', 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains', 'X-Frame-Options': 'deny', 'X-Content-Type-Options': 'nosniff', 'Access-Control-Expose-Headers': 'RequestId', 'RequestId': 'd04aaa75-d111-40a2-b8ce-b1ecb0a98b3a', 'Date': 'Tue, 21 Apr 2026 12:39:17 GMT'}.

[tayloramy]

Hi @MarcusTrinder, 

you have an extra / after microsoft.com in your request. 

Do you happen to have OneLake Security configured on this Lakehouse? Errors in configuring RLS can cause this in my experience. 

You cna also try refreshing the SQL Endpoint specifically: 
https://learn.microsoft.com/en-us/rest/api/fabric/sqlendpoint/items/refresh-sql-endpoint-metadata?ta...

[MarcusTrinder]

We do not have onelake security enabled

[MarcusTrinder]

removed the extra '/' and still get :

FabricHTTPException

404 Not Found for url: https://api.fabric.microsoft.com/v1/workspaces/e07c7f9e-d54f-4ba9-b492-9928669178ef/lakehouses/d8083... Error: {"requestId":"81fd1396-4070-4b3b-9292-754c5307bf8f","errorCode":"EntityNotFound","message":"The requested resource could not be found","isRetriable":false} Headers: {'Content-Length': '155', 'Content-Type': 'application/json; charset=utf-8', 'x-ms-public-api-error-code': 'EntityNotFound', 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains', 'X-Frame-Options': 'deny', 'X-Content-Type-Options': 'nosniff', 'Access-Control-Expose-Headers': 'RequestId', 'request-redirected': 'true', 'home-cluster-uri': 'https://wabi-north-europe-redirect.analysis.windows.net/', 'RequestId': '81fd1396-4070-4b3b-9292-754c5307bf8f', 'Date': 'Tue, 21 Apr 2026 13:37:19 GMT'}