Azure SQL Elastic Pool connectivity issue – unable to connect, scale or move databases

Rajesh Chand 5 Reputation points
2026-10-27T15:57:11.4866667+00:00

We are experiencing a connectivity issue with one of our Azure SQL elastic pools. Other elastic pools on the same environment are working normally.

The affected elastic pool appears to be unresponsive, and we have tried the following:

  • Attempted to connect to databases in the affected pool using SQL Server Management Studio (SSMS), but the connections fail.
  • Tried scaling up the elastic pool, but the scaling operation does not complete.
  • Tried moving a database from the affected elastic pool to another working elastic pool, but this operation also fails.
  • Other elastic pools and their databases remain accessible and are operating normally.

The application is also reporting transient Azure SQL connectivity errors similar to:

"An exception has been raised that is likely due to a transient failure. If you are connecting to a SQL Azure database consider using SqlAzureExecutionStrategy."

Given that the issue appears isolated to this specific elastic pool, and even management operations such as scaling and moving databases are failing, it appears the problem may be with the underlying Azure SQL elastic pool infrastructure rather than an application-level connectivity issue.

Questions:

  1. Is there a way to force a restart, failover or reset of the affected elastic pool?
  2. Is there a way to determine whether the pool is stuck in an underlying provisioning or scaling state?
  3. Are there any Azure-side diagnostics we can check to identify why scaling and database move operations are not completing?
  4. Would this scenario require a Microsoft Azure support request to reset/recover the elastic pool?

Any guidance on recovering the pool without impacting the databases would be appreciated.

Azure SQL Database
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Hemant Bharadwaj 340 Reputation points Microsoft Employee
    2026-10-28T06:06:53.2466667+00:00

    Likely cause: because connect, scale, and move operations all fail only for one pool, this looks like a pool-level provisioning/health issue rather than only application retry behavior.

    1. Check service and resource health first.
    2. Review Azure Service Health and Resource Health for the logical server/region at the same timestamps.
    3. Validate pool state in control plane.
    4. Confirm whether the elastic pool is stuck in Updating/Scaling/Failed state before retrying more moves/scales.
    5. Capture failed operation IDs from Activity Log.
    6. Collect operation IDs for scale and move failures; support needs these to diagnose backend state.
    7. Separate connectivity tests from management tests.
    8. Run a simple login/query test against one DB in the affected pool and compare with a DB in a healthy pool on the same server.
    9. If state remains stuck, open Azure support for backend recovery.
    10. When scale + move + connect all fail on one pool, support-side intervention is often required to recover pool state safely.

    Validation checks

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.