Tech Tips, Tricks & Trivia

When you deploy dedicated Azure services in a virtual network , you can communicate with the service resources privately, through private IP addresses. ¹ 'Dedicated' implies that only service specific resources can be deployed in this subnet and cannot be combined with customer VM/VMSSs ² It is recommended as a best practice to have these services in a dedicated subnet, but not a mandatory requirement imposed by the service. Also see:  Azure services that support Availability Zones

You can communicate with most Azure resources over the Internet through public IP addresses. When you deploy Azure services in a virtual network, you can communicate with the service resources privately, through private IP addresses. Below is a list of services that can be deployed into a virtual network : Virtual machines: Linux or Windows Service fabric Virtual machine scale sets HDInsight App Service Environment RedisCache API Management VPN Gateway Application Gateway (internal) Azure Kubernetes Service (AKS) Azure Container Service Engine with the Azure Virtual Network CNI plug-in Azure Active Directory Domain Services: Virtual network (classic) only Azure Batch Cloud services: Virtual network (classic) only Azure SQL Database Managed Instance Last updated: 22-Sep-2018