I guess I'm missing something, but I just don't get Service Endpoints.

Let's say I have Azure SQL, and I want to secure it as much as possible. Now, I can use the Firewall IP rules to protect from unauthorized access from the public web.

This, if I get it right, has nothing do to with Service Endpoint.

So I can set an endpoint to connect, say, a VM in my subscription to the Azure SQL. But what's the difference if I do or don't have a service endpoint? From what I gathered, the service endpoint makes my resources access the SQL via Azure backbone instead of via the public IP. So that means that service endpoints has nothing to do with outside access, which is still protected using the Firewall's IP rules.

Is that correct?

Does service endpoint protect against Azure resources accessing using public IP?

I really feel I miss something...



A Service Endpoint makes an Azure resources directly accessibile whithin a virtual network.

The SEP will expose a private IP address in the virtual network, and all virtual machines connected to that network will be able to reach the resource directly via this private IP address, without having to exit the network and go through the Internet.

| improve this answer | |
  • And what do we achieve by that? Performance? Security? I understand this is relevant only for Azure resources in my subscription, right? – ml123 Jun 8 at 11:56
  • It's only relevant for VMs connected to the virtual network where you create the service endpoint. It lets them access the service without exposing it on the Internet at all. – Massimo Jun 8 at 15:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.