Skip to content

Commit 962a775

Browse files
Learn Editor: Update azure-vmware-solution-known-issues.md
1 parent 75a010f commit 962a775

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

articles/azure-vmware/azure-vmware-solution-known-issues.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ Refer to the table to find details about resolution dates or possible workaround
1616

1717
|Issue | Date discovered | Workaround | Date resolved |
1818
| :------------------------------------- | :------------ | :------------- | :------------- |
19+
|For Azure VMware Solution Generation 2 private clouds, resources hosted on Azure VMware Solution that are advertised as /32 routes (such as DNS resolvers used for LDAP) are not reachable from peered virtual networks. |March 17, 2026|Contact Microsoft Support to request an update to your Generation 2 private to allow correct programming of /32 routes.|October, 2026|
20+
|For Azure VMware Solution Generation 2 private clouds, when a subnet that was previously delegated to a service such as DNS Private Resolver, AKS or webapps is repurposed for Azure VMware Solution (e.g. NSX Segment), a subset of IP addresses in that subnet may experience connectivity failures. |April 8, 2026|Avoid reusing subnets that were previously delegated to services such as DNS Private Resolver, AKS or webapps. Instead, create a new subnet for the new workload. If the subnet has already been repurposed and you are experiencing connectivity issues, contact Microsoft Support to request cleanup of the stale subnets.|November, 2026|
1921
| Azure VMware Solution hosts and associated VMs may become unresponsive due to an [ESXi Mellanox driver issue](https://knowledge.broadcom.com/external/article/383273). | October 22, 2025 | Microsoft is actively monitoring and mitigating this issue and notifying all impacted customers that an urgent upgrade is necessary to remediate this issue. | October 22, 2025 - Resolved in [ESXi 8.0_U3f](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/esxi-update-and-patch-release-notes/vsphere-esxi-80u3f-release-notes.html) |
2022
| Compression and deduplication are disabled by default in vSAN OSA-based clusters. This behavior is observed starting from Cluster-2 onwards, whereas Cluster-1 was deployed with the default configuration. | September 29, 2025 | To remediate, use existing Set-vSANCompressDedupe Run command to enable Compression and Deduplication. Click the [link](./configure-vsan.md#set-vmware-vsan-space-efficiency) to learn more about Set-vSANCompressDedupe cmdlet. | N/A |
2123
| [VMSA-2025-0016](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36150) VMware vCenter Server and NSX updates address multiple vulnerabilities (CVE-2025-41250, CVE-2025-41251, CVE-2025-41252). | September 29, 2025 | These vulnerabilities do not apply to Azure VMware Solution since we have existing compensating controls to mitigate the risk of exploitation. | N/A |

0 commit comments

Comments
 (0)