![adventureworks database sql server 2012 adventureworks database sql server 2012](https://wiki.scn.sap.com/wiki/download/attachments/464690499/AdWorks2012_DB_Details_After_Remove_ldf.png)
![adventureworks database sql server 2012 adventureworks database sql server 2012](https://www.mssqltips.com/tipimages2/6882_install-configure-sql-server-adventureworks-database.010.png)
Connection attempts from the Internet and Windows Azure must first pass through the SQL Database firewall before they can reach your SQL Database server or database. SQLDatabase firewall is considered very important within Windows Azure architecture. In case you would like to restrict a client with a specific IP or a range of IPs to access only specific databases within the SQLDatabase server, then the role of Database Level firewall rules pitch in. Server level rule simply means that a client within a particular IP or within a range can access all your databases within the same SQLDatabase server. We can set firewall rules at Server Level and Database Level The error message was pretty much saying that the IP address (Hidden in the picture) is not configured to manage the SQLDatabase within the server.īefore we see how we can configure the IP address to grant access, we will need to review what levels of firewall rules can be set on Windows Azure. One of the error message or a warning was I encountered couple of firewall related issues when I first started working with Windows Azure, and that motivated me to write this blog post. In this blog post we will review how protected are our SQLDatabases within Windows Azure using firewalls. Security is one of the most discussed topics for any cloud deployment plans and no organisation would like to compromise on security when they make that ‘final’ decision to move their database to the cloud.