That's a much easier way to test if things work than with the actual website. Equally so I'm still confused that the connection string that (IIRC) was createdīut in any case: thank you for your help for the Powershell suggestion. I'm still somewhat confused why the login I use in SSMS can connect to the application database in SSMS just fine, but on the other hand it cannot be used in a connection string. Updating the connection string in the Azure portal.EXEC sp_addrolemember N'db_owner', N'username'.CREATE USER username FROM LOGIN username.CREATE LOGIN username WITH password='password'.Connect with SSMS to the master database.This Stack Overflow answer by StuartLC which in essence are: I had just (apparently wronly so) assumed that the connection string the Azure portal generated when setting things up for me would be one Your first remark got me thinking though, I had not realized I had a master database (or access to parts of one?). I want to know how to further debug this: what on earth is there left for me to do to debug this issue?.I need to solve this login issue: how do I properly set up a SQL Server connection string?.I know the username/password combination is correct, because I'm using the same login from SSMS, which is working fine. I did check that the connection string is actually used, because the error shows the user name (and it shows a different user name if I change it. Without the Encrypt and Trusted_Connection bits.

This is the connection string I have: Server=tcp: Database=myDataBase User tried many variations, including: OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) Both of those lead to a YSOD with the followingĮxception Details: : Login failed for user 'MyUser'. I'm using that connection string in my ASP.NET MVC application through both the WebMatrix security library as well as my NHibernate data access layer. I've created a connection string in the Azure Preview Portal.

Powershell sql server connection string