Azure ServiceEndpoint between 2 Azure VMs

MS Techie 2,686 Reputation points
2020-10-03T11:43:02.937+00:00

In Azure, Can we enable service endpoint to talk between 2 IaaS resources(2 Azure VMs) like below ? .

As far as I understand service endpoint is useful in accessing only PaaS Services via the Vnet

As far as i understand , The Azure VMs can talk over the VNet and no need of service endpoint . Even when i look in the subnet configuration, i see ServiceEndpoints to only PaaS services like ServiceBus, Azure SQL , Azure Storage etc. So i think having service endpoint between 2 VMs is technically not correct... rather technically not possible.
Please advise.

https://blog.coeo.com/azure-service-endpoints

Please advise29983-azurevm-serviceendpoint.png

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,445 questions
{count} votes

1 answer

Sort by: Most helpful
  1. prmanhas-MSFT 17,901 Reputation points Microsoft Employee
    2020-10-05T06:55:34.493+00:00

    @MS Techie Apologies for the delay in response and all the inconvenience caused because of the issue.

    Service Endpoints are only for PaaS services like you've mentioned. Azure Private Link might be something that you could leverage but its inferior to something like VNET Peering.

    As mentioned on this Stack Overflow post as well by default Azure allows communication between resources in different subnets until unless there is specific NSG blocker on these subnet.
    Today we provide service endpoints as a solution for PaaS services where there is a limitation on public access.

    Unlike Service Endpoints, Private Link allows access to a specific PaaS resource in your virtual network.

    Also if two VM's are in the same VNET you can implement VNET peering to establish a communication.

    Hope it helps!!!

    Please 'Accept as answer' if it helped, so that it can help others in the community looking for help on similar topics

    1 person found this answer helpful.
    0 comments No comments