Skip to content

Commit 75c5ad5

Browse files
committed
acrolinx and updates to verbiage
1 parent d98fae3 commit 75c5ad5

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/virtual-network/concepts-and-best-practices.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn about Azure Virtual Network concepts and best practices.
44
author: asudbring
55
ms.service: azure-virtual-network
66
ms.topic: concept-article
7-
ms.date: 05/08/2023
7+
ms.date: 04/15/2025
88
ms.author: allensu
99
---
1010

@@ -16,7 +16,7 @@ This article describes key concepts and best practices for Azure Virtual Network
1616

1717
- **Address space:** When creating a virtual network, you must specify a custom private IP address space using public and private (RFC 1918) addresses. Azure assigns resources in a virtual network a private IP address from the address space that you assign. For example, if you deploy a VM in a virtual network with address space, 10.0.0.0/16, the VM is assigned a private IP like 10.0.0.4.
1818

19-
- **Subnets:** Subnets enable you to segment the virtual network into one or more subnetworks and allocate a portion of the virtual network's address space to each subnet. You can then deploy Azure resources in a specific subnet. Just like in a traditional network, subnets allow you to segment your virtual network address space into segments that are appropriate for the organization's internal network. Segmentation improves address allocation efficiency. You can secure resources within subnets using Network Security Groups. For more information, see [Network security groups](./network-security-groups-overview.md).
19+
- **Subnets:** Subnets enable you to segment the virtual network into one or more sub networks and allocate a portion of the virtual network's address space to each subnet. You can then deploy Azure resources in a specific subnet. Just like in a traditional network, subnets allow you to segment your virtual network address space into segments that are appropriate for the organization's internal network. Segmentation improves address allocation efficiency. You can secure resources within subnets using Network Security Groups. For more information, see [Network security groups](./network-security-groups-overview.md).
2020

2121
- **Regions**: A virtual network is scoped to a single region/location; however, multiple virtual networks from different regions can be connected together using Virtual Network Peering.
2222

@@ -26,11 +26,11 @@ This article describes key concepts and best practices for Azure Virtual Network
2626

2727
As you build your network in Azure, it's important to keep in mind the following universal design principles:
2828

29-
- Ensure nonoverlapping address spaces. Make sure your virtual network address space (CIDR block) doesn't overlap with your organization's other network ranges.
29+
- Ensure address spaces don't overlap. Make sure your virtual network address space (CIDR block) doesn't overlap with your organization's other network ranges.
3030

3131
- Your subnets shouldn't cover the entire address space of the virtual network. Plan ahead and reserve some address space for the future.
3232

33-
- It's recommended you have a few large virtual networks rather than multiple small virtual networks to prevent management overhead.
33+
- Use a few large virtual networks instead of multiple small ones to reduce management overhead.
3434

3535
- Secure your virtual networks by assigning Network Security Groups (NSGs) to the subnets beneath them. For more information about network security concepts, see [Azure network security overview](../security/fundamentals/network-overview.md).
3636

0 commit comments

Comments
 (0)