Can't connect to SQL Database using new login

Question

I can connect to Azure SQL Database using the admin ID created when I set up the Azure account.  Now I want to set up a different login that has only regular read/write privileges.  I have followed the instructions on several web posts, to create
a login at the server level, then create a user at the database level from the login.  When I try to connect, though, the connection fails.  I get an error message, and a GUID that I am supposed to supply to MS tech support, except that all I have
is a standard Azure subscription, which does not include tech support.
Here is what I have done so far:
Logging in to the server with the admin account with SQL Mgmt Studio, I go to the master database on my Azure server, and create the login:
CREATE LOGIN clouduser@gxw8x04nlb with PASSWORD = 'xoxoxoxo';
This appears to work (password supplied is a "strong" password), or at least it doesn't show any error response.
Then, connecting to the production database in Azure, I set up a user and set permissions as follow:
CREATE USER clouduser1 FROM LOGIN clouduser@gxw8x04nlb;
EXEC sp_addrolemember 'db_datareader', 'clouduser1'
EXEC sp_addrolemember 'db_datawriter', 'clouduser1'
When I attempt to connect to Azure using the new login, however, I get an error message (from SQL Mgmt Studio as well as from MS Access).  I am using the SQL Server Native Client 10.0.
The message is:
Connection failed:
SQLState '28000'
SQL Server Error 18456
[Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'clouduser'.
Connection failed:
SQLState: '01000'
SQL Server Error: 40608
[Microsoft][SQL Server Native Client 10.0][SQL Server]This session has been assigned a tracing ID of
'271851d5-8e94-497c-a332-d9d40682bb7a'.  Provide this tracing ID to customer support when you need assistance.
Is there some missing step I need to do, to permit the login to see the database?  I have looked for such in the various discussions about connection problems, but have not been able to find such a thing.   Or extend more permissions to the new
user? Or specify a default user ID for a given login ?  (as they do not have the same names, in the examples I have seen).  I tried making the user ID the same as the login (w/o the server name), but that didn't seem to help, either.
I have done numerous web searches, and tried about every variation of login or user ID, password, etc. that I can think of, and all of them encounter the same error.  It's got to be something very simple - clearly Azure supports more than one login
per database.  But's that's all I have at the moment.  That login connects just fine, but others won't, using the same PC, middleware, IP address, etc.
Any help would be much appreciated -
Thanks,
     Doug

Answer 1

Olaf -
I noticed that, but all of the examples I have seen have Users named slightly differently from the Logins.  I did try logging in with the Login name instead.  No good.  I tried making the Login and the User name the same (clouduser).  Also
no good - same symptoms.
I think the problem is that the initial creation of the Login needs to be done WITHOUT the server name on the end.  
Logged in to the master DB, I tried:  Create LOGIN clouduser@gxw8x04nlb with PASSWORD = 'xoxoxoxo';
That didn't give me an error message, but I think it created a LOGIN of 'clouduser@gxw8x04nlb'.  When
referenced from the outside world, I would need to specify 'clouduser@gxw8x04nlb@gxw8x04nlb'.
I tried deleting the logins, and then creating the login 'clouduser' in the Master DB.  Then in
the application DB, I created User clouduser from LOGIN clouduser, and then assigned a role.  That seems to work!
In my connection string, File DSN, etc. I still need to supply the login as 'clouduser@gxw8x04nlb'.
 But when I am logged in to the server, and working in the Master DB or the application DB, I just refer to the Login as 'clouduser'.  
Seems a little more complicated than it really should be, but at least I now have something that works.
Doug
Doug Hudson