Troubleshoot SQL Database connectivity error 40613

Question

Troubleshoot SQL Database connectivity error 40613

Rob Lim 0

On Azure SQL.

We tried to do the preview restart. Still got the error that it could not connect to database.

Ran the recommended cloud shell command for Manual Failover and still could not connect to database.

Not sure what to do, since it looks like I can't open a ticket anymore on the Developer plan.

Rob Lim 0 Reputation points

2026-05-14T18:28:09.29+00:00

How do I escalate this. I can't even set to a different DTU since we can't connect to the database.
TP 156.6K Reputation points Volunteer Moderator

2026-05-14T19:12:46.6433333+00:00

Hi Rob, is this in Canada Central? I ask because someone else is reporting same issue.

Since you have Developer support your question falls under Priority Community Support. A Microsoft External Staff person will reply and if they determine it is necessary they will create a technical support request on your behalf.

If you want to create your own Severity A (<1 hour response) Technical support request in the portal, you must first upgrade your support plan to Standard.
Rob Lim 0 Reputation points

2026-05-14T19:17:27.45+00:00

Yes, this is Canada Central. Am I mistaken, or were we able to submit tickets before? Under the Developer support? I dropped from Developer back to Basic, since it seems like Co-Pilot helps me a lot more with the troubleshooting, but can't do anything if it is a potential failure or outage.
TP 156.6K Reputation points Volunteer Moderator

2026-05-14T19:24:23.91+00:00

Yes, previously you could create Severity C tickets under Developer plan, but that changed over a year ago. Now you have to ask question here on Q & A and then if External Staff determines it is necessary they will create a technical support request on your behalf. Please see the link I posted above for more details.
Rob Lim 0 Reputation points

2026-05-14T19:31:49.86+00:00

OK thanks TP, I tried to do a search on this issue but got old posts. So not sure how you saw that someone was reporting the same issue for Canada Central. Let's see if anyone from M$ gets back to me on this issue. Because paying for Developer support on a "Maybe External Staff will deem it necessary" seems to be a strange way to assist with failure.
TP 156.6K Reputation points Volunteer Moderator

2026-05-14T19:36:50.1566667+00:00

Rob, below is link to other person experiencing same issue. I suggested to them they could try restoring since it worked for you:

https://learn.microsoft.com/en-us/answers/questions/5890977/can-not-connect-to-azure-database
SAI JAGADEESH KUDIPUDI 3,115 Reputation points Microsoft External Staff Moderator

2026-05-15T23:35:49.5+00:00
Hi Rob Lim,Error 40613 in Azure SQL Database generally indicates that the database is currently unavailable. This can happen during failover operations, scaling activities, maintenance events, or if the database is in a paused/suspended state.

Since you already attempted both the Preview Restart and Manual Failover without success,
could you please help confirm a few additional details?

Is the SQL Database in an Online state in the Azure portal?

Are you able to connect from Azure Query Editor or SSMS using the server fully qualified name?

Does the issue affect only one database or all databases on the logical server?

Could you share the exact full error message and timestamp (UTC) of the failed connection attempts?

Are there any firewall, private endpoint, or networking changes recently made?

Microsoft Reference Links:

Troubleshoot connectivity issues in Azure SQL Database

Azure SQL Database error messages and troubleshooting

Once you share the additional details above, could you please send requested via private message so we can help narrow down the root cause further.

1 answer

Your answer

Rob Lim 0 Reputation points

2026-05-14T18:28:09.29+00:00

How do I escalate this. I can't even set to a different DTU since we can't connect to the database.
TP 156.6K Reputation points Volunteer Moderator

2026-05-14T19:12:46.6433333+00:00

Hi Rob, is this in Canada Central? I ask because someone else is reporting same issue.

Since you have Developer support your question falls under Priority Community Support. A Microsoft External Staff person will reply and if they determine it is necessary they will create a technical support request on your behalf.

If you want to create your own Severity A (<1 hour response) Technical support request in the portal, you must first upgrade your support plan to Standard.
Rob Lim 0 Reputation points

2026-05-14T19:17:27.45+00:00

Yes, this is Canada Central. Am I mistaken, or were we able to submit tickets before? Under the Developer support? I dropped from Developer back to Basic, since it seems like Co-Pilot helps me a lot more with the troubleshooting, but can't do anything if it is a potential failure or outage.
TP 156.6K Reputation points Volunteer Moderator

2026-05-14T19:24:23.91+00:00

Yes, previously you could create Severity C tickets under Developer plan, but that changed over a year ago. Now you have to ask question here on Q & A and then if External Staff determines it is necessary they will create a technical support request on your behalf. Please see the link I posted above for more details.
Rob Lim 0 Reputation points

2026-05-14T19:31:49.86+00:00

OK thanks TP, I tried to do a search on this issue but got old posts. So not sure how you saw that someone was reporting the same issue for Canada Central. Let's see if anyone from M$ gets back to me on this issue. Because paying for Developer support on a "Maybe External Staff will deem it necessary" seems to be a strange way to assist with failure.
TP 156.6K Reputation points Volunteer Moderator

2026-05-14T19:36:50.1566667+00:00

Rob, below is link to other person experiencing same issue. I suggested to them they could try restoring since it worked for you:

https://learn.microsoft.com/en-us/answers/questions/5890977/can-not-connect-to-azure-database
SAI JAGADEESH KUDIPUDI 3,115 Reputation points Microsoft External Staff Moderator

2026-05-15T23:35:49.5+00:00

Hi Rob Lim,Error 40613 in Azure SQL Database generally indicates that the database is currently unavailable. This can happen during failover operations, scaling activities, maintenance events, or if the database is in a paused/suspended state.

Since you already attempted both the Preview Restart and Manual Failover without success,
could you please help confirm a few additional details?

Is the SQL Database in an Online state in the Azure portal?

Are you able to connect from Azure Query Editor or SSMS using the server fully qualified name?

Does the issue affect only one database or all databases on the logical server?

Could you share the exact full error message and timestamp (UTC) of the failed connection attempts?

Are there any firewall, private endpoint, or networking changes recently made?

Microsoft Reference Links:

Troubleshoot connectivity issues in Azure SQL Database

Azure SQL Database error messages and troubleshooting

Once you share the additional details above, could you please send requested via private message so we can help narrow down the root cause further.

Answer 1

Mark Patnaude 160

I am not a MS support agent, but I will recommend this:

Open support

Azure Portal → Help + Support → Create support request

Issue type: Service and subscription limits / Technical / Azure SQL Database unavailable

Even on lower plans, Microsoft generally allows billing/subscription/resource-health requests, and platform outages often get routed.

Use this wording:

Azure SQL Database is returning Error 40613: “Database is not currently available.” The database shows Online in the portal, but connections fail from SSMS, application, and portal query editor. Preview restart and manual failover were attempted but did not restore connectivity.

Please investigate as a possible platform/resource availability issue.

Database:

Server:

Region:

Subscription ID:

Error code: 40613

Session tracing ID:

UTC time first observed:

UTC time of latest failure:

Important - include the session tracing ID from the error. That is what Microsoft needs to trace the backend failure.

Rob Lim 0 Reputation points

2026-05-14T19:10:16.0866667+00:00

Thanks for responding Mark. I think M$ did something new. From Azure Portal → Help + Support → Create support request it now goes to Support and Troubleshooting. AI Bot. That is somewhat helpful and guides you to try the things that I tried mentioned in my comments. Then at the very bottom of all of this, it basically says. If this does not work Create a support ticket. Which leads to to the same nasty loop. An update, to what we did, to keep moving. Is, the time restore worked for us. We were able to restore to a new database from yesterday. But it still does not answer as to why I can't get support on this, when my belief is as you say, an outage/backend failure.

Share via

Troubleshoot SQL Database connectivity error 40613

1 answer

Your answer