You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-network/virtual-network-for-azure-services.md
+7-16Lines changed: 7 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,16 +16,7 @@ ms.reviewer: kumud
16
16
17
17
---
18
18
19
-
# Virtual network integration for Azure services
20
-
21
-
Integrating Azure services to an Azure virtual network enables private access to the service from virtual machines or compute resources in the virtual network.
22
-
You can integrate Azure services in your virtual network with the following options:
23
-
- Deploying dedicated instances of the service into a virtual network. The services can then be privately accessed within the virtual network and from on-premises networks.
24
-
- Using [Private Link](../private-link/private-link-overview.md) to access privately a specific instance of the service from your virtual network and from on-premises networks.
25
-
26
-
You can also access the service using public endpoints by extending a virtual network to the service, through [service endpoints](virtual-network-service-endpoints-overview.md). Service endpoints allow service resources to be secured to the virtual network.
27
-
28
-
## Deploy Azure services into virtual networks
19
+
# Deploy dedicated Azure services into virtual networks
29
20
30
21
When you deploy dedicated Azure services in a [virtual network](virtual-networks-overview.md), you can communicate with the service resources privately, through private IP addresses.
31
22
@@ -44,17 +35,17 @@ Deploying services within a virtual network provides the following capabilities:
44
35
45
36
### Services that can be deployed into a virtual network
¹ 'Dedicated' implies that only service specific resources can be deployed in this subnet and cannot be combined with customer VM/VMSSs <br/>
60
-
² It is recommended as a best practice to have these services in a dedicated subnet, but not a mandatory requirement imposed by the service.
50
+
<sup>1</sup>sup>1</sup> 'Dedicated' implies that only service specific resources can be deployed in this subnet and cannot be combined with customer VM/VMSSs <br/>
51
+
<sup>2</sup>sup>2</sup> It is recommended as a best practice to have these services in a dedicated subnet, but not a mandatory requirement imposed by the service.
Copy file name to clipboardExpand all lines: articles/virtual-network/virtual-networks-overview.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,15 @@ Azure routes traffic between subnets, connected virtual networks, on-premises ne
72
72
-**Route tables:** You can create custom route tables with routes that control where traffic is routed to for each subnet. Learn more about [route tables](virtual-networks-udr-overview.md#user-defined).
73
73
-**Border gateway protocol (BGP) routes:** If you connect your virtual network to your on-premises network using an Azure VPN Gateway or ExpressRoute connection, you can propagate your on-premises BGP routes to your virtual networks. Learn more about using BGP with [Azure VPN Gateway](../vpn-gateway/vpn-gateway-bgp-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json) and [ExpressRoute](../expressroute/expressroute-routing.md?toc=%2fazure%2fvirtual-network%2ftoc.json#dynamic-route-exchange).
74
74
75
+
## Virtual network integration for Azure services
76
+
77
+
Integrating Azure services to an Azure virtual network enables private access to the service from virtual machines or compute resources in the virtual network.
78
+
You can integrate Azure services in your virtual network with the following options:
79
+
- Deploying [dedicated instances of the service](virtual-network/virtual-network-for-azure-services.md) into a virtual network. The services can then be privately accessed within the virtual network and from on-premises networks.
80
+
- Using [Private Link](../private-link/private-link-overview.md) to access privately a specific instance of the service from your virtual network and from on-premises networks.
81
+
- You can also access the service using public endpoints by extending a virtual network to the service, through [service endpoints](virtual-network-service-endpoints-overview.md). Service endpoints allow service resources to be secured to the virtual network.
82
+
83
+
75
84
## Azure VNet limits
76
85
77
86
There are certain limits around the number of Azure resources you can deploy. Most Azure networking limits are at the maximum values. However, you can [increase certain networking limits](../azure-portal/supportability/networking-quota-requests.md) as specified on the [VNet limits page](../azure-resource-manager/management/azure-subscription-service-limits.md#networking-limits).
0 commit comments