Hi Magnus Kardell,
From your description, the issue is unlikely to be caused by code changes, since none were made. Instead, it may be related to infrastructure or configuration changes in the Azure SQL Database or the networking layer. Common causes include transient service interruptions, throttling due to resource limits, or changes in firewall/connection policies. I recommend checking the Azure Service Health dashboard to confirm whether there were any incidents in your region around the time the issue began.
It’s also important to review the DTU or vCore utilization of your database. If workloads have grown, queries may be hitting resource limits and timing out. You can monitor this in the Azure Portal under SQL Database metrics. In addition, verify that your connection strings are using the recommended retry logic for transient faults, as Azure SQL enforces throttling under certain conditions.
Regarding support requests, a Developer service plan does allow you to open support tickets, but you must do so through the Azure Portal under “Help + Support.” The API does not provide direct support request creation for this plan. If you are unable to open a ticket, please confirm that your subscription is correctly linked to the support plan.
If you find this answer helpful, please consider hitting “Accept Answer” so others can benefit from it as well.
Jason.