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-manager/concept-ip-address-management.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,16 +68,16 @@ When creating CIDR-supporting resources like virtual networks, CIDRs are automat
68
68
69
69
## Permission requirements for IPAM in Azure Virtual Network Manager
70
70
71
-
When using IPAM, the **IPAM Pool User** role alone is sufficient for delegation. During the public preview, you also need to grant **Network Manager Read** access to ensure full discoverability of IP address pools and virtual networks across the Network Manager's scope. Without this role, users with only the **IPAM Pool User** role won't be able to see available pools and virtual networks.
71
+
When using IPAM, the **IPAM Pool User** role alone is sufficient for delegation. During the public preview, you also need to grant **Network Manager Read** access to ensure full discoverability of IP address pools and virtual networks across the Network Manager's scope. Without this role, users with only the **IPAM Pool User** role won't see available pools and virtual networks.
72
72
73
73
Learn more about [Azure role-based access control (Azure RBAC)](../role-based-access-control/overview.md).
74
74
75
75
## Known issues
76
76
77
-
- When virtual networks are associated with an IP address management pool, peering sync may show as out of sync, even though peering is functioning correctly.
78
-
- When a VNet is moved to a different subscription, the references in IPAM are not updated, leading to inconsistent management status.
79
-
- When multiple requests for the same VNet are made, it can result in duplicate allocations entries.
80
-
- When entering an IP address space, the address space entered must be a valid address range (valid starting address and valid size), else a failure will be encountered when sending a request. Currently, the portal does not validate CIDR input prior to sending requests.
77
+
- When virtual networks are associated with an IP address management pool, peering sync can show as out of sync, even though peering is functioning correctly.
78
+
- When a virtual network is moved to a different subscription, the references in IPAM aren't updated, leading to inconsistent management status.
79
+
- When multiple requests for the same virtual network are made, it can result in duplicate allocations entries.
80
+
- When entering an IP address space, the address space entered must be a valid address range (valid starting address and valid size), else a failure is encountered when sending a request. Currently, the portal doesn't validate CIDR input prior to sending requests.
0 commit comments