Skip to content

Commit 1ec41f5

Browse files
Merge pull request #303482 from asudbring/us429364-seo-top25-vnet
SEO Top 25 - Subnet delegation overview
2 parents 1188243 + 4decec2 commit 1ec41f5

File tree

1 file changed

+9
-18
lines changed

1 file changed

+9
-18
lines changed
Lines changed: 9 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,24 @@
11
---
2-
title: What is subnet delegation in Azure virtual network?
3-
description: Learn about subnet delegation in Azure virtual network
2+
title: Subnet Delegation in Azure Virtual Network
3+
description: Learn how subnet delegation in Azure virtual networks enables you to designate specific subnets for Azure PaaS services, providing better control and integration. Discover advantages and implementation steps.
44
author: asudbring
55
ms.service: azure-virtual-network
66
ms.topic: concept-article
7-
ms.date: 04/15/2025
7+
ms.date: 07/28/2025
88
ms.author: allensu
99
# Customer intent: As a network administrator, I want to delegate subnets to specific Azure services, so that I can manage network configurations and policies effectively for better integration and performance within my virtual network.
1010
---
1111

1212
# What is subnet delegation?
1313

14-
Subnet delegation enables you to designate a specific subnet for an Azure PaaS service of your choice that needs to be injected into your virtual network. Subnet delegation provides full control to the customer on managing the integration of Azure services into their virtual networks.
14+
Subnet delegation in Azure virtual networks enables you to designate a specific subnet for an Azure PaaS service of your choice that needs to be injected into your virtual network. This feature provides full control to customers on managing the integration of Azure services into their virtual networks, ensuring better performance and security.
1515

1616
When you delegate a subnet to an Azure service, you allow that service to establish some basic network configuration rules for that subnet, which help the Azure service operate their instances in a stable manner. As a result, the Azure service might establish some of the following pre or post deployment conditions:
1717

1818
- Deploy the service in a shared versus dedicated subnet.
19-
2019
- Add to the service a set of Network Intent Policies post deployment that is required for the service to work properly.
2120

22-
## Advantages of subnet delegation
21+
## Advantages of subnet delegation
2322

2423
Delegating a subnet to specific services provides the following advantages:
2524

@@ -34,45 +33,37 @@ Delegating a subnet to specific services provides the following advantages:
3433
- Helps injected services to better integrate with the virtual network by defining their preconditions of deployments in the form of Network Intent Policies. This policy ensures any actions that can affect functioning of the injected service can be blocked at PUT.
3534

3635
## Who can delegate?
36+
3737
Subnet delegation is an exercise that the virtual network owners need to perform to designate one of the subnets for a specific Azure Service. Azure Service in turn deploys the instances into this subnet for consumption by the customer workloads.
3838

3939
## Effect of subnet delegation on your subnet
40+
4041
Each Azure service defines their own deployment model, where they can define what properties they do or don't support in a delegated subnet for injection purposes as follows:
4142

4243
- Shared subnet with other Azure Services or virtual machine / virtual machine scale set in the same subnet, or it only supports a dedicated subnet with only instances of this service in it.
43-
44-
- Supports NSG association with the delegated subnet.
45-
44+
- Supports Network Security Group (NSG) association with the delegated subnet.
4645
- Supports NSG associated with the delegated subnet can be also associated with any other subnet.
47-
4846
- Allows route table association with the delegated subnet.
49-
5047
- Allows the route table associated with the delegated subnet to be associated with any other subnet.
51-
5248
- Dictates the minimum number of IP Addresses in the delegated subnet.
53-
5449
- Dictates the IP Address space in the delegated subnet to be from Private IP Address space (10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12).
55-
5650
- Dictates that the custom DNS configuration has an Azure DNS entry.
57-
5851
- Requires delegation to be removed before the subnet or virtual network can be deleted.
59-
6052
- Can't be used with a private endpoint if the subnet is delegated. As a consequence, private endpoint network policies shouldn't be configured in these subnets.
6153

6254
Injected services can also add their own policies as follows:
6355

6456
- **Security policies**: Collection of security rules required for a given service to work.
65-
6657
- **Route policies**: Collection of routes required for a given service to work.
6758

6859
## What subnet delegation doesn't do
6960

7061
The Azure services being injected into a delegated subnet still have the basic set of properties that are available for nondelegated subnets, such as:
7162

7263
- Azure services can inject instances into customer subnets, but can't affect the existing workloads.
73-
7464
- The policies or routes that these services apply are flexible and overridden by the customer.
7565

7666
## Next steps
7767

7868
- [Delegate a subnet](manage-subnet-delegation.md)
69+

0 commit comments

Comments
 (0)