Issues with Blazor Web App Connecting To SQL Server Consistently

Question

Issues with Blazor Web App Connecting To SQL Server Consistently

Andrew Sabin 80

Hello Microsoft Support,

With my Blazor Web App hosted as an Azure Static Web app, I have been having issues with accessing certain information through different pages that are stored on a SQL server after opening a tab accessing my Web App and keeping it idle for around 20 to 30 minutes.

Here is the connection string that I am using with my Azure Static Web app to connect to the specific database:

Server=tcp:<DataBaseName>,<PortNumber>;Initial Catalog=<ServerName>;Persist Security Info=False;User ID=<UserName>;Password=<Password>;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=60;

Would this be an issue with my web application or the connection string that I am using? I can provide information from the Program.cs file if you need me to.

Thank you very much for your time and help,

Andrew Sabin

Abhinaba Das 115 Reputation points Microsoft External Staff Moderator

2026-08-24T22:48:49.71+00:00

Thank you for contacting us about the Issues with Blazor Web App Connecting To SQL Server Consistently issue .We have begun looking into it and will share our suggestions with you as soon as possible. If you have any additional details or concerns in the meantime, please let us know. We appreciate your patience while we work on this

2 answers

Your answer

Abhinaba Das 115 Reputation points Microsoft External Staff Moderator

2026-08-24T22:48:49.71+00:00

Thank you for contacting us about the Issues with Blazor Web App Connecting To SQL Server Consistently issue .We have begun looking into it and will share our suggestions with you as soon as possible. If you have any additional details or concerns in the meantime, please let us know. We appreciate your patience while we work on this

Answer 1

kagiyama yutaka 5,165

I think the behavior you saw aligns with Azure SQL ending idle sessions around 20–30 minutes. Azure Static Web Apps run Blazor only on the client and cannot keep any SQL connection, so direct access to SQL becomes unstable after idle periods. The stable setup is to move the DB access into a small Azure Functions API and call it from the pages.

This isn’t a connection‑string issue — it simply matches Azure SQL’s idle‑session behavior.　

0 comments

Answer 2

This is most likely a connection-idle issue rather than a Blazor page issue.

Azure SQL Database can terminate idle connections after about 30 minutes when the connection is idle at the TDS/query layer, even if TCP keepalive is present. That matches the pattern described: the app works, sits idle for 20–30 minutes, then fails on the next database access.

The connection string is not the main problem based on the idle timing alone. The important parts already align with recommended settings:

Use the fully qualified Azure SQL server name and port 1433
Keep Encrypt=True
Keep TrustServerCertificate=False
Use a connection timeout of at least 30 seconds

Recommended checks and fixes:

Verify the server name format in the connection string.
- For Azure SQL Database, use the fully qualified server name in this form: Server=tcp:<database-server-name>.database.windows.net,1433;
- If the current Server=tcp:<DataBaseName>,<PortNumber>; value is not the Azure SQL fully qualified name, correct it.
Confirm the database name placement.
- Initial Catalog should be the database name.
- The server name belongs in the Server= portion.
Add retry logic in the app.
- Retry logic is strongly recommended for Azure SQL client applications so the app can reconnect after transient failures.
- The recommended first retry delay is 5 seconds, then increase delays exponentially up to 60 seconds.
Check for stale DNS or hosts-file overrides.
- If failures happen only on certain networks, remove any hosts-file, static CNAME, or other DNS override for the Azure SQL FQDN, then flush DNS and retest.
For Azure Static Web Apps, verify database access prerequisites.
- The database firewall must allow network access from Azure resources for Static Web Apps workers.
- Allowing specific Static Web Apps IP addresses is not supported.
- If Managed Identity authentication is used, the Static Web App managed identity must be granted access to the database.
If using the JDBC driver anywhere in the stack, review idle connection handling.
- Azure SQL documentation notes that idle connections can be dropped by network devices or by the Azure SQL Gateway after 30 minutes of no active query.
- Using the Redirect connection policy is one documented way to avoid gateway termination of idle connections.

A corrected Azure SQL connection string shape would be:

Server=tcp:<database-server-name>.database.windows.net,1433;Initial Catalog=<database-name>;Encrypt=True;TrustServerCertificate=False;Connection Timeout=60;

A better long-term option is passwordless authentication instead of storing SQL username and password in the connection string. For Azure SQL, the recommended pattern is:

Server=tcp:<database-server-name>.database.windows.net,1433;Initial Catalog=<database-name>;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;Authentication="Active Directory Default";

If the current issue is specifically “fails after being idle,” the first practical fix is to implement retry logic and verify the server/database values in the connection string.

References: