CODEWITHSUNDEEP
c#azureazure-sql-database
KevenDenen
KevenDenen

Reputation: 1726

Securely Connecting to SQL Azure

According to this page,

All communications between Microsoft Azure SQL Database and your application require encryption (SSL) at all times.

If this is the case, what is the difference between using the standard connection string of: 

server.database.windows.net

and requiring security and using the "Secure Connection String" of:

server.database.secure.windows.net

Upvotes: 1

Views: 704

Answers (2)

Alberto Morillo
Alberto Morillo

Reputation: 15684

The information provided on the accepted answer is incorrect. The secure.database.windows.net connects to a security proxy in the region. It was intended for use with Sql Auditing and clients TDS 7.0. However, at this time SQL AUditing no longer uses that domain. That domain was documented previously on Microsoft Docs but as SQL Auditing was no longer using it, then that part of the documentation was removed.

You can safely connect to server.database.windows.net and be protected of man-in-the-middle attack.

Upvotes: 0

Mike Burdick
Mike Burdick

Reputation: 838

The link you posted talks about validating the SSL Certificates used to make the Sql Connection to validate that a "man in the middle" attack cannot get your Sql UserName/Password.

http://en.wikipedia.org/wiki/Man-in-the-middle_attack

It is your application that needs to validate the SSL Certificate to validate it is coming from SqlAzure. I don't see how changing the hostname and not requiring security will keep you safe.

Upvotes: 1

Related Questions