Blog Post

Azure Database Support Blog
3 MIN READ

Connectivity Errors caused by slow logins in a Microsoft Fabric SQL Database

Tancy's avatar
Tancy
Icon for Microsoft rankMicrosoft
Aug 26, 2026

By Tanayankar Chakraborty & Sukhwant Kaur 

Issue 

A customer recently reported that their Azure App Service intermittently cannot establish a TDS connection to its Microsoft Fabric SQL database within 15 seconds. Also, Review Queue and Worklists returned HTTP 500 after approximately 15 seconds. 

This occurred before any SQL statement executed and was not an Entra login/permission error.

Error 

Here is the error generated in the App service logs:

At 2026-07-29 22:42:15 UTC, App Insights recorded: 

ConnectionError / ETIMEOUT: Failed to connect to the Fabric SQL endpoint in 15000ms. 

GET /api/review/queue returned HTTP 500 in 15,100ms. 

 

Troubleshooting 

As stated in our public documentation, throttling by Fabric platform is expected behavior (requests getting delayed by 20 seconds for initial throttling, and requests getting rejected outright if it gets worse) if usage is heavy, especially on a heavy SQL workload on workspace/capacity shared with other artifacts, with a small capacity size (F4, etc).

Assuming that's what the issue is, general guidance is to: 

  • Decrease the max vCore limit on the affected SQL DB to limit the amount of CUs it can consume , but obviously there would be a performance tradeoff here though, and throttling can still be caused by other items in the workspace/capacity 
  • Increase the capacity (F16+, etc) 

Fabric allows operations to temporarily use more compute than the provisioned SKU through bursting and distributes that usage over future capacity through smoothing. When smoothed usage exceeds the capacity's available future compute, the excess becomes carry-forward usage. Fabric then progressively protects the capacity by delaying or rejecting new operations. 

 

Workaround 

### Mitigate Active Throttling 

Microsoft's documented mitigation options include:  

- Wait for the capacity to self-heal while unused capacity burns down carry-forward usage. 

- Temporarily increase the F SKU size. The larger SKU provides more idle capacity and accelerates burndown. 

- Pause and resume the capacity. This creates a billing event for accumulated future usage, and the resumed capacity starts with zero future usage. 

- Consider capacity overage billing where appropriate. Microsoft documents this option as being billed at three times the normal capacity rate. 

 

Any pause/resume or billing change should be reviewed by the capacity administrator for operational and cost impact.

 

### Improve Application Resilience 

- Use bounded retry with jitter for transient connection failures where the operation is safe to retry. 

- Align SQL connection timeout and retry settings with the application's end-to-end request budget. 

- Capture UTC timestamps, connection/request IDs, operation names, and SQL error numbers for future incidents. 

 

Monitoring 

It is recommended to monitor and right size the capacity: 

Use the Microsoft Fabric Capacity Metrics app to monitor: 

- Utilization by workload and item 

- Interactive and background CU consumption 

- Carry-forward and burndown 

- Throttling events and rejected operations 

- Minutes to burndown 

A capacity that is throttled might appear in the Fabric Capacity Metrics app as shown below:

 

In the Capacity Metrics app: 

1. Use the **Utilization** chart and drill through to individual timepoints to identify operations contributing to overages. 

2. Use the **Throttling** chart to determine whether an overage has crossed a throttling threshold. 

3. Use the **Overages** tab to review carry-forward, additions, burndown, and cumulative utilization. 

4. Configure capacity alerts so administrators are notified when provisioned CU usage reaches 100%. 

 

### Reduce Peak Concurrent Usage 

- Stagger high-CU SQL and Data Integration operations where possible. 

- Review expensive or highly concurrent SQL database operations. 

- Distribute workloads across capacities if sustained demand requires it. 

- Use historical Capacity Metrics data to select a SKU with sufficient peak headroom. 

 

References 

Understand capacity throttling and smoothing - Microsoft Fabric | Microsoft Learn

Surge protection - Microsoft Fabric | Microsoft Learn

Billing and Utilization Reporting - Microsoft Fabric | Microsoft Learn

Control Compute Usage - Microsoft Fabric | Microsoft Learn

What is the Microsoft Fabric Capacity Metrics app? - Microsoft Fabric | Microsoft Learn

Set alerts on Fabric capacity overview events in Real-Time hub - Microsoft Fabric | Microsoft Learn

 

 

 

Published Aug 26, 2026
Version 1.0
No CommentsBe the first to comment