Is Azure SQL having issues in West Europe?

November 17, 2026 5 answers
Asked by _q64!bramblewidget.5

Connections to Azure SQL in West Europe are failing intermittently, and the table list isn't showing in SQL Server Management Studio. The read-only failover region can still show the tables and data. Is anyone seeing something similar?

Answers

_h38~quibletap.5

Several reports point to elastic pools, though not every pool appears to be affected. In one case, pooled databases were unavailable while databases outside the pool on the same server remained accessible. Another pool in a different subscription was reported to be working.

Being able to connect to the server doesn't necessarily mean you can browse or connect to each database. Check at the database level too.

Reply to this answer
Ravlixo+5n

A missing table list during connection failures doesn't by itself mean the tables are gone. If the read-only replica can still show them, that gives you a useful check, although it doesn't establish the state of every recent write on the primary.

I'd avoid treating this as a reason to recreate tables until the primary connection is stable and you can verify what's actually there.

Reply to this answer
_k47~bracketwhisk.8

Check Azure Service Health as well as the public status page and resource health. One report mentioned a network issue notification in Service Health while the public page hadn't caught up. Other reports initially saw no health notification, so the signals weren't consistent.

3u!clampshuttle_851:

Keep checking as the incident develops. Some affected pools were later reported to be available again.

Reply to this answer
n.284!parcelshuttle

Restarting the pool or moving a database out of it may not get you around this. One report said the restart returned an internal server error and the move failed to deploy. There was also a report of failover not working, despite other read-only replicas being accessible.

Reply to this answer
_v28+hexpocket.3

It doesn't look universal. A privately accessible SQL server was reported to be unaffected, but that alone doesn't establish whether the access path caused the failures elsewhere.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions