Blog Post

Azure Database Support Blog
4 MIN READ

Azure SQL Database idle sessions are killed after about 30 minutes when "Proxy" connection policy

hugo_sql's avatar
hugo_sql
Icon for Microsoft rankMicrosoft
Sep 29, 2022
When we connect to our Azure SQL Databases or Azure SQL Managed Instances databases using the "Proxy" connection policy and the session is still open without any activity, the Azure SQL Gateway will ...
Updated Mar 18, 2024
Version 4.0
azure
databases
idle
kill
Managed Instance
sessions
sql
Colin_Hunter's avatar
Colin_Hunter
Copper Contributor
Oct 10, 2023
"To these scenarios, we need to add another variable "https://docs.microsoft.com/en-us/azure/azure-sql/database/private-endpoint-overview?msclkid=7e415dadadfd11ecb772e98959fcdbf4#limitations" (Private Endpoint Connections). If we have enabled a "Private endpoint connection" on our Azure SQL Server, the only supported connection policy within Azure, Site-to-Site VPN and ExpressRoute are "Proxy", so all sessions will be killed after about 30 minutes of being inactive (idle).

Only when you connect from on-premises without Site-to-Site VPN and ExpressRoute you can force it to use "Redirect", and the connections will be handled directly by the node that hosts the database, and then your session won't be killed by the Azure SQL Gateway."

 

Hi,

Can I check the comment about Private Endpoint for SQL managed instances.
Is this saying that the only connection "type" for MI, with private endpoint, is proxy - so idle session will always be disconnected after 30mins when using Private endpoint?
Or can an on-prem connection without site-to-site VPN/ExpressRoute be used for SQL MI with PE (and therefore use "redirect")?
The meaning of the sentence is not clear to me

Thanks