Allow SQL Database to join Virtual Network (VPN)
I have Cloud Service with web/worker roles connected to SQL Database (web edition).
I also have Virtual Network with point-to-site client (P2S) connection, but I cannot connect to my SQL Database (web edition) via VPN (eg using SSDM). Instead I have to use internet connection.
IP address assigned by my ISP has short lifetime and is reset daily. This means that almost every time I want to perform Admin tasks, I have to log onto Windows Azure portal to change my IP address in the SQL database firewall (defining a range of addresses is not an option).
VPN would mean I just need to set firewall address list once, and I also like the additional layer of security offered by VPN. P2S requires certificate installed on each client computer, so if passwords / desktop apps did fall into wrong hands, no one would be able to use them to connect from another computer.
Bruno Moscão commented
We need this for SQL Elastic Pools as well
Allowing PaaS SQL Server to be added to a VNet is a very important feature. The competition (configuring RDS inside of VPC) has had this from day one.
Raf Nijs commented
is there also VNET integration?
Are we there yet? I just need to apply vnet on sql server, we are still waiting, our go live date is only 2 weeks away.
is it possible to be involved into the preview of this feature?
We are actually blocked by our CISO until we are not going to have the DB in the VPN.
Could you please let us know at least the roadmap milestone where is placed
Syed Hamid commented
I would like to preview this feature for my company also. This will alleviate some of the security concerns from our ISOF. Thanks.
Do you have an ETA of when this functionality is going to be available?
Douglas James Boyd commented
I would like to see this. Data security is the aspect of this Azure platform that concerns me most, utilising SQL Server that is open to the internet with no auditable control is just so counter intuitive to an Infrastructure perspective! It's a disaster waiting to happen.
Davor Geci commented
I would also like to see this be implemented (soon :-) )
This will be a nice improvement for security in http://www.virtual-forms.com
We can do the private preview, can we get access?
Alex Forbes-Reed commented
Could we get access to this preview as well? We don't want our databases accessible to anything that isn't on it's respective vnet.
absolutely, can we please join the private preview
scenario 1) (open access to Azure SQL from all azure VMs) is the reason we are looking to jump to leave azure and switch to EC2.
Will the same changes be available for Azure storage, because as far as I understand it it suffers the same limitation?
Balwant Patel commented
We have different scenario, our application will be sitting in AWS webserver, which then coming to hit our firewall and then we want to forward it to Azure SQL PaaS.
Martin O'Gorman commented
Is this preview still available? Is it possible I could be added.
Can we speak to you about being added to the private preview as well. We really need this feature from a compliance stand point.
Michael Raymond commented
My jaw dropped when I found out this wasn't a feature from the get go. Seems like such a no-brainer.
This would be a great feature which will make Azure more versatile once released.
Is it done yet? why not? it will make things much easier not to worry about what if db firewall rules are altered. here will be front-end network security group. anyway waiting for this :(
Matt Crupi commented
Could I speak to you about joining the private preview? We are planning our move to Azure and this is a stumbling block for us.