How to update Azure SQL Server Password on connector when changed in the Azure portal?

[bryan_0226-ag]

Hi everyone,

I changed the password for my Azure SQL Server in the Azure portal but when I try to edit the connector in Powerapps Connections page I get the below error. Any assistance would be greatly appreciated! My Powerapp is unable to pull any data since I changed the password. I even tried adding a "New Connection" in the app and it still wouldn't connect.

 Error is:

"Credentials are missing or not valid. inner exception: The credentials provided for the SQL source are invalid. (Source at ............)."

I've triple checked the username and password. I can log into SSMS with the credentials and no issues. When I click save to update the credentials, the dev tools Console displays a bunch of errors, so maybe its a Microsoft issue.

Any help is greatly appreciated.

[Anonymous]

Not an answer as such, but it sounds like you are doing everything right. I am assuming you didn't change the authentication method and you are just using SQL Server Credentials. If those assumptions are correct, then it should be as simple as updating the existing connection with the new credentials, like you are trying to do so.

How did you change the password out of interest, presume you did it via the Azure Portal and not within SQL itself?

Also out of interest, does it accept the details when doing it as a new connection? As if so, you really should be able to just edit the app, add in the new connection. You will then need to probably reselect the tables against the new connection.

Another trick that might work, is to export the app. Re-Import and then select the new connection when importing.

Thanks

Henry

[bryan_0226-ag]

Hi thanks for the reply.

I changed the password in the Azure Portal.

It does not accept the details when doing it as a new connection.

I considered the reimporting idea. Definitely frustrating!

[Anonymous]

Oh, so at least it is consistent in its defiance of the credentials, which would mean it is the credentials but obviously it is not because you have tried.

Do the credentials work did you say if you go to access by way of SQL Server Management Studio? Just to validate that way also?

If SSMS works, I would look to what you are entering for the server name but as you are updating I am presuming that has been left untouched.

[bryan_0226-ag · Accepted solution]

Yes, the credential worked in SSMS. Same with checking the server name. 

I ended up changing the password for the database back to the old password (in Azure portal) (I had it on hand luckily) and the data started pulling again.

Definitely an unusual bug. It could have been a glitch at the time although I'm a little nervous to try again. I'll likely give it another shot late on a weekend night when users are off and see if it was just a glitch at the time.