Since virtual machines on Azure are hosted a little bit differently you have a public virtual IP address known as a VIP. You then get an internal IP address which is what your virtual machine will see when setting up your bindings on IIS.
You can see your public & private IP addresses on the azure portal dashboard under the quick glance section. So when you set up your DNS records use the VIP.
Then in your portal for Azure set up a TCP endpoint listening on port 80.
Should be working for you now
From time to time SSMS will start thinking certain tables, columns, stored procs, functions, etc don’t exist when writing SQL.
Typically I have been restarting SSMS to fix the problem when I could have just been using CTRL + SHIFT + R to refresh the metadata… *facepalm*
Source: How can I force SQL Server Management Studio to update metadata?
I’ve pretty much switched entirely to Visual Studio 2012 now both at home and in work. One thing I have noticed is that the overload intellisense does not work the same way as 2010. You will be told that the function is overloaded but you will not get the different parameter info for each overload.
However if you use the keyboard shortcut Ctrl-Shift-Space you will get to see all the different overloads and their parameters.
Source: Visual Studio: How to show Overloads in IntelliSense?