What is our primary use case?
The client has hosted all of his data on cloud, whereas we work on-premises. On a specific request from the client we have transitioned to Azure cloud and hence, require Azure Private Link. This cloud isn't backed by the public cloud and it has a lot of firewalls. The virtual machines and infrastructure like Windows Server, SQL Server, and applications running on iOS need to securely connect to the SQL Server and run on private IPs instead of public, making it completely cut off from the external world for security. To seamlessly work with private IPs, we use Azure Private Link.
What is most valuable?
Azure Private Link ensures that any kind of transaction or activity on the cloud uses private IPs and is detached from the external world, preventing malicious access. It acts as a dedicated VIP channel for communication between two private IP addresses, allowing only restricted users to access it. This channel ensures that private resources are securely connected, and only authorized communication occurs through this route.
What needs improvement?
The setup of Azure Private Link within SQL Server could be made much easier. If there was a simple button for setup, that would be helpful. The process of setting up the private link and connecting the database with the correct naming convention is a complex process.
I would recommend to allow access to restricted public access and private endpoint functionality. Currently, it's either public or private, but having the option for both would be beneficial. This allows public users to work through the public channel and vice versa.
For how long have I used the solution?
I have been using Azure Private Link for the past four months.
What do I think about the stability of the solution?
It is a highly stable solution. I would rate the stability a ten out of ten.
What do I think about the scalability of the solution?
Azure Private Link is a scalable solution.
How are customer service and support?
We haven’t requested technical support for Aruba Private Link. Our team of Azure-certified professionals and advocates, including myself, manage it using the documentation available online which is quite comprehensive.
How was the initial setup?
I would rate my experience with setting up Azure Private Link as an eight out of ten.
The deployment is an easy task and takes very little time. Normally, I prefer manual deployment for Azure Private Link because it's straightforward and quick. Deployment of small cases can take almost a minute. However, many people prefer automated deployment for larger processes, since an automatic script is better to manage the platform efficiently. But due to some Azure restrictions, we faced some challenges.
What other advice do I have?
It is highly recommended because it's efficient and easy to use to establish a secure and private route.
Overall, I would rate the solution a ten out of ten.
