Skip to content

Commit 0f477c0

Browse files
author
Michael Bender
committed
IPAM updates
1 parent 5c3cbef commit 0f477c0

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/virtual-network-manager/concept-ip-address-management.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -68,16 +68,16 @@ When creating CIDR-supporting resources like virtual networks, CIDRs are automat
6868

6969
## Permission requirements for IPAM in Azure Virtual Network Manager
7070

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.
7272

7373
Learn more about [Azure role-based access control (Azure RBAC)](../role-based-access-control/overview.md).
7474

7575
## Known issues
7676

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.
8181

8282
## Next steps
8383

0 commit comments

Comments
 (0)