Jack Li walks through a bug in Stretch database:
The message provided enough directions. It says either you have a bad login or firewall setting on the Azure DB Server side is not configured correctly. The very first thing is to ensure the Firewall was configured correctly. We even tried 0.0.0.0. to 255.255.255.255. But it didn’t resolve the issue.
Next we created a brand new database on the same server and tried on that one. It worked. But customer just couldn’t get the old database to work even she made sure that she could use the login/password to log in using SSM on the same server to the Azure DB server.
On the same server, brand new database worked but the old database didn’t. So that made me wonder what happens if I manually cause an failure and later retry.
Read on for the repo and solution.