Skip to content

Commit f5d505c

Browse files
committed
Removed Known Issues
1 parent f6b3e44 commit f5d505c

File tree

1 file changed

+1
-8
lines changed

1 file changed

+1
-8
lines changed

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

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: mbender-ms
55
ms.author: mbender
66
ms.service: azure-virtual-network-manager
77
ms.topic: how-to
8-
ms.date: 10/08/2024
8+
ms.date: 1/16/2024
99
ms.custom: references_regions
1010
#customer intent: As a network administrator, I want to learn about IP address management in Azure Virtual Network Manager so that I can manage IP addresses in my virtual networks.
1111
---
@@ -72,13 +72,6 @@ When using IPAM, the **IPAM Pool User** role alone is sufficient for delegation.
7272

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

75-
## Known issues
76-
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.
81-
8275
## Next steps
8376

8477
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)